All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-gpio@vger.kernel.org
Cc: sbranden@broadcom.com, linus.walleij@linaro.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH] pinctrl: bcm: Default PINCTRL_BCM281XX to y for ARCH_BCM_MOBILE
Date: Wed, 2 Dec 2015 09:42:57 -0800	[thread overview]
Message-ID: <565F2DA1.60908@broadcom.com> (raw)
In-Reply-To: <1449020490-27084-1-git-send-email-f.fainelli@gmail.com>



On 12/1/2015 5:41 PM, Florian Fainelli wrote:
> This driver is mandatory for proper operation on the platforms covered
> by the ARCH_BCM_MOBILE Kconfig symbol, make sure we do that driver on
> for these platforms.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>   drivers/pinctrl/bcm/Kconfig | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pinctrl/bcm/Kconfig b/drivers/pinctrl/bcm/Kconfig
> index cd11d4d9ad58..b63d7068f26c 100644
> --- a/drivers/pinctrl/bcm/Kconfig
> +++ b/drivers/pinctrl/bcm/Kconfig
> @@ -9,6 +9,7 @@ config PINCTRL_BCM281XX
>   	select PINCONF
>   	select GENERIC_PINCONF
>   	select REGMAP_MMIO
> +	default ARCH_BCM_MOBILE
>   	help
>   	  Say Y here to support Broadcom BCM281xx pinctrl driver, which is used
>   	  for the BCM281xx SoC family, including BCM11130, BCM11140, BCM11351,
>

pinmux and pinctrl related configurations from the bcm281xx pinctrl 
driver are indeed mandatory for ARCH_BCM_MOBILE related platforms for 
some peripherals to function properly. It looks like we are missing some 
required configurations in the DT files though, but I guess that needs 
to be addressed by separate patches.

This change looks good to me!

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

Thanks!

Ray

  reply	other threads:[~2015-12-02 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  1:41 [PATCH] pinctrl: bcm: Default PINCTRL_BCM281XX to y for ARCH_BCM_MOBILE Florian Fainelli
2015-12-02 17:42 ` Ray Jui [this message]
2015-12-10 22:54 ` Linus Walleij

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=565F2DA1.60908@broadcom.com \
    --to=rjui@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=sbranden@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.