From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Stefan Wahren <stefan.wahren@i2se.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Pramod KUMAR <pramodku@broadcom.com>,
Jonathan Bell <jonathan@raspberrypi.org>,
Scott Branden <sbranden@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC
Date: Wed, 9 Mar 2016 10:50:09 -0700 [thread overview]
Message-ID: <56E06251.3020502@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdaKn4puDsZBPSbfkmHW4KHqBW8q1T2vpyNk_0Yb7C0AXQ@mail.gmail.com>
On 03/09/2016 04:04 AM, Linus Walleij wrote:
> On Thu, Mar 3, 2016 at 6:41 PM, Yendapally Reddy Dhananjaya Reddy
> <yendapally.reddy@broadcom.com> wrote:
>
>> This adds the initial support of the Broadcom NS2 pinmux driver
>>
>> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
>
> Now yet another Broadcom driver!
>
> Can I get the help of the maintainers of the other
> Broadcom drivers to say:
>
> - If this looks sane
>
> - If this hardware looks suspiciously similar to one of the
> other drivers and should rather me a subdriver of one of
> the existing ones
Based on this patch, I don't quickly see any obvious relation between
this HW and bcm2835. I don't know anything about other bcm pinmux, so
didn't check those.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC
Date: Wed, 9 Mar 2016 10:50:09 -0700 [thread overview]
Message-ID: <56E06251.3020502@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdaKn4puDsZBPSbfkmHW4KHqBW8q1T2vpyNk_0Yb7C0AXQ@mail.gmail.com>
On 03/09/2016 04:04 AM, Linus Walleij wrote:
> On Thu, Mar 3, 2016 at 6:41 PM, Yendapally Reddy Dhananjaya Reddy
> <yendapally.reddy@broadcom.com> wrote:
>
>> This adds the initial support of the Broadcom NS2 pinmux driver
>>
>> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
>
> Now yet another Broadcom driver!
>
> Can I get the help of the maintainers of the other
> Broadcom drivers to say:
>
> - If this looks sane
>
> - If this hardware looks suspiciously similar to one of the
> other drivers and should rather me a subdriver of one of
> the existing ones
Based on this patch, I don't quickly see any obvious relation between
this HW and bcm2835. I don't know anything about other bcm pinmux, so
didn't check those.
next prev parent reply other threads:[~2016-03-09 17:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:41 [PATCH 0/3] pinmux support for Broadcom NS2 SoC Yendapally Reddy Dhananjaya Reddy
2016-03-03 11:41 ` Yendapally Reddy Dhananjaya Reddy
2016-03-03 11:41 ` [PATCH 1/3] pinctrl: Broadcom Northstar2 pinctrl device tree bindings Yendapally Reddy Dhananjaya Reddy
2016-03-03 11:41 ` Yendapally Reddy Dhananjaya Reddy
2016-03-05 4:29 ` Rob Herring
2016-03-05 4:29 ` Rob Herring
2016-03-09 10:58 ` Linus Walleij
2016-03-09 10:58 ` Linus Walleij
2016-03-03 11:41 ` [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC Yendapally Reddy Dhananjaya Reddy
2016-03-03 11:41 ` Yendapally Reddy Dhananjaya Reddy
2016-03-09 11:04 ` Linus Walleij
2016-03-09 11:04 ` Linus Walleij
2016-03-09 17:50 ` Stephen Warren [this message]
2016-03-09 17:50 ` Stephen Warren
2016-03-09 21:07 ` Ray Jui
2016-03-03 11:41 ` [PATCH 3/3] ARM: dts: enable pinctrl " Yendapally Reddy Dhananjaya Reddy
2016-03-03 11:41 ` Yendapally Reddy Dhananjaya Reddy
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=56E06251.3020502@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=jonathan@raspberrypi.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pramodku@broadcom.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=yendapally.reddy@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.