From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Daniel Mack <zonque@gmail.com>,
linux-input@vger.kernel.org,
Jonas ABERG <jonas.aberg@stericsson.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH] Input: gpio_keys: allocate pins
Date: Fri, 12 Oct 2012 14:35:52 -0700 [thread overview]
Message-ID: <2124185.0mAfDLSa7H@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <CACRpkdayOh=i4Fp6zWCy2yt7ZJU=ETD3x6N3KTAg++QhPOzH-w@mail.gmail.com>
On Friday, October 12, 2012 11:26:00 PM Linus Walleij wrote:
> On Fri, Oct 12, 2012 at 5:55 PM, Daniel Mack <zonque@gmail.com> wrote:
> > This allows DT driven boards to allocate and configure the pinmux once
> > the driver is probed.
> >
> > Signed-off-by: Daniel Mack <zonque@gmail.com>
> > Cc: Linus Walleij <linus.walleij@linaro.org>
> > Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
> (...)
>
> > + /* request pin mux */
> > + pinctrl = devm_pinctrl_get_select_default(dev);
> > + if (IS_ERR(pinctrl))
> > + dev_warn(dev, "pins are not configured from the
> > driver\n");
>
> I think dev_warn() is rather nasty to throw in here, dev_info() is OK.
>
> However I suspect this driver could actually handle default, idle and sleep
> states, especially after the runtime PM patches discussed elsewhere,
> but that can be patched later.
I take this as Acked-by then?
--
Dmitry
next prev parent reply other threads:[~2012-10-12 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 15:55 [PATCH] Input: gpio_keys: allocate pins Daniel Mack
2012-10-12 21:26 ` Linus Walleij
2012-10-12 21:27 ` Daniel Mack
2012-10-12 21:37 ` Linus Walleij
2012-10-12 21:40 ` Daniel Mack
2012-10-12 21:44 ` Linus Walleij
2012-10-25 7:58 ` Lee Jones
2012-10-25 8:08 ` Linus Walleij
2012-10-25 8:20 ` Lee Jones
2012-10-25 8:20 ` Daniel Mack
2012-10-12 21:35 ` Dmitry Torokhov [this message]
2012-10-12 21:40 ` 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=2124185.0mAfDLSa7H@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=jonas.aberg@stericsson.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).