All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Random Linux/device tree/GPIO question posted to the wrong list...
Date: Tue, 31 Jul 2018 16:17:56 +0200	[thread overview]
Message-ID: <20180731161756.47cb4d72@windsurf> (raw)
In-Reply-To: <CAF_dkJAfeaGXejcOkUk8=WMfS6eNbqLjNYPZHaRU1wArb7_G6w@mail.gmail.com>

Hello Patrick,

On Tue, 31 Jul 2018 09:53:34 -0400, Patrick Doyle wrote:

> Thank you for the quick reply.  pinctrl_nand_default _is_ referenced
> by the device tree clause for the nand controller:
> 
>         nand0: nand at 80000000 {
>             nand-bus-width = <8>;
>             nand-ecc-mode = "hw";
>             nand-on-flash-bbt;
>             atmel,has-pmecc;
>             atmel,pmecc-cap = <12>;
>             atmel,pmecc-sector-size = <512>;
>             pinctrl-names = "default";
>             pinctrl-0 = <&pinctrl_nand_default &pinctrl_nand_rdy_en>;
>             status = "okay";
> ...
> 
> Hence my confusion.  Am I missing something else somewhere?

Asked internally, and my colleague Maxime Ripard (in Cc) gave some
explanation about this: it depends on whether the pinctrl driver uses
the strict mode or not and the Atmel doesn't.

This allows to request a pin as a GPIO even if this pin is already
muxed as a different functionality. Some details about this are
available at "GPIO mode pitfalls" in
https://www.kernel.org/doc/Documentation/driver-api/pinctl.rst (link
also provided by Maxime).

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-31 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 21:29 [Buildroot] Random Linux/device tree/GPIO question posted to the wrong list Patrick Doyle
2018-07-30 21:51 ` Thomas Petazzoni
2018-07-31 13:53   ` Patrick Doyle
2018-07-31 14:17     ` Thomas Petazzoni [this message]
2018-07-31 15:17       ` Patrick Doyle

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=20180731161756.47cb4d72@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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 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.