[PATCH] MAINTAINERS: extend Raspberry Pi entry

Uwe Kleine-König u.kleine-koenig at pengutronix.de
Mon Jan 30 00:51:28 PST 2017

On Mon, Jan 30, 2017 at 12:09:32AM -0800, Michael Zoran wrote:
> On Mon, 2017-01-30 at 08:56 +0100, Uwe Kleine-König wrote:
> > On Sun, Jan 29, 2017 at 02:24:08PM -0800, Michael Zoran wrote:
> > I don't agree. To be able to review a driver to a Broadcom specific
> > spi
> > driver, you need to know more about spi than about Broadcom.
> > 
> I would say that's 50/50.  Some of these drivers like I2C or SPI
> are not really that complex.  The complexity happens when people begin
> to try to connect the various drivers in arbitrary ways at which point
> things begin to break.
> SOCs are designed with cost in mind, so allowing arbitrary
> configurations are not aways possible because of attempts to limits the
> amount of hardware resources required and the complexity. And I don't
> think this is specific to Broadcom or anybody. It's just the way SOCs
> work.
> This is all vary different from PCs where you expect people to buy
> random parts and start connecting them together.  For the reasons I
> have given, SOCs arn't quite as flexible.

I fail to follow here. Can you please show an example where you see a
benefit from having the drivers grouped by SoC instead of bus type?

Best regards

Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

More information about the linux-rpi-kernel mailing list