From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Warren <swarren@nvidia.com>,
Tony Lindgren <tony@atomide.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] pinctrl: rip out the direct pinconf API
Date: Mon, 24 Jun 2013 09:26:28 -0600 [thread overview]
Message-ID: <51C86524.8020708@wwwdotorg.org> (raw)
In-Reply-To: <1372079700-16580-1-git-send-email-linus.walleij@stericsson.com>
On 06/24/2013 07:15 AM, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> From the inception ot the pin config API there has been the
> possibility to get a handle at a pin directly and configure
> its electrical characteristics. For this reason we had:
>
> int pin_config_get(const char *dev_name, const char *name,
> unsigned long *config);
> int pin_config_set(const char *dev_name, const char *name,
> unsigned long config);
> int pin_config_group_get(const char *dev_name,
> const char *pin_group,
> unsigned long *config);
> int pin_config_group_set(const char *dev_name,
> const char *pin_group,
> unsigned long config);
>
> After the intruction of the pin control states that will
> control pins associated with devices, and its subsequent
> introduction to the device core, as well as the
> introduction of pin control hogs that can set up states on
> boot and optionally also at sleep, this direct pin control
> API is a thing of the past.
>
> As could be expected, it has zero in-kernel users.
> Let's delete this API and make our world simpler.
Reviewed-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-06-24 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 13:15 [PATCH] pinctrl: rip out the direct pinconf API Linus Walleij
2013-06-24 15:26 ` Stephen Warren [this message]
2013-06-25 7:41 ` Tony Lindgren
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=51C86524.8020708@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=tony@atomide.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