From: Aurelien Jarno <aurelien@aurel32.net>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Jack Zhu <jack.zhu@starfivetech.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
E Shattow <lucent@gmail.com>
Subject: Re: 回复: [v3] riscv: dts: starfive: jh7110: Add camera subsystem nodes
Date: Mon, 14 Oct 2024 22:27:41 +0200 [thread overview]
Message-ID: <Zw1-vcN4CoVkfLjU@aurel32.net> (raw)
In-Reply-To: <ZQ0PR01MB13026F78B2580376095AF7E7F2442@ZQ0PR01MB1302.CHNPR01.prod.partner.outlook.cn>
Hi,
On 2024-10-14 01:08, Changhuang Liang wrote:
> Hi, Aurelien
>
> >
> > Hi,
> >
> > On 2024-02-18 19:27, Changhuang Liang wrote:
> > > Add camera subsystem nodes for the StarFive JH7110 SoC. They contain
> > > the dphy-rx, csi2rx, camss nodes.
> > >
> > > Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> > > ---
> > > .../jh7110-starfive-visionfive-2.dtsi | 49 ++++++++++++++
> > > arch/riscv/boot/dts/starfive/jh7110.dtsi | 67
> > +++++++++++++++++++
> > > 2 files changed, 116 insertions(+)
> >
> > We have been asked to enable CONFIG_VIDEO_STARFIVE_CAMSS in the
> > Debian kernel, which from my understanding and given the device tree shown
> > below also requires enabling CONFIG_VIDEO_CADENCE_CSI2RX. That said
> > doing so triggers the following error in dmesg:
> >
> > [ 25.143282] cdns-csi2rx 19800000.csi: probe with driver cdns-csi2rx
> > failed with error -22
> >
> > From a quick look it seems there is something in the port@0 csi2rx entry. Do
> > you happen to know what is wrong?
> >
>
> You need to add your sensor node. You can refer to this patch:
> https://patchwork.kernel.org/project/linux-riscv/patch/20240119100639.84029-3-changhuang.liang@starfivetech.com/
>
> We suggest that using the imx219
Thanks for your answer. I do not have any sensor attached, the goal is
to build a generic kernel, and people can use overlays or patch their
device tree to add support for additional devices.
In that regard, I have the impression that csi2rx device (and maybe the
camss device?) should not be marked as enabled in the default device
tree. I think they could be enabled by users as part of the change need
to add the sensor node.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://aurel32.net
next prev parent reply other threads:[~2024-10-14 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 1:08 Changhuang Liang
2024-10-14 20:27 ` Aurelien Jarno [this message]
2024-10-14 20:31 ` Conor Dooley
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=Zw1-vcN4CoVkfLjU@aurel32.net \
--to=aurelien@aurel32.net \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jack.zhu@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lucent@gmail.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
all inboxes | Powered by JetHome®