From: Tony Lindgren <tony@atomide.com>
To: FanWu <fwu@marvell.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>, Chao Xie <cxie4@marvell.com>,
Yilu Mao <ylmao@marvell.com>, Ning Jiang <njiang1@marvell.com>,
Xiaofan Tian <tianxf@marvell.com>, Fangsuo Wu <fswu@marvell.com>
Subject: Re: [PATCH] pinctrl: add params in disable_setting for different usage
Date: Wed, 21 May 2014 15:52:26 -0700 [thread overview]
Message-ID: <20140521225226.GE14520@atomide.com> (raw)
In-Reply-To: <537C4605.2090203@marvell.com>
* FanWu <fwu@marvell.com> [140520 23:23]:
> To remove the HW disable function in pinmux_disable_setting is no effect for
> our SoC platform. I am just not sure whether it has effect for other
> platform just as I described before.
> If there is no vendor using the HW disabling operation, I also agree to
> remove this. :)
>
> Could you please give your suggestion about this topic ?
I agree with Stephen that we should remove the disable as at least
for the SoCs that I've dealt with there is no disable setting. The
closest I can think of is the safe mode that some omaps have, but
that too is just one mode. And disabling input logic can be done
separately from the mux mode typically.
Regards,
Tony
next prev parent reply other threads:[~2014-05-21 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 2:01 [PATCH] pinctrl: add params in disable_setting for different usage fwu
2014-05-16 16:21 ` Linus Walleij
2014-05-16 19:53 ` Stephen Warren
2014-05-19 2:54 ` FanWu
2014-05-19 20:55 ` Stephen Warren
2014-05-20 3:05 ` FanWu
2014-05-20 18:42 ` Stephen Warren
2014-05-21 6:21 ` FanWu
2014-05-21 22:52 ` Tony Lindgren [this message]
2014-05-23 14:10 ` 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=20140521225226.GE14520@atomide.com \
--to=tony@atomide.com \
--cc=cxie4@marvell.com \
--cc=fswu@marvell.com \
--cc=fwu@marvell.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=njiang1@marvell.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=tianxf@marvell.com \
--cc=ylmao@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox