linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mzoran@crowfest.net (Michael Zoran)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: extend Raspberry Pi entry
Date: Mon, 30 Jan 2017 00:09:32 -0800	[thread overview]
Message-ID: <1485763772.13537.1.camel@crowfest.net> (raw)
In-Reply-To: <20170130075609.pcrujbzdnabkmuux@pengutronix.de>

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.

  reply	other threads:[~2017-01-30  8:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 20:08 [PATCH] MAINTAINERS: extend Raspberry Pi entry Baruch Siach
2017-01-29 20:52 ` Michael Zoran
2017-01-29 21:06   ` Baruch Siach
2017-01-29 21:41     ` Michael Zoran
2017-01-29 21:52       ` Baruch Siach
2017-01-29 22:02         ` Michael Zoran
2017-01-29 22:24           ` Michael Zoran
2017-01-30  7:56             ` Uwe Kleine-König
2017-01-30  8:09               ` Michael Zoran [this message]
2017-01-30  8:51                 ` Uwe Kleine-König
2017-01-30  9:01                   ` Michael Zoran
2017-01-29 21:06   ` Stefan Wahren
2017-01-29 21:25   ` Michael Zoran
2017-01-30 17:03 ` Stephen Warren
2017-01-31 19:49   ` Eric Anholt
2017-02-01  5:21     ` Stephen Warren
2017-02-01 19:51       ` Eric Anholt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1485763772.13537.1.camel@crowfest.net \
    --to=mzoran@crowfest.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).