From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Christoph Fritz <chf.fritz@googlemail.com>
Cc: Steve Glendinning <steve.glendinning@shawell.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Sebastien Guiriec <s-guiriec@ti.com>,
Daniel Mack <daniel@zonque.org>,
"Hans J. Koch" <hjk@hansjkoch.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] net: smsc911x: adopt pinctrl support
Date: Sat, 13 Apr 2013 20:32:45 +0200 [thread overview]
Message-ID: <CAAwP0s2BD_nVXPyTi+EsgnqStdFUbHELJRjU_sP5E_w-XiWnRw@mail.gmail.com> (raw)
In-Reply-To: <1365873745.3812.37.camel@mars>
On Sat, Apr 13, 2013 at 7:22 PM, Christoph Fritz
<chf.fritz@googlemail.com> wrote:
> This patch is derived from 2d4b4520a "i2c: omap: adopt pinctrl support":
> Some GPIO expanders need some early pin control muxing. Due to
> legacy boards sometimes the driver uses subsys_initcall instead of
> module_init. This patch takes advantage of defer probe feature
> and pin control in order to wait until pin control probing before
> GPIO driver probing.
>
> Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> ---
> drivers/net/ethernet/smsc/smsc911x.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/net/ethernet/smsc/smsc911x.c b/drivers/net/ethernet/smsc/smsc911x.c
> index da5cc9a..3e3547c 100644
> --- a/drivers/net/ethernet/smsc/smsc911x.c
> +++ b/drivers/net/ethernet/smsc/smsc911x.c
> @@ -59,6 +59,7 @@
> #include <linux/of_device.h>
> #include <linux/of_gpio.h>
> #include <linux/of_net.h>
> +#include <linux/pinctrl/consumer.h>
> #include "smsc911x.h"
>
> #define SMSC_CHIPNAME "smsc911x"
> @@ -144,6 +145,8 @@ struct smsc911x_data {
>
> /* regulators */
> struct regulator_bulk_data supplies[SMSC911X_NUM_SUPPLIES];
> +
> + struct pinctrl *pins;
> };
>
> /* Easy access to information */
> @@ -2433,6 +2436,18 @@ static int smsc911x_drv_probe(struct platform_device *pdev)
> if (retval < 0)
> goto out_disable_resources;
>
> + pdata->pins = devm_pinctrl_get_select_default(&pdev->dev);
> + if (IS_ERR(pdata->pins)) {
> + if (PTR_ERR(pdata->pins) == -EPROBE_DEFER) {
> + retval = -EPROBE_DEFER;
> + goto out_disable_resources;
> + }
> +
> + dev_warn(&pdev->dev, "No pins for smsc911x error: %li\n",
> + PTR_ERR(pdata->pins));
> + pdata->pins = NULL;
> + }
> +
> /* configure irq polarity and type before connecting isr */
> if (pdata->config.irq_polarity == SMSC911X_IRQ_POLARITY_ACTIVE_HIGH)
> intcfg |= INT_CFG_IRQ_POL_;
> --
> 1.7.10.4
>
>
>
Hi Christoph,
This is handled from the device core after from v3.9.
Please take a loot at this:
http://marc.info/?l=linux-kernel&m=135887740715083&w=2
Best regards,
Javier
prev parent reply other threads:[~2013-04-13 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 17:22 [PATCH] net: smsc911x: adopt pinctrl support Christoph Fritz
2013-04-13 18:32 ` Javier Martinez Canillas [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=CAAwP0s2BD_nVXPyTi+EsgnqStdFUbHELJRjU_sP5E_w-XiWnRw@mail.gmail.com \
--to=martinez.javier@gmail.com \
--cc=chf.fritz@googlemail.com \
--cc=daniel@zonque.org \
--cc=hjk@hansjkoch.de \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s-guiriec@ti.com \
--cc=steve.glendinning@shawell.net \
/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).