All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] net: gmac_rockchip: Add support for pinctrl
Date: Thu, 6 Jul 2017 21:58:59 -0600	[thread overview]
Message-ID: <CAPnjgZ3dhdyaKkFoUs=EijUskbszYhPyyU53jWqncYQbrTwv_A@mail.gmail.com> (raw)
In-Reply-To: <20170703071312.19770-1-romain.perier@collabora.com>

+Philipp

Hi Romain,

On 3 July 2017 at 01:13, Romain Perier <romain.perier@collabora.com> wrote:
> Currently, selecting state simple is done by the device driver model,
> prior probing the driver. The problem is that it's done and called on
> the pinctrl node with "gmac" as the "periph" struct udevice *. So
> pinctrl-rk3288 is looking for an interrupt property that is not found,
> and then gmac_config is never called.
>
> This commits toggles the pinctrl on the right node from the probe
> function of the driver.

Is it possible to fix this while still using driver-model automatic pinctrl?

>
> Signed-off-by: Romain Perier <romain.perier@collabora.com>
> ---
>  drivers/net/gmac_rockchip.c | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/drivers/net/gmac_rockchip.c b/drivers/net/gmac_rockchip.c
> index 5e2ca76302..8581026b4a 100644
> --- a/drivers/net/gmac_rockchip.c
> +++ b/drivers/net/gmac_rockchip.c
> @@ -160,6 +160,10 @@ static int gmac_rockchip_probe(struct udevice *dev)
>         struct clk clk;
>         int ret;
>
> +       ret = pinctrl_select_state(dev, "simple");
> +       if (ret)
> +               return ret;
> +
>         ret = clk_get_by_index(dev, 0, &clk);
>         if (ret)
>                 return ret;
> --
> 2.11.0
>

Regards,
Simon

  reply	other threads:[~2017-07-07  3:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  7:13 [U-Boot] [PATCH] net: gmac_rockchip: Add support for pinctrl Romain Perier
2017-07-07  3:58 ` Simon Glass [this message]
2017-07-10  6:43   ` Romain Perier
2017-07-11 13:43     ` Dr. Philipp Tomsich
2017-07-11 14:30       ` Romain Perier
2017-07-11 13:44   ` Dr. Philipp Tomsich

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='CAPnjgZ3dhdyaKkFoUs=EijUskbszYhPyyU53jWqncYQbrTwv_A@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.