| Message ID | 1559815233-24796-4-git-send-email-louis.kuo@mediatek.com (mailing list archive) |
|---|---|
| State | RFC |
| Headers | show |
| Series | media: support Mediatek sensor interface driver | expand |
Hi, Louis: It looks like that "mediatek,mt8183-seninf" has many common part with "mediatek,mt2712-mipicsi" [1] and "mediatek,mt2712-mipicsi-common" [2]. The evidence comes from each driver. The register definition of mipi_rx phy is "mediatek,mt2712-mipicsi" +#define MIPI_RX_ANA00_CSI 0x00 +#define MIPI_RX_ANA04_CSI 0x04 +#define MIPI_RX_ANA08_CSI 0x08 +#define MIPI_RX_ANA0C_CSI 0x0c +#define MIPI_RX_ANA10_CSI 0x10 +#define MIPI_RX_ANA20_CSI 0x20 +#define MIPI_RX_ANA24_CSI 0x24 "mediatek,mt8183-seninf" +#define MIPI_RX_ANA00_CSI0A 0x0000 +#define MIPI_RX_ANA04_CSI0A 0x0004 +#define MIPI_RX_ANA08_CSI0A 0x0008 +#define MIPI_RX_ANA0C_CSI0A 0x000C +#define MIPI_RX_ANA10_CSI0A 0x0010 +#define MIPI_RX_ANA20_CSI0A 0x0020 +#define MIPI_RX_ANA24_CSI0A 0x0024 The register definition of sensor interface top is "mediatek,mt2712-mipicsi-common" +#define SENINF_TOP_CTRL 0x00 +#define SENINF_TOP_CMODEL_PAR 0x04 +#define SENINF_TOP_MUX 0x08 + +#define SENINF_MUX_CTRL 0x00 "mediatek,mt8183-seninf" +#define SENINF_TOP_CTRL 0x0000 +#define SENINF_TOP_CMODEL_PAR 0x0004 +#define SENINF_TOP_MUX_CTRL 0x0008 +#define rsv_000C 0x000C +#define SENINF_TOP_CAM_MUX_CTRL 0x0010 The register definition of csi is "mediatek,mt2712-mipicsi" +#define SENINF_NCSI2_CTL 0xA0 +#define SENINF_NCSI2_LNRD_TIMING 0xA8 +#define SENINF_NCSI2_INT_EN 0xB0 +#define SENINF_NCSI2_INT_STATUS 0xB4 +#define SENINF_NCSI2_DBG_SEL 0xB8 +#define SENINF_NCSI2_HSRX_DBG 0xD8 +#define SENINF_NCSI2_DI 0xDC +#define SENINF_NCSI2_DI_CTRL 0xE4 "mediatek,mt8183-seninf" +#define SENINF1_CSI2_CTL 0x0A00 +#define SENINF1_CSI2_LNRD_TIMING 0x0A08 +#define SENINF1_CSI2_INT_EN 0x0A10 +#define SENINF1_CSI2_INT_STATUS 0x0A14 +#define SENINF1_CSI2_DGB_SEL 0x0A18 +#define SENINF1_CSI2_HSRX_DBG 0x0A38 +#define SENINF1_CSI2_DI 0x0A3C +#define SENINF1_CSI2_DI_CTRL 0x0A44 Because they have many common part, the common part should be merged and keep the different part for each SoC. Here is an example for common part and different part. Mtk_hdmi_phy (Common part) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/mediatek/mtk_hdmi_phy.c?h=v5.2-rc4 Mtk_hdmi_phy (MT2701 part) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/mediatek/mtk_mt2701_hdmi_phy.c?h=v5.2-rc4 Mtk_hdmi_phy (MT8173 part) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/mediatek/mtk_mt8173_hdmi_phy.c?h=v5.2-rc4 So the first step is to common the binding document. Maybe you should discuss with Stu to achieve this target. [1] https://patchwork.kernel.org/patch/10974567/ [2] https://patchwork.kernel.org/patch/10974559/ Regards, CK On Thu, 2019-06-06 at 18:00 +0800, Louis Kuo wrote: > This patch adds the DT binding documentation for the sensor interface > module in Mediatek SoCs. > > Signed-off-by: Louis Kuo <louis.kuo@mediatek.com> > --- > .../devicetree/bindings/media/mediatek-seninf.txt | 31 ++++++++++++++++++++++ > 1 file changed, 31 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/mediatek-seninf.txt > > diff --git a/Documentation/devicetree/bindings/media/mediatek-seninf.txt b/Documentation/devicetree/bindings/media/mediatek-seninf.txt > new file mode 100644 > index 0000000..979063a > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/mediatek-seninf.txt > @@ -0,0 +1,31 @@ > +* Mediatek seninf MIPI-CSI2 host driver > + > +Seninf MIPI-CSI2 host driver is a HW camera interface controller. It support a widely adopted, > +simple, high-speed protocol primarily intended for point-to-point image and video > +transmission between cameras and host devices. > + > +Required properties: > + - compatible: "mediatek,mt8183-seninf" > + - reg: Must contain an entry for each entry in reg-names. > + - reg-names: Must include the following entries: > + "base_reg": seninf registers base > + "rx_reg": Rx analog registers base > + - interrupts: interrupt number to the cpu. > + - clocks : clock name from clock manager > + - clock-names: must be CLK_CAM_SENINF and CLK_TOP_MUX_SENINF. > + It is the clocks of seninf > + > +Example: > + seninf: seninf@1a040000 { > + compatible = "mediatek,mt8183-seninf"; > + reg = <0 0x1a040000 0 0x8000>, > + <0 0x11C80000 0 0x6000>; > + reg-names = "base_reg", "rx_reg"; > + interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_LOW>; > + power-domains = <&scpsys MT8183_POWER_DOMAIN_CAM>; > + clocks = > + <&camsys CLK_CAM_SENINF>, <&topckgen CLK_TOP_MUX_SENINF>; > + clock-names = > + "CLK_CAM_SENINF", "CLK_TOP_MUX_SENINF"; > + } > +
Hi, Louis: Please translate your Chinese reply into English. I think not all member in the mail list understand Chinese. Regards, CK On Mon, 2019-06-10 at 12:11 +0800, Louis Kuo (郭德寧) wrote: > Hi CK, > > 剛才有跟Stu討論過了, 基本上mt8183 sensor interface driver和MT2712 MIPI-CSI2 driver是兩套不一樣的架構 > > 1. mt8183 sensor interface driver處理raw sensor, mt2712 mipi-csi2 driver處理yuv sensor, register設定不相同. > 2. mt8183 sensor interface driver是獨立的v4l2 sub device, 單純處理phy和mipi-csi2設定, 沒有buffer概念. 後接另外一個isp cam v4l2 driver用來處理及輸出raw image. > 3. mt2712 mipi-csi2 driver則是合併了mipi-csi2和camsv成一個video device, 需要做query buf/request buf/qbuf/dqbuf輸出yuv buffer, 架構設計上不同, > Binding document也無法共用. > > 結論: > 目前這兩套driver無法共用, 請悉知. > > > In MIPI-CSI2 dt-binding for Mediatek MT2712 SoC > > +Example: > > +mipicsi0: mipicsi@10217000 { > > +compatible = "mediatek,mt2712-mipicsi"; > > +mediatek,mipicsi = <&mipicsi>; > > +iommus = <&iommu0 M4U_PORT_CAM_DMA0>, <= mt8183 sensor interface driver單獨做phy和mipi-csi2設定, 沒dma output port > > + <&iommu0 M4U_PORT_CAM_DMA1>; > > +mediatek,larb = <&larb2>; > > +power-domains = <&scpsys MT2712_POWER_DOMAIN_ISP>; > > + > > +mediatek,seninf_mux_camsv = <&seninf1_mux_camsv0 <=mt8183 sensor driver沒有綁camsv driver > > + &seninf2_mux_camsv1 > > + &seninf3_mux_camsv2 > > + &seninf4_mux_camsv3>; > > +reg = <0 0x10217000 0 0x60>, > > + <0 0x15002100 0 0x4>, > > + <0 0x15002300 0 0x100>; > > +mediatek,mipicsiid = <0>; > > +mediatek,mipicsi_max_vc = <4>; <=mt8183 sensor driver不支持vc settings > > +mediatek,serdes_link_reg = <0x49>; > > +}; > > BRs > Louis > > -----Original Message----- > From: Louis Kuo (郭德寧) > Sent: Monday, June 10, 2019 10:57 AM > To: 'CK Hu' <ck.hu@mediatek.com> > Cc: hans.verkuil@cisco.com; laurent.pinchart+renesas@ideasonboard.com; tfiga@chromium.org; keiichiw@chromium.org; matthias.bgg@gmail.com; mchehab@kernel.org; devicetree@vger.kernel.org; Sean Cheng (鄭昇弘) <Sean.Cheng@mediatek.com>; Rynn Wu (吳育恩) <Rynn.Wu@mediatek.com>; srv_heupstream <srv_heupstream@mediatek.com>; Holmes Chiou (邱挺) <holmes.chiou@mediatek.com>; Jerry-ch Chen (陳敬憲) <Jerry-ch.Chen@mediatek.com>; Jungo Lin (林明俊) <jungo.lin@mediatek.com>; Sj Huang (黃信璋) <sj.huang@mediatek.com>; yuzhao@chromium.org; linux-mediatek@lists.infradead.org; zwisler@chromium.org; Christie Yu (游雅惠) <christie.yu@mediatek.com>; Frederic Chen (陳俊元) <frederic.chen@mediatek.com>; linux-arm-kernel@lists.infradead.org; linux-media@vger.kernel.org; Stu Hsieh (謝博鈞) <Stu.Hsieh@mediatek.com> > Subject: RE: [RFC PATCH V3 3/4] dt-bindings: mt8183: Add sensor interface dt-bindings > > Loop more > > -----Original Message----- > From: CK Hu [mailto:ck.hu@mediatek.com] > Sent: Monday, June 10, 2019 10:24 AM > To: Louis Kuo (郭德寧) <louis.kuo@mediatek.com> > Cc: hans.verkuil@cisco.com; laurent.pinchart+renesas@ideasonboard.com; tfiga@chromium.org; keiichiw@chromium.org; matthias.bgg@gmail.com; mchehab@kernel.org; devicetree@vger.kernel.org; Sean Cheng (鄭昇弘) <Sean.Cheng@mediatek.com>; Rynn Wu (吳育恩) <Rynn.Wu@mediatek.com>; srv_heupstream <srv_heupstream@mediatek.com>; Holmes Chiou (邱挺) <holmes.chiou@mediatek.com>; Jerry-ch Chen (陳敬憲) <Jerry-ch.Chen@mediatek.com>; Jungo Lin (林明俊) <jungo.lin@mediatek.com>; Sj Huang (黃信璋) <sj.huang@mediatek.com>; yuzhao@chromium.org; linux-mediatek@lists.infradead.org; zwisler@chromium.org; Christie Yu (游雅惠) <christie.yu@mediatek.com>; Frederic Chen (陳俊元) <Frederic.Chen@mediatek.com>; linux-arm-kernel@lists.infradead.org; linux-media@vger.kernel.org > Subject: Re: [RFC PATCH V3 3/4] dt-bindings: mt8183: Add sensor interface dt-bindings > > Hi, Louis: > > It looks like that "mediatek,mt8183-seninf" has many common part with "mediatek,mt2712-mipicsi" [1] and "mediatek,mt2712-mipicsi-common" [2]. > > The evidence comes from each driver. > > The register definition of mipi_rx phy is > > "mediatek,mt2712-mipicsi" > > +#define MIPI_RX_ANA00_CSI0x00 > +#define MIPI_RX_ANA04_CSI0x04 > +#define MIPI_RX_ANA08_CSI0x08 > +#define MIPI_RX_ANA0C_CSI0x0c > +#define MIPI_RX_ANA10_CSI0x10 > +#define MIPI_RX_ANA20_CSI0x20 > +#define MIPI_RX_ANA24_CSI0x24 > > "mediatek,mt8183-seninf" > > +#define MIPI_RX_ANA00_CSI0A 0x0000 > +#define MIPI_RX_ANA04_CSI0A 0x0004 > +#define MIPI_RX_ANA08_CSI0A 0x0008 > +#define MIPI_RX_ANA0C_CSI0A 0x000C > +#define MIPI_RX_ANA10_CSI0A 0x0010 > +#define MIPI_RX_ANA20_CSI0A 0x0020 > +#define MIPI_RX_ANA24_CSI0A 0x0024 > > The register definition of sensor interface top is > > "mediatek,mt2712-mipicsi-common" > > +#define SENINF_TOP_CTRL0x00 > +#define SENINF_TOP_CMODEL_PAR0x04 > +#define SENINF_TOP_MUX0x08 > + > +#define SENINF_MUX_CTRL0x00 > > "mediatek,mt8183-seninf" > > +#define SENINF_TOP_CTRL 0x0000 > +#define SENINF_TOP_CMODEL_PAR 0x0004 > +#define SENINF_TOP_MUX_CTRL 0x0008 > +#define rsv_000C 0x000C > +#define SENINF_TOP_CAM_MUX_CTRL 0x0010 > > The register definition of csi is > > "mediatek,mt2712-mipicsi" > > +#define SENINF_NCSI2_CTL0xA0 > +#define SENINF_NCSI2_LNRD_TIMING0xA8 > +#define SENINF_NCSI2_INT_EN0xB0 > +#define SENINF_NCSI2_INT_STATUS0xB4 > +#define SENINF_NCSI2_DBG_SEL0xB8 > +#define SENINF_NCSI2_HSRX_DBG0xD8 > +#define SENINF_NCSI2_DI0xDC > +#define SENINF_NCSI2_DI_CTRL0xE4 > > "mediatek,mt8183-seninf" > > +#define SENINF1_CSI2_CTL 0x0A00 > +#define SENINF1_CSI2_LNRD_TIMING 0x0A08 > +#define SENINF1_CSI2_INT_EN 0x0A10 > +#define SENINF1_CSI2_INT_STATUS 0x0A14 > +#define SENINF1_CSI2_DGB_SEL 0x0A18 > +#define SENINF1_CSI2_HSRX_DBG 0x0A38 > +#define SENINF1_CSI2_DI 0x0A3C > +#define SENINF1_CSI2_DI_CTRL 0x0A44 > > Because they have many common part, the common part should be merged and keep the different part for each SoC. Here is an example for common part and different part. > > Mtk_hdmi_phy (Common part) > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/mediatek/mtk_hdmi_phy.c?h=v5.2-rc4 > Mtk_hdmi_phy (MT2701 part) > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/mediatek/mtk_mt2701_hdmi_phy.c?h=v5.2-rc4 > Mtk_hdmi_phy (MT8173 part) > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/mediatek/mtk_mt8173_hdmi_phy.c?h=v5.2-rc4 > > So the first step is to common the binding document. Maybe you should discuss with Stu to achieve this target. > > [1] https://patchwork.kernel.org/patch/10974567/ > [2] https://patchwork.kernel.org/patch/10974559/ > > Regards, > CK > > On Thu, 2019-06-06 at 18:00 +0800, Louis Kuo wrote: > > This patch adds the DT binding documentation for the sensor interface > > module in Mediatek SoCs. > > > > Signed-off-by: Louis Kuo <louis.kuo@mediatek.com> > > --- > > .../devicetree/bindings/media/mediatek-seninf.txt | 31 > > ++++++++++++++++++++++ > > 1 file changed, 31 insertions(+) > > create mode 100644 > > Documentation/devicetree/bindings/media/mediatek-seninf.txt > > > > diff --git > > a/Documentation/devicetree/bindings/media/mediatek-seninf.txt > > b/Documentation/devicetree/bindings/media/mediatek-seninf.txt > > new file mode 100644 > > index 0000000..979063a > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/media/mediatek-seninf.txt > > @@ -0,0 +1,31 @@ > > +* Mediatek seninf MIPI-CSI2 host driver > > + > > +Seninf MIPI-CSI2 host driver is a HW camera interface controller. It > > +support a widely adopted, simple, high-speed protocol primarily > > +intended for point-to-point image and video transmission between cameras and host devices. > > + > > +Required properties: > > + - compatible: "mediatek,mt8183-seninf" > > + - reg: Must contain an entry for each entry in reg-names. > > + - reg-names: Must include the following entries: > > + "base_reg": seninf registers base > > + "rx_reg": Rx analog registers base > > + - interrupts: interrupt number to the cpu. > > + - clocks : clock name from clock manager > > + - clock-names: must be CLK_CAM_SENINF and CLK_TOP_MUX_SENINF. > > + It is the clocks of seninf > > + > > +Example: > > +seninf: seninf@1a040000 { > > +compatible = "mediatek,mt8183-seninf"; > > +reg = <0 0x1a040000 0 0x8000>, > > + <0 0x11C80000 0 0x6000>; > > +reg-names = "base_reg", "rx_reg"; > > +interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_LOW>; > > +power-domains = <&scpsys MT8183_POWER_DOMAIN_CAM>; > > +clocks = > > +<&camsys CLK_CAM_SENINF>, <&topckgen CLK_TOP_MUX_SENINF>; > > +clock-names = > > +"CLK_CAM_SENINF", "CLK_TOP_MUX_SENINF"; > > +} > > + > > > *********************MEDIATEK Confidential/Internal Use*********************
Hi Louis, On Thu, Jun 06, 2019 at 06:00:32PM +0800, Louis Kuo wrote: > This patch adds the DT binding documentation for the sensor interface > module in Mediatek SoCs. > > Signed-off-by: Louis Kuo <louis.kuo@mediatek.com> > --- > .../devicetree/bindings/media/mediatek-seninf.txt | 31 ++++++++++++++++++++++ > 1 file changed, 31 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/mediatek-seninf.txt > > diff --git a/Documentation/devicetree/bindings/media/mediatek-seninf.txt b/Documentation/devicetree/bindings/media/mediatek-seninf.txt > new file mode 100644 > index 0000000..979063a > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/mediatek-seninf.txt > @@ -0,0 +1,31 @@ > +* Mediatek seninf MIPI-CSI2 host driver Note that DT bindings document the hardware, not the driver implementation. > + > +Seninf MIPI-CSI2 host driver is a HW camera interface controller. It support a widely adopted, Same here; driver apparently refers to software. Please wrap before or at 80 characters per line. > +simple, high-speed protocol primarily intended for point-to-point image and video > +transmission between cameras and host devices. Could you elaborate the properties of the hardware in a bit more detail, such as how many ports there are and how many lanes they can support? See e.g. Documentation/devicetree/bindings/media/ti,omap3isp.txt . Please also refer to video-interfaces.txt and document the port nodes and the relevant properties in the endpoint nodes, as in the binding example I referred to. > + > +Required properties: > + - compatible: "mediatek,mt8183-seninf" > + - reg: Must contain an entry for each entry in reg-names. > + - reg-names: Must include the following entries: > + "base_reg": seninf registers base > + "rx_reg": Rx analog registers base > + - interrupts: interrupt number to the cpu. > + - clocks : clock name from clock manager > + - clock-names: must be CLK_CAM_SENINF and CLK_TOP_MUX_SENINF. > + It is the clocks of seninf > + > +Example: > + seninf: seninf@1a040000 { > + compatible = "mediatek,mt8183-seninf"; > + reg = <0 0x1a040000 0 0x8000>, > + <0 0x11C80000 0 0x6000>; > + reg-names = "base_reg", "rx_reg"; > + interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_LOW>; > + power-domains = <&scpsys MT8183_POWER_DOMAIN_CAM>; > + clocks = > + <&camsys CLK_CAM_SENINF>, <&topckgen CLK_TOP_MUX_SENINF>; Please wrap before 80 and align the above two lines. > + clock-names = > + "CLK_CAM_SENINF", "CLK_TOP_MUX_SENINF"; No need to wrap here. > + } > + > -- > 1.9.1 This must be old.
diff --git a/Documentation/devicetree/bindings/media/mediatek-seninf.txt b/Documentation/devicetree/bindings/media/mediatek-seninf.txt new file mode 100644 index 0000000..979063a --- /dev/null +++ b/Documentation/devicetree/bindings/media/mediatek-seninf.txt @@ -0,0 +1,31 @@ +* Mediatek seninf MIPI-CSI2 host driver + +Seninf MIPI-CSI2 host driver is a HW camera interface controller. It support a widely adopted, +simple, high-speed protocol primarily intended for point-to-point image and video +transmission between cameras and host devices. + +Required properties: + - compatible: "mediatek,mt8183-seninf" + - reg: Must contain an entry for each entry in reg-names. + - reg-names: Must include the following entries: + "base_reg": seninf registers base + "rx_reg": Rx analog registers base + - interrupts: interrupt number to the cpu. + - clocks : clock name from clock manager + - clock-names: must be CLK_CAM_SENINF and CLK_TOP_MUX_SENINF. + It is the clocks of seninf + +Example: + seninf: seninf@1a040000 { + compatible = "mediatek,mt8183-seninf"; + reg = <0 0x1a040000 0 0x8000>, + <0 0x11C80000 0 0x6000>; + reg-names = "base_reg", "rx_reg"; + interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_LOW>; + power-domains = <&scpsys MT8183_POWER_DOMAIN_CAM>; + clocks = + <&camsys CLK_CAM_SENINF>, <&topckgen CLK_TOP_MUX_SENINF>; + clock-names = + "CLK_CAM_SENINF", "CLK_TOP_MUX_SENINF"; + } +
This patch adds the DT binding documentation for the sensor interface module in Mediatek SoCs. Signed-off-by: Louis Kuo <louis.kuo@mediatek.com> --- .../devicetree/bindings/media/mediatek-seninf.txt | 31 ++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/mediatek-seninf.txt