From: Heiko Schocher <hs-ynQEQJNshbs@public.gmane.org>
To: Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] arm, imx6, dts: add aristainetos board support
Date: Fri, 20 Jun 2014 16:24:32 +0200 [thread overview]
Message-ID: <53A44420.6010106@denx.de> (raw)
In-Reply-To: <20140620130628.GK28225@dragon>
Hello Shwan,
Am 20.06.2014 15:06, schrieb Shawn Guo:
> On Thu, Jun 19, 2014 at 01:26:21PM +0200, Heiko Schocher wrote:
>>>> + pinctrl-names = "default";
>>>> + pinctrl-0 =<&pinctrl_hog&pinctrl_backlight&pinctrl_gpio>;
>>>
>>> pinctrl_backlight and pinctrl_gpio shouldn't be in there.
>>
>> removed&pinctrl_backlight, removed device specific gpios to
>> device nodes ... but there are some gpios only used with GPIO API ...
>>
>> Where to move this pinctrls ?
>
> For GPIO that do not have a clear client device owing, it's fine to have
> it in hog group.
Ok, so I put them back to the DTS.
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-06-20 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 6:35 [PATCH] arm, imx6, dts: add aristainetos board support Heiko Schocher
[not found] ` <1402468548-17539-1-git-send-email-hs-ynQEQJNshbs@public.gmane.org>
2014-06-18 13:29 ` Shawn Guo
2014-06-19 11:26 ` Heiko Schocher
[not found] ` <53A2C8DD.7000601-ynQEQJNshbs@public.gmane.org>
2014-06-20 13:06 ` Shawn Guo
2014-06-20 14:24 ` Heiko Schocher [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=53A44420.6010106@denx.de \
--to=hs-ynqeqjnshbs@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).