From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: enable pinctrl for Broadcom NSP
Date: Tue, 1 Dec 2015 08:24:21 -0800 [thread overview]
Message-ID: <565DC9B5.8070801@broadcom.com> (raw)
In-Reply-To: <565DC555.2070004@broadcom.com>
On 12/1/2015 8:05 AM, Scott Branden wrote:
> Hi Linus,
>
> On 15-12-01 02:00 AM, Linus Walleij wrote:
>> On Wed, Nov 25, 2015 at 1:08 AM, Florian Fainelli
>> <f.fainelli@gmail.com> wrote:
>>> On 20/11/15 09:58, Yendapally Reddy Dhananjaya Reddy wrote:
>>>> This enables the pinctrl support for Broadcom NSP SoC
>>>>
>>>> Signed-off-by: Yendapally Reddy Dhananjaya Reddy
>>>> <yrdreddy@broadcom.com>
>>>
>>> Looks like a sane pinctrl node here, unless there are objections, I
>>> would like to go ahead and apply this for v4.5, thanks!
>>
>> I'm waiting for an indication from the other BCM pinctrl
>> maintainers to tell whether this SoC is unique enough to deserve
>> its own driver.
> If Stephen Warren is the other maintainer you are talking about he does
> not work at Broadcom. I don't think he is familiar with the variety of
> pinctrl implementations present. But yes, the pinctrl implementations
> have been rather unique in these Socs. As Ray indicated we're trying to
> get the silicon designers to standardize more going forward so we don't
> have to create unique drivers for these SoCs.
Yes. Hopefully NSP and NS2 will be the last iProc based SoCs that
require unique pinmux driver.
>>
>> Yours,
>> Linus Walleij
>>
>
> Regards,
> Scott
>
Thanks,
Ray
next prev parent reply other threads:[~2015-12-01 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 17:58 [PATCH 3/3] ARM: dts: enable pinctrl for Broadcom NSP Yendapally Reddy Dhananjaya Reddy
2015-11-25 0:08 ` Florian Fainelli
2015-12-01 10:00 ` Linus Walleij
2015-12-01 16:05 ` Scott Branden
2015-12-01 16:24 ` Ray Jui [this message]
2015-12-01 23:17 ` Florian Fainelli
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=565DC9B5.8070801@broadcom.com \
--to=rjui@broadcom.com \
--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).