From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Lucas Stach <dev@lynxeye.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/2] tegra20: add pinctrl driver
Date: Tue, 22 Oct 2013 17:07:06 +0200 [thread overview]
Message-ID: <20131022150706.GA27227@pengutronix.de> (raw)
In-Reply-To: <1368210538-15286-1-git-send-email-dev@lynxeye.de>
Hello Lucas,
On Fri, May 10, 2013 at 08:28:57PM +0200, Lucas Stach wrote:
> diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
> index e6aee50..0b859b8 100644
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> @@ -25,4 +25,10 @@ config PINCTRL_IMX_IOMUX_V3
> help
> This iomux controller is found on i.MX25,35,51,53,6.
>
> +config PINCTRL_TEGRA20
> + select PINCTRL
> + bool "Tegra 20 pinmux"
Now that I tried barebox' master on an i.MX28 I was presented with the
question to enable PINCTRL_TEGRA20 or not during oldconfig. Maybe don't
make this user-selectable? (The other pinctrl driver are affected by the
same "issue".)
> + help
> + The pinmux controller found on the Tegra 20 line of SoCs.
> +
> endmenu
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-10-22 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 18:28 [PATCH v2 1/2] tegra20: add pinctrl driver Lucas Stach
2013-05-10 18:28 ` [PATCH v2 2/2] tegra: paz00: import pinconfig from Linux Lucas Stach
2013-05-10 19:03 ` [PATCH v2 1/2] tegra20: add pinctrl driver Alexander Aring
2013-05-11 15:17 ` Sascha Hauer
2013-05-12 13:48 ` Jean-Christophe PLAGNIOL-VILLARD
2013-10-22 15:07 ` Uwe Kleine-König [this message]
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=20131022150706.GA27227@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=dev@lynxeye.de \
/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.