ARM topic: Is DT on ARM the solution, or is there something better?

Grant Likely grant.likely at secretlab.ca
Mon Nov 18 08:40:22 EST 2013


On Mon, 18 Nov 2013 13:26:46 +0100, Thierry Reding <thierry.reding at gmail.com> wrote:
> On Sun, Oct 20, 2013 at 10:26:54PM +0100, Stephen Warren wrote:
> [...]
> > In general, the kernel still needs a complete driver to every last
> > device on every strange board, and needs to support every strange way
> > some random board hooks all the devices together.
> [...]
> 
> This may only be slightly related and it doesn't address all the points
> you brought up here, but for lack of a better place, here goes.
> 
> I've had an interesting discussion with a friend over the weekend which
> eventually turned to a similar topic. With all the recent discussions
> about how to push board-specific details out into firmware, perhaps a
> more drastic measure would be to push for standardization of hardware
> interfaces.

Some hardware does that. That's what OHCI, EHCI, UHCI, XHCI, SDHCI, and
similar are all about. It always helps when well understood hardware
follows a register interface. It doesn't work for everything, but I
agree it would be good to have preferred hw interfaces for SPI & I2C.

g.




More information about the linux-arm-kernel mailing list