From: Tomasz Figa <tomasz.figa@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Kevin Bracey" <kevin@bracey.fi>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"Kyungmin Park" <kmpark@infradead.org>,
"Heiko Stübner" <heiko@sntech.de>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Tomasz Figa" <t.figa@samsung.com>,
"Doug Anderson" <dianders@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kukjin Kim" <kgene.kim@samsung.com>,
"Thomas Abraham" <thomas.abraham@linaro.org>,
"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [PATCH] pinctrl: samsung: Allow pin value to be initialized using pinfunc.
Date: Tue, 03 Dec 2013 10:33:43 +0100 [thread overview]
Message-ID: <2004634.MefHDYV4b2@flatron> (raw)
In-Reply-To: <CACRpkdYDONQ-7U3hGYnx7jb0_Y=rcOcvy-2F1dO058FfOO4stg@mail.gmail.com>
On Tuesday 03 of December 2013 10:31:12 Linus Walleij wrote:
> On Tue, Nov 26, 2013 at 1:30 AM, Tomasz Figa <tomasz.figa@gmail.com> wrote:
>
> > IMHO a way to specify a default safe state of all pins (with lowest power
> > consumption, without possibility of glitching external devices, etc.)
> > would be really useful for Samsung platforms (and probably Renesas ones
> > as Kevin wrote).
>
> I'm following :-)
>
> Now if we could see some more details and a patch, that would
> be great ...
Yeah, I would like to see them too. ;)
Unfortunately my make_pinctrl_default_state_patches() function is
returning -ENOTIME at the moment. :( (I hope to get it fixed
later this month, though.)
Best regards,
Tomasz
next prev parent reply other threads:[~2013-12-03 9:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 17:15 [PATCH] pinctrl: samsung: Allow pin value to be initialized using pinfunc Tomasz Figa
2013-11-19 18:46 ` Stephen Warren
2013-11-19 18:59 ` Doug Anderson
2013-11-19 19:16 ` Stephen Warren
2013-11-20 0:02 ` Kyungmin Park
2013-11-20 0:07 ` Stephen Warren
2013-11-20 12:51 ` Mark Brown
2013-11-25 14:34 ` Linus Walleij
2013-11-25 20:01 ` Kevin Bracey
2013-11-26 0:30 ` Tomasz Figa
2013-12-03 9:31 ` Linus Walleij
2013-12-03 9:33 ` Tomasz Figa [this message]
2013-12-03 9:29 ` Linus Walleij
2013-12-05 15:07 ` Mark Brown
2013-12-05 15:11 ` Tomasz Figa
2013-12-05 16:49 ` Kevin Bracey
2013-12-05 17:03 ` Tomasz Figa
2013-12-05 18:00 ` Mark Brown
2013-12-09 10:22 ` Linus Walleij
2013-12-09 17:04 ` Mark Brown
[not found] ` <CACRpkdYrPd9tnO48bA_5n+-k=KEDyhY7czkCNhTZfpgF3ar+LQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-05 23:54 ` Stephen Warren
2013-12-09 12:57 ` Linus Walleij
2013-11-20 14:57 ` Tomasz Figa
2013-11-20 13:38 ` Tomasz Figa
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=2004634.MefHDYV4b2@flatron \
--to=tomasz.figa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=kevin@bracey.fi \
--cc=kgene.kim@samsung.com \
--cc=kmpark@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=swarren@wwwdotorg.org \
--cc=t.figa@samsung.com \
--cc=thomas.abraham@linaro.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).