mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: DTS: myir-x335x: Add GPIO aliases
Date: Tue, 24 May 2022 12:21:58 +0300	[thread overview]
Message-ID: <CAP1tNvScB7n4u0HuEkqtM8_KVXy_izWuT2vkRk-bfqfVAjHA4A@mail.gmail.com> (raw)
In-Reply-To: <20220524090314.sdb3tt6jhtjpmm6o@pengutronix.de>

вт, 24 мая 2022 г. в 12:03, Marco Felsch <m.felsch@pengutronix.de>:
> On 22-05-24, Alexander Shiyan wrote:
> > For the correct work of GPIO driver, we need to define aliases.
> > Let's add them to the devicetree.
...
> > +     aliases {
> > +             gpio0 = &gpio0;
> > +             gpio1 = &gpio1;
> > +             gpio2 = &gpio2;
> > +             gpio3 = &gpio3;
> > +     };
>
> Out of curiousity, are those aliases not defined in the "upstream" linux
> device-tree? If not, wouldn't it be better to defined it there?

Hello.

The linux gpio-omap driver does not use aliases, it would be hard for
me to explain the need to make such changes to the linux dts tree :)

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2022-05-24  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  7:30 Alexander Shiyan
2022-05-24  9:03 ` Marco Felsch
2022-05-24  9:21   ` Alexander Shiyan [this message]
2022-05-24 12:03     ` Marco Felsch
2022-05-24 12:28 ` Ahmad Fatoum
2022-05-25  6:23   ` Marco Felsch
2022-05-25  6:27   ` Alexander Shiyan
2022-05-25  8:16     ` Ahmad Fatoum
2022-05-25  8:33       ` Alexander Shiyan
2022-05-25  8:52         ` Ahmad Fatoum
2022-05-30  6:55 ` Sascha Hauer

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=CAP1tNvScB7n4u0HuEkqtM8_KVXy_izWuT2vkRk-bfqfVAjHA4A@mail.gmail.com \
    --to=eagle.alexander923@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=m.felsch@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox