All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: GPIO request failures for Renesas rcar-gen3
Date: Thu, 18 Jun 2020 23:00:39 +0200	[thread overview]
Message-ID: <6c86fb41-bb62-cf4e-1339-4e20d806e22b@gmail.com> (raw)
In-Reply-To: <CAHCN7xJKTP5L5fxizfX0+CWrnT8PMeodiZpqna=waP7UMgwD8w@mail.gmail.com>

On 6/18/20 10:33 PM, Adam Ford wrote:
> I am trying to port U-Boot to a new product based on a Renesas RZ/G2M
> (rcar-gen3).  We're have this working with Renesas' version from
> 2018.09, but I am trying to integrate it with U-Boot 2020.07-rc4
> 
> What's happening is that it seems like all GPIO are failing to be
> requested, so things like regulator-gpio fail, reset-gpios, etc. all
> return errors.
> 
> The dm tree and gpio status commands all appear to show gpio banks are
> enumerating, but since nothing can use the GPIO's it seems like the
> common thread is the gpio driver for the rcar3.
> 
> I was hoping someone might have some thoughts of things I could try or
> investigate.  In order to properly set the voltage for the MMC card, I
> need "regulator-gpio" to operate correctly.

Note that RZ/G2M is not supported by mainline U-Boot.

Also note that the GPIO driver and PFC drivers are working together,
grep for sh_pfc_config_mux_for_gpio(), so unless both work and probed,
the GPIO driver will likely not work.

Can you provide 'dm tree' output ?

  reply	other threads:[~2020-06-18 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 20:33 GPIO request failures for Renesas rcar-gen3 Adam Ford
2020-06-18 21:00 ` Marek Vasut [this message]
2020-06-18 21:20   ` Adam Ford
2020-06-18 21:29     ` Adam Ford
2020-06-18 21:33     ` Marek Vasut
2020-06-18 21:46       ` Adam Ford
2020-06-18 21:49         ` Marek Vasut

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=6c86fb41-bb62-cf4e-1339-4e20d806e22b@gmail.com \
    --to=marek.vasut@gmail.com \
    --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.