Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1353997 > unrolled thread

Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom  NS2 SoC Linus Walleij <linus.walleij@linaro.org> - 2016-03-09 12:10 +0100
    Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom  NS2 SoC Stephen Warren <swarren@wwwdotorg.org> - 2016-03-09 19:00 +0100
    Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom  NS2 SoC Ray Jui <ray.jui@broadcom.com> - 2016-03-09 22:10 +0100

#1353997 — Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC

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

?

Yours,
Linus Walleij

[toc] | [next] | [standalone]

#1354325

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.

[toc] | [prev] | [next] | [standalone]

#1354457

Hi Linus,

On 3/9/2016 3: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
>

I've reviewed this driver internally before it was sent out to public. 
Here's my reviewed-by:

Reviewed-by: Ray Jui <ray.jui@broadcom.com>

Like I mentioned before, we have been working closely with our ASIC team 
to have one pad per register based register layout in our next-gen SoC. 
That way we are able to use the generic pinctrl-single driver. It's 
definitely our best interest to re-use a generic driver when possible, 
to minimize the ongoing maintenance cost. Note we only have control on 
chips that we work on; there are other Broadcom SoCs that we do not have 
a say, unfortunately.

> - If this hardware looks suspiciously similar to one of the
>   other drivers and should rather me a subdriver of one of
>   the existing ones

The IOMUX block in NS2 seems different from that of Cygnus and NSP. It 
only supports group based mux configuration and does not have any 
mechanism to allow GPIO pin function override. It also supports per pad 
based pinconf functions.

>
> Yours,
> Linus Walleij
>

Thanks,

Ray

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web