From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Eric Anholt <eric@anholt.net>
Cc: Rob Herring <robh+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: bcm283x: Disable dsi0 node
Date: Thu, 16 Apr 2020 11:36:11 +0200 [thread overview]
Message-ID: <aa03258a2db37293b4be56dcd2b3f5f32665c6dc.camel@suse.de> (raw)
In-Reply-To: <CADaigPXwfjd-HoOtBm_fuPQ9eh7AKTaJx+ocLsppPFdL3Cr4jg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Wed, 2020-04-15 at 12:17 -0700, Eric Anholt wrote:
> On Wed, Apr 15, 2020 at 7:42 AM Nicolas Saenz Julienne
> <nsaenzjulienne@suse.de> wrote:
> > Since its inception the module was meant to be disabled by default, but
> > the original commit failed to add the relevant property.
> >
> > Fixes: 4aba4cf82054 ("ARM: dts: bcm2835: Add the DSI module nodes and
> > clocks")
> > Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> > ---
> > arch/arm/boot/dts/bcm283x.dtsi | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi
> > index e1abe8c730cef..b83a864e2e8ba 100644
> > --- a/arch/arm/boot/dts/bcm283x.dtsi
> > +++ b/arch/arm/boot/dts/bcm283x.dtsi
> > @@ -372,6 +372,7 @@ dsi0: dsi@7e209000 {
> > "dsi0_ddr2",
> > "dsi0_ddr";
> >
> > + status = "disabled";
> > };
>
> If you've confirmed that vc4 still probes,
Confirmed.
> Reviewed-by: Eric Anholt <eric@anholt.net>
Thanks,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-16 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 14:42 [PATCH] ARM: dts: bcm283x: Disable dsi0 node Nicolas Saenz Julienne
2020-04-15 19:17 ` Eric Anholt
2020-04-16 9:36 ` Nicolas Saenz Julienne [this message]
2020-04-16 20:58 ` Florian Fainelli
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=aa03258a2db37293b4be56dcd2b3f5f32665c6dc.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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).