| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAHCN7xLuJm6_WXFS3eXCf9wF1oyFJFPpEiBMV6UMCAqMRzAqbg@mail.gmail.com>
Date: Sun, 23 Apr 2023 21:29:04 -0500
From: Adam Ford <aford173@...il.com>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: linux-arm-kernel@...ts.infradead.org,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
NXP Linux Team <linux-imx@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: imx8mn: Enable CSI and ISI Nodes
On Sun, Apr 23, 2023 at 7:48 PM Laurent Pinchart
<laurent.pinchart@...asonboard.com> wrote:
>
> On Mon, Apr 24, 2023 at 03:47:13AM +0300, Laurent Pinchart wrote:
> > Hi Adam,
>
> Another comment, do you plan to submit a patch with a camera DT overlay
> for an i.MX8MN board ?
My test repo has the ISI driver working with my OV5640 camera, but for
some reason the mainline doesn't work. I'm trying to figure out
what's different between my test repo and the mainline. I am not
planning on an overlay, as the Beacon baseboard was only designed with
one camera module, a TD Next 5640, based on the OV5640. Newer boards
have been designed with a more generic camera interface, so I plan to
use overlays in the future, but for the imx8mn-beacon-kit, I was
planning to follow a similar design to what was done for the
imx8mm-beacon-kit. They share the same baseboard with a different
processor on the system-on-module.
Do you want me to add a patch to the imx8mn-beacon-kit so there is at
least one user of this driver, once I get my error resolved?
adam
>
> > Thank you for the patch.
> >
> > On Sun, Apr 23, 2023 at 04:26:55PM -0500, Adam Ford wrote:
> > > The CSI in the imx8mn is the same as what is used in the imx8mm,
> > > but it's routed to the ISI on the Nano. Add both the ISI and CSI
> > > nodes, and pointing them to each other. Since the CSI capture is
> > > dependent on an attached camera, mark both ISI and CSI as
> > > disabled by default.
> >
> > I'd then write the subject line as "Add CSI and ISI nodes".
> >
> > > Signed-off-by: Adam Ford <aford173@...il.com>
> > >
> > > diff --git a/arch/arm64/boot/dts/freescale/imx8mn.dtsi b/arch/arm64/boot/dts/freescale/imx8mn.dtsi
> > > index 8be8f090e8b8..102550b41f22 100644
> > > --- a/arch/arm64/boot/dts/freescale/imx8mn.dtsi
> > > +++ b/arch/arm64/boot/dts/freescale/imx8mn.dtsi
> > > @@ -1104,6 +1104,24 @@ dsim_from_lcdif: endpoint {
> > > };
> > > };
> > >
> > > + isi: isi@...20000 {
> > > + compatible = "fsl,imx8mn-isi";
> > > + reg = <0x32e20000 0x100>;
> >
> > The i.MX8MN reference manual documents the ISI registers block size to
> > be 64kB. Should we use the same here, even if all the registers we need
> > are within the first 256 bytes ?
> >
> > > + interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>;
> > > + clocks = <&clk IMX8MN_CLK_DISP_AXI_ROOT>,
> > > + <&clk IMX8MN_CLK_DISP_APB_ROOT>;
> > > + clock-names = "axi", "apb";
> > > + fsl,blk-ctrl = <&disp_blk_ctrl>;
> > > + power-domains = <&disp_blk_ctrl IMX8MN_DISPBLK_PD_ISI>;
> > > + status = "disabled";
> > > +
> > > + port {
> > > + isi_in: endpoint {
> > > + remote-endpoint = <&mipi_csi_out>;
> > > + };
> > > + };
> >
> > This will fail to validate against the ISI DT binding, as they require a
> > "ports" node. When a single port is present using a "port" node directly
> > is fine from an OF graph point of view, but to avoid too much complexity
> > in the ISI binding the consensus was to always require a "ports" node
> > for the ISI.
> >
> > > + };
> > > +
> > > disp_blk_ctrl: blk-ctrl@...28000 {
> > > compatible = "fsl,imx8mn-disp-blk-ctrl", "syscon";
> > > reg = <0x32e28000 0x100>;
> > > @@ -1147,6 +1165,42 @@ disp_blk_ctrl: blk-ctrl@...28000 {
> > > #power-domain-cells = <1>;
> > > };
> > >
> > > + mipi_csi: mipi-csi@...30000 {
> > > + compatible = "fsl,imx8mm-mipi-csi2";
> > > + reg = <0x32e30000 0x1000>;
> > > + interrupts = <GIC_SPI 17 IRQ_TYPE_LEVEL_HIGH>;
> > > + assigned-clocks = <&clk IMX8MN_CLK_CAMERA_PIXEL>,
> > > + <&clk IMX8MN_CLK_CSI1_PHY_REF>;
> > > + assigned-clock-parents = <&clk IMX8MN_SYS_PLL2_1000M>,
> > > + <&clk IMX8MN_SYS_PLL2_1000M>;
> > > + assigned-clock-rates = <333000000>;
> > > + clock-frequency = <333000000>;
> > > + clocks = <&clk IMX8MN_CLK_DISP_APB_ROOT>,
> > > + <&clk IMX8MN_CLK_CAMERA_PIXEL>,
> > > + <&clk IMX8MN_CLK_CSI1_PHY_REF>,
> > > + <&clk IMX8MN_CLK_DISP_AXI_ROOT>;
> > > + clock-names = "pclk", "wrap", "phy", "axi";
> > > + power-domains = <&disp_blk_ctrl IMX8MN_DISPBLK_PD_MIPI_CSI>;
> > > + status = "disabled";
> > > +
> > > + ports {
> > > + #address-cells = <1>;
> > > + #size-cells = <0>;
> > > +
> > > + port@0 {
> > > + reg = <0>;
> > > + };
> > > +
> > > + port@1 {
> > > + reg = <1>;
> > > +
> > > + mipi_csi_out: endpoint {
> > > + remote-endpoint = <&isi_in>;
> > > + };
> > > + };
> > > + };
> > > + };
> > > +
> > > usbotg1: usb@...40000 {
> > > compatible = "fsl,imx8mn-usb", "fsl,imx7d-usb", "fsl,imx27-usb";
> > > reg = <0x32e40000 0x200>;
>
> --
> Regards,
>
> Laurent Pinchart
Powered by blists - more mailing lists