Devicetree
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paulk@sys-base.io>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: linux-sunxi@lists.linux.dev, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org,
	sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH v9 5/9] ARM: dts: sun8i: v3s: Add nodes for MIPI CSI-2 support
Date: Sat, 13 Jun 2026 16:11:59 +0200	[thread overview]
Message-ID: <ai1lLxu9rFYfeUEF@collins> (raw)
In-Reply-To: <ahWqcWy_6QuNIOi-@shepard>

[-- Attachment #1: Type: text/plain, Size: 3109 bytes --]

Hi Chen-Yu,

Le Tue 26 May 26, 16:13, Paul Kocialkowski a écrit :
> > > > +                     reg = <0x01cb2000 0x1000>;
> > > > +                     clocks = <&ccu CLK_BUS_CSI>,
> > > > +                              <&ccu CLK_MIPI_CSI>;
> > > > +                     clock-names = "bus", "mod";
> > > > +                     resets = <&ccu RST_BUS_CSI>;
> > >
> > > Will this node fail dtbs_check schema validation? The existing device tree
> > > binding schema for "allwinner,sun6i-a31-mipi-dphy" requires an interrupts
> > > property, which appears to be missing here.
> > 
> > Yeah, this is definitely going to fail validation.
> 
> To be very clear about this, the interrupt is absolutely not required for
> proper operation of the unit and there's a chance we might eventually see
> a SoC that doesn't have it wired.
> 
> I could just hook the interrupt for now and we could make it optional if ever
> needed, but I could also mark is as optional now if you prefer.
> 
> > > If the V3s hardware physically lacks a D-PHY interrupt, would it be better
> > > to add the V3s-specific compatible string and update the binding schema
> > > to make the interrupts property conditionally optional for the V3s?
> > 
> > FWIW the vendor kernel has some code for the D-PHY's interrupt bits [1].
> > Could you add the interrupt (I'm guessing the MIPI-CSI interrupt?) and
> > give it a quick test?
> 
> Thanks for digging this up! It really looks like it's just used for debug
> purposes.
> 
> I have previously used the mipi csi-2 interrupt for the mipi csi-2 controller
> and never for the d-phy. There's a chance it's the same interrupt that is wired
> to both units (like it is for isp/csi).
> 
> I'll give it a try when I get back home. If it doesn't trigger, it probbaly
> means it's not wired to the d-phy and should really be made optional.

I just tested it: the interrupt is wired to both the mipi csi-2 and d-phy
units and triggers when interrupt enable bits are set on the d-phy.

So I will just add it to the d-phy node and keep the property marked as
mandatory in the binding.

All the best,

Paul

> > Thanks
> > ChenYu
> > 
> > [1] https://github.com/gediz/v3s-linux-sdk/blob/master/linux-3.4/drivers/media/video/sunxi-vfe/mipi_csi/dphy/dphy_reg.c
> > 
> > 
> > > > +                     allwinner,direction = "rx";
> > > > +                     status = "disabled";
> > > > +                     #phy-cells = <0>;
> > > > +             };
> > > > +
> > >
> > > --
> > > Sashiko AI review · https://sashiko.dev/#/patchset/20260518153339.619947-1-paulk@sys-base.io?part=5
> > >
> 
> -- 
> Paul Kocialkowski,
> 
> Independent contractor - sys-base - https://www.sys-base.io/
> Free software developer - https://www.paulk.fr/
> 
> Expert in multimedia, graphics and embedded hardware support with Linux.



-- 
Paul Kocialkowski,

Independent contractor - sys-base - https://www.sys-base.io/
Free software developer - https://www.paulk.fr/

Expert in multimedia, graphics and embedded hardware support with Linux.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-06-13 14:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 15:33 [PATCH v9 0/9] Allwinner A31/A83T MIPI CSI-2 and A31 ISP / Platform Support Paul Kocialkowski
2026-05-18 15:33 ` [PATCH v9 1/9] dt-bindings: media: sun6i-a31-csi: Add optional interconnect properties Paul Kocialkowski
2026-05-18 15:33 ` [PATCH v9 2/9] dt-bindings: media: sun6i-a31-isp: " Paul Kocialkowski
2026-05-18 15:50   ` sashiko-bot
2026-05-18 15:59     ` Paul Kocialkowski
2026-05-18 15:33 ` [PATCH v9 3/9] clk: sunxi-ng: v3s: Export MBUS and DRAM clocks to the public header Paul Kocialkowski
2026-05-18 15:33 ` [PATCH v9 4/9] ARM: dts: sun8i: v3s: Add mbus node to represent the interconnect Paul Kocialkowski
2026-05-18 15:33 ` [PATCH v9 5/9] ARM: dts: sun8i: v3s: Add nodes for MIPI CSI-2 support Paul Kocialkowski
2026-05-18 16:11   ` sashiko-bot
2026-05-24 17:49     ` Chen-Yu Tsai
2026-05-26 14:13       ` Paul Kocialkowski
2026-06-13 14:11         ` Paul Kocialkowski [this message]
2026-05-18 15:33 ` [PATCH v9 6/9] ARM: dts: sun8i: v3s: Add support for the ISP Paul Kocialkowski
2026-05-18 15:33 ` [PATCH v9 7/9] ARM: dts: sun8i: a83t: Add MIPI CSI-2 controller node Paul Kocialkowski
2026-05-18 15:33 ` [PATCH v9 8/9] ARM: dts: sun8i-a83t: Add BananaPi M3 OV5640 camera overlay Paul Kocialkowski
2026-05-24 20:24   ` Chen-Yu Tsai
2026-05-18 15:33 ` [PATCH v9 9/9] ARM: dts: sun8i-a83t: Add BananaPi M3 OV8865 " Paul Kocialkowski
2026-05-18 17:10   ` sashiko-bot
2026-05-24 19:36 ` (subset) [PATCH v9 0/9] Allwinner A31/A83T MIPI CSI-2 and A31 ISP / Platform Support Chen-Yu Tsai
2026-05-24 20:26 ` Chen-Yu Tsai

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=ai1lLxu9rFYfeUEF@collins \
    --to=paulk@sys-base.io \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wens@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