From: nicolas saenz julienne <nsaenz@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Rob Herring <robh+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Maxime Ripard <maxime@cerno.tech>,
devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Mateusz Kwiatkowski <kfyatek+publicgit@gmail.com>
Subject: Re: [PATCH] ARM: dts: bcm283x: Fix VEC address for BCM2711
Date: Mon, 26 Jul 2021 10:30:08 +0200 [thread overview]
Message-ID: <1a9705ff4a4f30b80371f464182ac53a5b16a541.camel@kernel.org> (raw)
In-Reply-To: <1626980528-3835-1-git-send-email-stefan.wahren@i2se.com>
On Thu, 2021-07-22 at 21:02 +0200, Stefan Wahren wrote:
> From: Mateusz Kwiatkowski <kfyatek+publicgit@gmail.com>
>
> The VEC has a different address (0x7ec13000) on the BCM2711 (used in
> e.g. Raspberry Pi 4) compared to BCM283x (e.g. Pi 3 and earlier). This
> was erroneously not taken account for.
>
> Definition of the VEC in the devicetrees had to be moved from
> bcm283x.dtsi to bcm2711.dtsi and bcm2835-common.dtsi to allow for this
> differentiation.
>
> Fixes: 7894bdc6228f ("ARM: boot: dts: bcm2711: Add BCM2711 VEC compatible")
> Signed-off-by: Mateusz Kwiatkowski <kfyatek+publicgit@gmail.com>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
Applied for next.
Thanks,
Nicolas
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-07-26 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 19:02 [PATCH] ARM: dts: bcm283x: Fix VEC address for BCM2711 Stefan Wahren
2021-07-26 8:30 ` nicolas saenz julienne [this message]
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=1a9705ff4a4f30b80371f464182ac53a5b16a541.camel@kernel.org \
--to=nsaenz@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kfyatek+publicgit@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
/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;
as well as URLs for NNTP newsgroup(s).