From: Arnd Bergmann <arnd@kernel.org>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Rob Herring <robh+dt@kernel.org>, SoC Team <soc@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Krzysztof Kozlowski <krzk@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: picoxcell: fix missing interrupt-parent properties
Date: Sat, 2 Jan 2021 11:54:15 +0100 [thread overview]
Message-ID: <CAK8P3a3TR3qzJ2JP8-mFHtEA0sqDYeuG5vR6W1_XGzWF-S0-YA@mail.gmail.com> (raw)
In-Reply-To: <20201231124946.GA2918779@willow>
On Thu, Dec 31, 2020 at 1:49 PM Jamie Iles <jamie@jamieiles.com> wrote:
>
> Hi Arnd,
>
> On Wed, Dec 30, 2020 at 04:20:05PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > dtc points out that the interrupts for some devices are not parsable:
> >
> > picoxcell-pc3x2.dtsi:45.19-49.5: Warning (interrupts_property): /paxi/gem@30000: Missing interrupt-parent
> > picoxcell-pc3x2.dtsi:51.21-55.5: Warning (interrupts_property): /paxi/dmac@40000: Missing interrupt-parent
> > picoxcell-pc3x2.dtsi:57.21-61.5: Warning (interrupts_property): /paxi/dmac@50000: Missing interrupt-parent
> > picoxcell-pc3x2.dtsi:233.21-237.5: Warning (interrupts_property): /rwid-axi/axi2pico@c0000000: Missing interrupt-parent
> >
> > There are two VIC instances, so it's not clear which one needs to be
> > used. I found the BSP sources that reference VIC0, so use that:
> >
> > https://github.com/r1mikey/meta-picoxcell/blob/master/recipes-kernel/linux/linux-picochip-3.0/0001-picoxcell-support-for-Picochip-picoXcell-SoC.patch
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Rob has a series to remove Picoxcell as there's no active development on
> this anymore and Intel have stopped producing the chips.
Right, I am aware of Rob's series. My patch was a little older but I only got
around to submitting it now. I'd still like to merge it as a bugfix for v5.11
though and have it backported to avoid the warnings with new dtc on
stable kernels, while doing the platform removal for v5.12.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Jamie Iles <jamie@jamieiles.com>
Cc: DTML <devicetree@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>, SoC Team <soc@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: picoxcell: fix missing interrupt-parent properties
Date: Sat, 2 Jan 2021 11:54:15 +0100 [thread overview]
Message-ID: <CAK8P3a3TR3qzJ2JP8-mFHtEA0sqDYeuG5vR6W1_XGzWF-S0-YA@mail.gmail.com> (raw)
Message-ID: <20210102105415.afZOx-QE3CLsbgnIUjnjK3wGb29oNyOY0-O_D3v5UUw@z> (raw)
In-Reply-To: <20201231124946.GA2918779@willow>
On Thu, Dec 31, 2020 at 1:49 PM Jamie Iles <jamie@jamieiles.com> wrote:
>
> Hi Arnd,
>
> On Wed, Dec 30, 2020 at 04:20:05PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > dtc points out that the interrupts for some devices are not parsable:
> >
> > picoxcell-pc3x2.dtsi:45.19-49.5: Warning (interrupts_property): /paxi/gem@30000: Missing interrupt-parent
> > picoxcell-pc3x2.dtsi:51.21-55.5: Warning (interrupts_property): /paxi/dmac@40000: Missing interrupt-parent
> > picoxcell-pc3x2.dtsi:57.21-61.5: Warning (interrupts_property): /paxi/dmac@50000: Missing interrupt-parent
> > picoxcell-pc3x2.dtsi:233.21-237.5: Warning (interrupts_property): /rwid-axi/axi2pico@c0000000: Missing interrupt-parent
> >
> > There are two VIC instances, so it's not clear which one needs to be
> > used. I found the BSP sources that reference VIC0, so use that:
> >
> > https://github.com/r1mikey/meta-picoxcell/blob/master/recipes-kernel/linux/linux-picochip-3.0/0001-picoxcell-support-for-Picochip-picoXcell-SoC.patch
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Rob has a series to remove Picoxcell as there's no active development on
> this anymore and Intel have stopped producing the chips.
Right, I am aware of Rob's series. My patch was a little older but I only got
around to submitting it now. I'd still like to merge it as a bugfix for v5.11
though and have it backported to avoid the warnings with new dtc on
stable kernels, while doing the platform removal for v5.12.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-02 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:20 [PATCH] ARM: picoxcell: fix missing interrupt-parent properties Arnd Bergmann
2020-12-30 15:20 ` Arnd Bergmann
2020-12-31 12:49 ` Jamie Iles
2020-12-31 12:49 ` Jamie Iles
2021-01-02 10:54 ` Arnd Bergmann [this message]
2021-01-02 10:54 ` Arnd Bergmann
2021-01-02 18:03 ` Jamie Iles
2021-01-02 18:03 ` Jamie Iles
2021-01-08 15:30 ` patchwork-bot+linux-soc
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=CAK8P3a3TR3qzJ2JP8-mFHtEA0sqDYeuG5vR6W1_XGzWF-S0-YA@mail.gmail.com \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jamie@jamieiles.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.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 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.