Hi ThierryCurrently all channels allocation and creating media links are all in vi init client ops.
So just populating CSI child from VI with moving CSI as child node to VI for Tegra210 should work.
Will have all the fixes in v2 along with link_validate implementations and merging files to have it simpler.
Thanks Sowjanya On 1/30/20 12:18 PM, Sowjanya Komatineni wrote:
On 1/30/20 10:58 AM, Sowjanya Komatineni wrote:On 1/30/20 9:58 AM, Thierry Reding wrote:Yes we need CSI structure for hard link TPG also as all csi channel list is part of CSI device.On Thu, Jan 30, 2020 at 09:18:50AM -0800, Sowjanya Komatineni wrote:On 1/30/20 4:36 AM, Thierry Reding wrote:On Wed, Jan 29, 2020 at 08:22:48AM -0800, Sowjanya Komatineni wrote:From our discussion, my understanding was that CSI would be a separate device, but it would still be a subdevice of VI. The address offset ofOn 1/29/20 1:46 AM, Thierry Reding wrote:On Tue, Jan 28, 2020 at 10:23:21AM -0800, Sowjanya Komatineni wrote:Can this be a child of the vi node? Looking at the register ranges it seems like these are actually a single IP block. If they have separate blocks with clearly separate functionality, then it makes sense to have CSI be a child node of VI, though it may also be okay to merge both andTegra210 contains VI controller for video input capture from MIPICSI camera sensors and also supports built-in test pattern generator.CSI ports can be one-to-one mapped to VI channels for capturing froman external sensor or from built-in test pattern generator.This patch adds support for VI and CSI and enables them in Tegra210device tree. Signed-off-by: Sowjanya Komatineni <skomatineni@xxxxxxxxxx> --- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 8 +++++++arch/arm64/boot/dts/nvidia/tegra210.dtsi | 31 +++++++++++++++++++++++++-2 files changed, 38 insertions(+), 1 deletion(-)diff --git a/arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi b/arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsiindex b0095072bc28..ec1b3033fa03 100644 --- a/arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi +++ b/arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi @@ -10,6 +10,14 @@ status = "okay"; }; + vi@54080000 { + status = "okay"; + }; + + csi@0x54080838 { + status = "okay"; + }; + sor@54580000 { status = "okay";diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi b/arch/arm64/boot/dts/nvidia/tegra210.dtsiindex 48c63256ba7f..c6107ec03ad1 100644 --- a/arch/arm64/boot/dts/nvidia/tegra210.dtsi +++ b/arch/arm64/boot/dts/nvidia/tegra210.dtsi @@ -136,9 +136,38 @@ vi@54080000 { compatible = "nvidia,tegra210-vi"; - reg = <0x0 0x54080000 0x0 0x00040000>; + reg = <0x0 0x54080000 0x0 0x808>; interrupts = <GIC_SPI 69 IRQ_TYPE_LEVEL_HIGH>; status = "disabled"; + assigned-clocks = <&tegra_car TEGRA210_CLK_VI>;+ assigned-clock-parents = <&tegra_car TEGRA210_CLK_PLL_C4_OUT0>;+ + clocks = <&tegra_car TEGRA210_CLK_VI>; + clock-names = "vi"; + resets = <&tegra_car 20>; + reset-names = "vi"; + }; + + csi@0x54080838 { + compatible = "nvidia,tegra210-csi"; + reg = <0x0 0x54080838 0x0 0x2000>; + status = "disabled"; + assigned-clocks = <&tegra_car TEGRA210_CLK_CILAB>, + <&tegra_car TEGRA210_CLK_CILCD>, + <&tegra_car TEGRA210_CLK_CILE>;+ assigned-clock-parents = <&tegra_car TEGRA210_CLK_PLL_P>,+ <&tegra_car TEGRA210_CLK_PLL_P>, + <&tegra_car TEGRA210_CLK_PLL_P>; + assigned-clock-rates = <102000000>, + <102000000>, + <102000000>; + + clocks = <&tegra_car TEGRA210_CLK_CSI>, + <&tegra_car TEGRA210_CLK_CILAB>, + <&tegra_car TEGRA210_CLK_CILCD>, + <&tegra_car TEGRA210_CLK_CILE>; + clock-names = "csi", "cilab", "cilcd", "cile"; + };have a single node with the driver doing all of the differentiation between what's VI and what's CSI.Looking at later chips, the split between VI and CSI is more explicit, so having the split in DT for Tegra210 may make sense for consistency.I know we've discussed this before, but for some reason I keep coming back to this. I'll go through the other patches to see if I can get aclearer picture of how this could all work together. ThierryWe can keep it separate as we discussed.But as Tegra186 onwards, CSI is separate device to be all cosistent I keptCSI as separate node for Tegra210 as well.the CSI registers not being aligned to a power of two is a strong indication that this is really all part of the same block.Yes our earlier discussion is to have CSI as subdevice.Later looking into T186 and later NVCSI is totally separate so it will beseparate device and to have driver common moved Tegra210 CSI also as separate device instead of having it as subdevice of VI. Earlier when we discussed at that time I am using TPG also from device graphs but not moved to hard media links inside driver for TPG. For this we need CSI to be available prior to VI.Why is that? Does creating the hard media links need access to a struct device? What if we created that device in the VI driver without any reliance on DT? Shouldn't that also work? I have a hard time imagining that there aren't other devices like this where we don't necessarily have separate devices for these links.We can create CSI channel subdevices within VI without using CSI device from a separate CSI driver probe for Tegra210 and make all subdev related ops implementations as global so they can be used from VI driver for Tegra210 and can also be used for Tegra186 and later in separate CSI driver.During creating media links in VI driver for TPG, for T210 we can use local CSI device structure and for T186+ we can use CSI device structure created during CSI probe.Sorry, I didn't understood what you meant by separate devices for these link.We only have Tegra CSI linked to Tegra VI for TPG/Real sensor.If we add CSI as subdevice to VI, CSI will not be available by the timeThe CSI subdevice should be registered as part of the VI driver's probe,VI init happens.right? That's typically where you'd call of_platform_populate(). Could we not set up the hard media links in the ->init() callbacks for the host1x clients? Those are called after all of the devices have been probed, so the CSI device should be available at that time.yes, will update to have CSI as child node to VICurrently host1x subdevices listed has CSI before VI and CSI init happens earlier so by the time VI init happens CSI is available to do media linksOkay, I understand how this would be a convenient solution. However, the device tree is a hardware description, so we need to ignore what we knowb/w VI video entity and CSI subdevice entity.about the operating system infrastructure that we want to use when writing the device tree bindings (and the device tree content) in order to make sure the same binding will work on a different operating system which may have a completely different infrastructure (or none at all).Also having CSI as separate subdevice (not as subdevice to VI) for T210 willbe consistent with T186 and later.Again, I see how that's convenient. But the main difference between Tegra210 and Tegra186 is that on the former, the CSI is merged with VI, whereas on the latter the CSI is a completely separate hardware block. Since device tree describes the hardware, that difference should be apparent in the device tree. I initially thought as well that it would be advantageous if both had the same representation, but I do realize now that this has a significant impact on the device tree, and it violates the basic principles we base device tree binding design on. ThierryI just thought of driver implementation being common b/w T210 and T186+ by having CSI as separate device node rather than as child node to VI to avoid CSI structure handling within VI for T210 only.Will update DT and driver to have CSI as child node of VI for T210.
