On Fri, Jan 24, 2014 at 7:28 AM, Baruch Siach <[email protected]> wrote:
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -285,7 +285,9 @@ static inline void spi_unregister_driver(struct
> spi_driver *sdrv)
> * @transfer_one: transfer a single spi_transfer. When the
> * driver is finished with this transfer it must call
> * spi_finalize_current_transfer() so the subsystem can issue
> - * the next transfer
> + * the next transfer. Note: transfer_one and
> + * transfer_one_message are mutually exclusive; when both are
> + * set, transfer_one takes precedence.
I find this a bit difficult to grasp. What does "take precedence" mean in
this context?
The default spi_transfer_one_message() uses .transfer_one().
But if .transfer_one_message() is set, it depends on your own driver if
.transfer_one() is used or not.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
