Messages in this thread | | | Date | Thu, 24 May 2018 17:29:40 +0100 | From | Mark Brown <> | Subject | Re: [PATCH] spi: spi-geni-qcom: Add SPI driver support for GENI based QUP |
| |
On Thu, May 24, 2018 at 10:25:58AM -0600, Mahadevan, Girish wrote:
> The reason I have the cur_speed_hz is that there is a max_speed_hz which > is the max frequency the slave can do; but every transfer can also > specify a speed_hz and override this.
Every transfer *will* specify a speed, you should never see a transfer that doesn't specify a speed.
> > delay_usecs is for inter-transfer delays within a message rather than > > after the initial chip select assert (it can be used to keep chip select > > asserted for longer after the final transfer too). Obviously this is > > also something that shouldn't be configured in a driver specific > > fashion.
> Hmmm ok, so you mean don't send these as controller_data, rather add new > members to the spi_device struct ?
Yes, that'd be one way to do it. [unhandled content-type:application/pgp-signature] | |