From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Dong Aisheng <aisheng.dong@freescale.com>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
Dong Aisheng-B29396 <B29396@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] pinctrl: handle dummy state in core
Date: Wed, 18 Apr 2012 11:37:09 -0600 [thread overview]
Message-ID: <4F8EFBC5.1030607@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdZw6iv=PjvvU4s5L8yV6813gCD7t8Vk-S66v-nXPaf+=Q@mail.gmail.com>
On 04/18/2012 07:52 AM, Linus Walleij wrote:
> On Wed, Apr 18, 2012 at 2:28 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
>> Currently Dong Aisheng is working on i.MX6, we have i.MX31, i.MX35,
>> i.MX51 and i.MX53 enabled in the same defconfig. Waiting for all
>> machines turn over at once to pinctrl is illusionary. We have to make
>> drivers work with and without pinctrl. We have a bunch of bad choices:
>>
>> - create a dummy pinctrl for all boards which do not have real pinmux
>> support
>
> Viable compromise.
>
>> - ignore pinctrl_request errors in drivers.
>
> Ugh. Not good.
>
>> - generate and return a dummy pinctrl in the core if no real pinctrl is
>> found.
>>
>> (replace pinctrl with regulators or clocks, it's the same situation, and
>> it's not only i.MX specific)
>
> Since we have dummy regulators, we should not break the design
> pattern creating more confusion.
>
> Stephen can you live with dummy pinctrl handles emitted by the
> core, if explicitly enabled by a Kconfig option?
Yes, I'm happy with the pinctrl core having the ability to "magically"
work when the dummy mapping table entries (or DT entries) are missing,
so long as there is a default-off Kconfig or runtime option that enables
that feature, which I'd expect to be use only for boards/platforms/...
that are "under conversion".
prev parent reply other threads:[~2012-04-18 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 14:24 [PATCH 1/1] pinctrl: handle dummy state in core Dong Aisheng
2012-04-16 16:03 ` Stephen Warren
2012-04-17 3:42 ` Dong Aisheng
2012-04-17 19:53 ` Stephen Warren
2012-04-18 11:31 ` Linus Walleij
2012-04-18 12:28 ` Sascha Hauer
2012-04-18 13:52 ` Linus Walleij
2012-04-18 14:00 ` Sascha Hauer
2012-04-18 14:38 ` Dong Aisheng
2012-04-19 17:22 ` Linus Walleij
2012-04-18 17:37 ` Stephen Warren [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=4F8EFBC5.1030607@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=B29396@freescale.com \
--cc=aisheng.dong@freescale.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox