From: Conor Dooley <conor@kernel.org>
To: Conor Dooley <conor@kernel.org>, linux-riscv@lists.infradead.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Jamie Gibbons <jamie.gibbons@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Aurelien Jarno <aurelien@aurel32.net>,
Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Changhuang Liang <changhuang.liang@starfivetech.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1] riscv: dts: starfive: disable unused csi/camss nodes
Date: Thu, 17 Oct 2024 17:41:50 +0100 [thread overview]
Message-ID: <20241017-bagpipe-mouse-340040a59684@spud> (raw)
In-Reply-To: <20241016-moonscape-tremor-8d41e6f741ff@spud>
From: Conor Dooley <conor.dooley@microchip.com>
On Wed, 16 Oct 2024 21:11:15 +0100, Conor Dooley wrote:
> Aurelien reported probe failures due to the csi node being enabled
> without having a camera attached to it. A camera was in the initial
> submissions, but was removed from the dts, as it had not actually been
> present on the board, but was from an addon board used by the
> developer of the relevant drivers. The non-camera pipeline nodes were
> not disabled when this happened and the probe failures are problematic
> for Debian. Disable them.
>
> [...]
Applied to riscv-soc-fixes, thanks!
[1/1] riscv: dts: starfive: disable unused csi/camss nodes
https://git.kernel.org/conor/c/2e11e78667db
Thanks,
Conor.
prev parent reply other threads:[~2024-10-17 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 20:11 [PATCH v1] riscv: dts: starfive: disable unused csi/camss nodes Conor Dooley
2024-10-17 5:42 ` Aurelien Jarno
2024-10-17 11:01 ` Emil Renner Berthing
2024-10-17 16:41 ` Conor Dooley [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=20241017-bagpipe-mouse-340040a59684@spud \
--to=conor@kernel.org \
--cc=aurelien@aurel32.net \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jamie.gibbons@microchip.com \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox