mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: DTS: myir-x335x: Add GPIO aliases
Date: Wed, 25 May 2022 11:33:03 +0300	[thread overview]
Message-ID: <CAP1tNvTqa-qVTBCR1QQptsfvgTWsWNCEGSFG+ZnvNrBT62cabg@mail.gmail.com> (raw)
In-Reply-To: <1db17488-d759-712a-6014-8d2cde412474@pengutronix.de>

ср, 25 мая 2022 г. в 11:16, Ahmad Fatoum <a.fatoum@pengutronix.de>:
> On 25.05.22 08:27, Alexander Shiyan wrote:
> > вт, 24 мая 2022 г. в 15:28, Ahmad Fatoum <a.fatoum@pengutronix.de>:
> >> On 24.05.22 09:30, Alexander Shiyan wrote:
> >>> For the correct work of GPIO driver, we need to define aliases.
> >>> Let's add them to the devicetree.
> > ...
> >>> diff --git a/arch/arm/dts/am335x-myirtech-myd.dts b/arch/arm/dts/am335x-myirtech-myd.dts
> >>> index 6ec65e533d..1ea0f2a440 100644
> >>> --- a/arch/arm/dts/am335x-myirtech-myd.dts
> >>> +++ b/arch/arm/dts/am335x-myirtech-myd.dts
> >>> @@ -6,6 +6,13 @@
> >>>  #include <arm/am335x-myirtech-myd.dts>
> >>
> >> Other boards do #include "am33xx.dtsi", which takes care of these
> >> aliases. It's probably better you include that too.
> >
> > Including this file results in an error.
> >
> > Changed to:
> > #include "am33xx.dtsi"
> > #include <arm/am335x-myirtech-myd.dts>
> >
> > Output:
> > DTC     arch/arm/dts/am335x-myirtech-myd.dtb
> > Error: /home/ARM/barebox/dts/src/arm/am335x-myirtech-myd.dts:6.1-9 syntax error
> > FATAL ERROR: Unable to parse input tree
> >
> > Most likely this is the result of double inclusion of the file arm/am33xx.dtsi,
> > first time from "am33xx.dtsi" and second from arm/am335x-myirtech-myd.dts.
>
> Hi, you need to include if after the upstream DT. That's why it doesn't have
> a /dts-v1/;

Yes, if "am33xx.dtsi" is after <arm/am335x-myirtech-myd.dts>, it compiles fine.
But in this case, upstreaming <arm/am33xx.dtsi> (from local
am33xx.dtsi) overwrites
any binding changes from the board file.

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

  reply	other threads:[~2022-05-25  8:34 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
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 [this message]
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=CAP1tNvTqa-qVTBCR1QQptsfvgTWsWNCEGSFG+ZnvNrBT62cabg@mail.gmail.com \
    --to=eagle.alexander923@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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