Hi Mark,
On Thu, Dec 15, 2016 at 6:53 PM, Mark Brown <broonie@xxxxxxxxxx> wrote:
> On Mon, Sep 12, 2016 at 10:50:42PM +0200, Geert Uytterhoeven wrote:
>> TBD:
>> - s/spi_master/spi_controller/ where appropriate,
>> - Provide wrappers (e.g. "#define spi_master spi_controller" until all
>> SPI drivers have been converted),
>> - Do we want a separate spi_register_slave() instead?
>
> This basically looks fine to me - there's these TBDs so I might be
> missing things and we probably need some GPIO chip select handling but
Given the hard real-time requirements of SPI slave, supporting GPIO chip
select may not be feasible.
> that's a separate thing. Sorry it took me so long to review this.
Thanks for the review!
As I managed to fix the issue with spi_slave_abort() on MSIOF, I think
the remaining
obstacle is the DT binding. Do you have any feedback or other
suggestions in that area?
IMHO having the ability to bind to an SPI slave handler either from DT or
by using the sysfs virtual file is useful to have.
Thanks again!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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 devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
