Support for Tegra video capture from external sensor
Subsystems (10)
Sowjanya Komatineni
maintainerv2 cover Support for Tegra video capture from external sensor
This series adds support for video capture from external camera sensor to Tegra video driver.
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.
Tegra video driver updates
- TPG Vs Non-TPG based on Kconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.
Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.
Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.
Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Update tegra_mipi_request() to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer before clk_disable.
Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and
power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path in tegra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoid tegra_i2c_init_dma() for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Update tegra_mipi_request() to be node based
gpu: host1x: mipi: Split tegra_mipi_calibrate and tegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano
.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++ arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770 +++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +- 16 files changed, 1251 insertions(+), 100 deletions(-)
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 1/18 dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and power-domains
This patch documents missing clocks and power-domains of Tegra210 VI I2C.
--- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-)
Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.txt +13 -6
@@ -35,12 +35,12 @@ Required properties: Due to above changes, Tegra114 I2C driver makes incompatible with previous hardware driver. Hence, tegra114 I2C controller is compatible with "nvidia,tegra114-i2c". - nvidia,tegra210-i2c-vi: Tegra210 has one I2C controller that is part of the - host1x domain and typically used for camera use-cases. This VI I2C - controller is mostly compatible with the programming model of the - regular I2C controllers with a few exceptions. The I2C registers start - at an offset of 0xc00 (instead of 0), registers are 16 bytes apart - (rather than 4) and the controller does not support slave mode. + nvidia,tegra210-i2c-vi: Tegra210 has one I2C controller that is on host1x bus + and is part of VE power domain and typically used for camera use-cases. + This VI I2C controller is mostly compatible with the programming model + of the regular I2C controllers with a few exceptions. The I2C registers + start at an offset of 0xc00 (instead of 0), registers are 16 bytes + apart (rather than 4) and the controller does not support slave mode. - reg: Should contain I2C controller registers physical address and length. - interrupts: Should contain I2C controller interrupts. - address-cells: Address cells for I2C device address.
@@ -53,10 +53,17 @@ Required properties: - fast-clk Tegra114: - div-clk + Tegra210: + - div-clk + - slow (only for nvidia,tegra210-i2c-vi compatible node) - resets: Must contain an entry for each entry in reset-names. See ../reset/reset.txt for details. - reset-names: Must include the following entries: - i2c +- power-domains: Only for nvidia,tegra210-i2c-vi compatible node and must + include venc powergate node as vi i2c is part of VE power domain. + tegra210-i2c-vi: + - pd_venc - dmas: Must contain an entry for each entry in clock-names. See ../dma/dma.txt for details. - dma-names: Must include the following entries:
Signature · 1 line
2.7.4
Re: [RFC PATCH v2 01/18] dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and power-domains
Quoted 7 lines · Sowjanya Komatineni
This patch documents missing clocks and power-domains of Tegra210 VI I2C.
Signed-off-by Sowjanya Komatineni <[email protected]>--- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-)
Sowjanya Komatineni
maintainerRFC PATCH v2 2/18 arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
In reply to Sowjanya KomatineniTegra210 VI I2C is in VE power domain and i2c-vi node should have power-domains property.
Current Tegra210 i2c-vi device node is missing both VI I2C clocks and power-domains property.
This patch adds them.
--- arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 ++++++ 1 file changed, 6 insertions(+)
arch/arm64/boot/dts/nvidia/tegra210.dtsi +6 -0
@@ -376,6 +376,12 @@ compatible = "nvidia,tegra210-i2c-vi"; reg = <0x0 0x546c0000 0x0 0x00040000>; interrupts = <GIC_SPI 17 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&tegra_car TEGRA210_CLK_VI_I2C>, + <&tegra_car TEGRA210_CLK_I2CSLOW>; + clock-names = "div-clk", "slow"; + resets = <&tegra_car TEGRA210_CLK_VI_I2C>; + reset-names = "i2c"; + power-domains = <&pd_venc>; status = "disabled"; }; };
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 3/18 i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
In reply to Sowjanya KomatineniTegra VI I2C is part of VE power domain and typically used for camera usecases.
VE power domain is not always on and is non-IRQ safe. So, IRQ safe device cannot be attached to a non-IRQ safe domain as it prevents powering off the PM domain and generic power domain driver will warn.
Current driver marks all I2C devices as IRQ safe and VI I2C device does not require IRQ safe as it will not be used for atomic transfers.
This patch has fix to make VI I2C as non-IRQ safe.
--- drivers/i2c/busses/i2c-tegra.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
drivers/i2c/busses/i2c-tegra.c +9 -1
@@ -1750,7 +1750,15 @@ static int tegra_i2c_probe(struct platform_device *pdev) goto unprepare_slow_clk; } -pm_runtime_irq_safe (&pdev->dev); +/* +* VI I2C is in VE power domain which is not always on and not +* an IRQ safe. So, IRQ safe device can't be attached to a non-IRQ +* safe domain as it prevents powering off the PM domain. +* Also, VI I2C device don't need to use runtime IRQ safe as it will +* not be used for atomic transfers. +*/ +if (!i2c_dev->is_vi) +pm_runtime_irq_safe (&pdev->dev);pm_runtime_enable (&pdev->dev);if (!pm_runtime_enabled (&pdev->dev)) { ret =tegra_i2c_runtime_resume (&pdev->dev);
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 4/18 i2c: tegra: Fix the error path in tegra_i2c_runtime_resume
In reply to Sowjanya Komatinenitegra_i2c_runtime_resume does not disable prior enabled clocks properly.
This patch fixes it.
--- drivers/i2c/busses/i2c-tegra.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
drivers/i2c/busses/i2c-tegra.c +8 -3
@@ -668,7 +668,7 @@ static int __maybe_unused tegra_i2c_runtime_resume(struct device *dev) ret =clk_enable (i2c_dev->slow_clk);if (ret <0 ) {dev_err (dev,"failed to enable slow clock: %d\n" , ret); -return ret; + goto disable_fast_clk; } }
@@ -676,11 +676,16 @@ static int __maybe_unused tegra_i2c_runtime_resume(struct device *dev)if (ret <0 ) {dev_err (i2c_dev->dev,"Enabling div clk failed, err %d\n" , ret); -clk_disable (i2c_dev->fast_clk); -return ret; + goto disable_slow_clk; }return 0 ; + +disable_slow_clk: +clk_disable (i2c_dev->slow_clk); +disable_fast_clk: +clk_disable (i2c_dev->fast_clk); +return ret; }static int __maybe_unused tegra_i2c_runtime_suspend (struct device *dev)
Signature · 1 line
2.7.4
Dmitry Osipenko
reviewerRe: [RFC PATCH v2 04/18] i2c: tegra: Fix the error path in tegra_i2c_runtime_resume
17.06.2020 04:41, Sowjanya Komatineni пишет:
Quoted 33 lines
tegra_i2c_runtime_resumedoes not disable prior enabled clocks properly.This patch fixes it.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/i2c/busses/i2c-tegra.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)drivers/i2c/busses/i2c-tegra.c +2
-3@@ -668,7 +668,7 @@ static int __maybe_unused tegra_i2c_runtime_resume(struct device *dev) ret =clk_enable (i2c_dev->slow_clk);if (ret <0 ) {dev_err (dev,"failed to enable slow clock: %d\n" , ret); -return ret; + goto disable_fast_clk; } }@@ -676,11 +676,16 @@ static int __maybe_unused tegra_i2c_runtime_resume(struct device *dev)if (ret <0 ) {dev_err (i2c_dev->dev,"Enabling div clk failed, err %d\n" , ret); -clk_disable (i2c_dev->fast_clk); -return ret; + goto disable_slow_clk; }
drivers/i2c/busses/i2c-tegra.c static int __maybe_unused tegra_i2c_runtime_resume(struct device *dev) · line 691
Quoted 10 lines
drivers/i2c/busses/i2c-tegra.c +6
-0return 0 ; + +disable_slow_clk: +clk_disable (i2c_dev->slow_clk); +disable_fast_clk: +clk_disable (i2c_dev->fast_clk); +return ret; }static int __maybe_unused tegra_i2c_runtime_suspend (struct device *dev)
This looks good to me. Could you please add an additional patch to remove all the other conditions of the clk enable/disable? The current code was already inconsistent because in most cases there are conditions, but not in all cases.
Sowjanya Komatineni
maintainerRFC PATCH v2 5/18 i2c: tegra: Fix runtime resume to re-init VI I2C
In reply to Sowjanya KomatineniVI I2C is on host1x bus and is part of VE power domain.
During suspend/resume VE power domain goes through power off/on.
So, controller reset followed by i2c re-initialization is required after the domain power up.
This patch fixes it.
--- drivers/i2c/busses/i2c-tegra.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
drivers/i2c/busses/i2c-tegra.c +16 -0
@@ -293,6 +293,8 @@ struct tegra_i2c_dev {bool is_curr_atomic_xfer; }; +static int tegra_i2c_init (struct tegra_i2c_dev *i2c_dev,bool clk_reinit); +static void dvc_writel (struct tegra_i2c_dev *i2c_dev,u32 val,unsigned long reg) {
@@ -679,8 +681,22 @@ static int __maybe_unused tegra_i2c_runtime_resume(struct device *dev) goto disable_slow_clk; } +/* +* VI I2C device is attached to VE power domain which goes through +* power ON/OFF during PM runtime resume/suspend. So, controller +* should go through reset and need to re-initialize after power +* domain ON. +*/ +if (i2c_dev->is_vi) { + ret =tegra_i2c_init (i2c_dev, true); +if (ret) + goto disable_div_clk; + } +return 0 ; +disable_div_clk: +clk_disable (i2c_dev->div_clk); disable_slow_clk:clk_disable (i2c_dev->slow_clk); disable_fast_clk:
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 6/18 i2c: tegra: Avoid tegra_i2c_init_dma() for Tegra210 vi i2c
In reply to Sowjanya KomatineniVI I2C is on host1x bus so APB DMA can't be used for Tegra210 VI I2C and there are no tx and rx dma channels for VI I2C.
So, avoid attempt of requesting DMA channels.
--- drivers/i2c/busses/i2c-tegra.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/busses/i2c-tegra.c +1 -1
@@ -421,7 +421,7 @@ static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev)dma_addr_t dma_phys;int err; -if (!i2c_dev->hw->has_apb_dma) +if (!i2c_dev->hw->has_apb_dma || i2c_dev->is_vi)return 0 ;if (!IS_ENABLED (CONFIG_TEGRA20_APB_DMA )) {
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 7/18 media: tegra-video: Fix channel format alignment
In reply to Sowjanya KomatineniPixel format width is mistakenly aligned to surface align bytes and altering width to aligned value may force sensor mode change other than the requested one and also cause mismatch in width programmed between sensor and vi which can lead to capture errors.
This patch removes width alignment and clamps width as per Tegra minimum and maximum limits.
--- drivers/staging/media/tegra-video/vi.c | 16 +++------------- 1 file changed, 3 insertions(+), 13 deletions(-)
drivers/staging/media/tegra-video/vi.c +3 -13
@@ -359,25 +359,15 @@ static void tegra_channel_fmt_align(struct tegra_vi_channel *chan, struct v4l2_pix_format *pix, unsigned int bpp) { -unsigned int align; -unsigned int min_width; -unsigned int max_width; -unsigned int width;unsigned int min_bpl;unsigned int max_bpl;unsigned int bpl;/* -* The transfer alignment requirements are expressed in bytes. Compute -* minimum and maximum values, clamp the requested width and convert -* it back to pixels. Use bytesperline to adjust the width. +* The transfer alignment requirements are expressed in bytes. +* Clamp the requested width and height to the limits. */ - align =lcm (SURFACE_ALIGN_BYTES , bpp); - min_width =roundup (TEGRA_MIN_WIDTH , align); - max_width =rounddown (TEGRA_MAX_WIDTH , align); - width =roundup (pix->width * bpp, align); - - pix->width =clamp (width, min_width, max_width) / bpp; + pix->width =clamp (pix->width,TEGRA_MIN_WIDTH ,TEGRA_MAX_WIDTH ); pix->height =clamp (pix->height,TEGRA_MIN_HEIGHT ,TEGRA_MAX_HEIGHT );/* Clamp the requested bytes per line value. If the maximum bytes per
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 8/18 media: tegra-video: Enable TPG based on kernel config
In reply to Sowjanya KomatineniTegra internal TPG mode is only for Tegra vi and csi testing without a real sensor and driver should default support real sensor.
So, This patch adds CONFIG_VIDEO_TEGRA_TPG and enables Tegra internal TPG mode only when this config is selected.
--- drivers/staging/media/tegra-video/Kconfig | 6 +++++ drivers/staging/media/tegra-video/csi.c | 38 +++++++++++++++++++++++----- drivers/staging/media/tegra-video/tegra210.c | 6 +++++ drivers/staging/media/tegra-video/vi.c | 13 +++++++--- drivers/staging/media/tegra-video/video.c | 23 +++++++++-------- 5 files changed, 65 insertions(+), 21 deletions(-)
drivers/staging/media/tegra-video/Kconfig +6 -0
@@ -10,3 +10,9 @@ config VIDEO_TEGRA To compile this driver as a module, choose M here: the module will be called tegra-video. + +config VIDEO_TEGRA_TPG + bool "NVIDIA Tegra VI driver TPG mode" + depends on VIDEO_TEGRA + help + Say yes here to enable Tegra internal TPG mode
drivers/staging/media/tegra-video/csi.c +31 -7
@@ -62,6 +62,9 @@ static int csi_enum_bus_code(struct v4l2_subdev *subdev, struct v4l2_subdev_pad_config *cfg, struct v4l2_subdev_mbus_code_enum *code) { +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +if (code->index >=ARRAY_SIZE (tegra_csi_tpg_fmts))return -EINVAL ;
@@ -76,6 +79,9 @@ static int csi_get_format(struct v4l2_subdev *subdev, {struct tegra_csi_channel *csi_chan =to_csi_chan (subdev); +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + fmt->format = csi_chan->format;return 0 ;
@@ -121,6 +127,9 @@ static int csi_enum_framesizes(struct v4l2_subdev *subdev, {unsigned int i; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +if (fse->index >=ARRAY_SIZE (tegra_csi_tpg_sizes))return -EINVAL ;
@@ -148,6 +157,9 @@ static int csi_enum_frameintervals(struct v4l2_subdev *subdev,const struct tpg_framerate *frmrate = csi->soc->tpg_frmrate_table;int index; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +/* one framerate per format and resolution */ if (fie->index >0 )return -EINVAL ;
@@ -172,6 +184,9 @@ static int csi_set_format(struct v4l2_subdev *subdev,const struct v4l2_frmsize_discrete *sizes;unsigned int i; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + sizes = v4l2_find_nearest_size(tegra_csi_tpg_sizes, ARRAY_SIZE(tegra_csi_tpg_sizes), width, height,
@@ -208,6 +223,9 @@ static int tegra_csi_g_frame_interval(struct v4l2_subdev *subdev, {struct tegra_csi_channel *csi_chan =to_csi_chan (subdev); +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + vfi->interval.numerator =1 ; vfi->interval.denominator = csi_chan->framerate;
@@ -311,8 +329,12 @@ static int tegra_csi_channel_init(struct tegra_csi_channel *chan) subdev = &chan->subdev;v4l2_subdev_init (subdev, &tegra_csi_ops); subdev->dev = csi->dev; -snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s-%d" ,"tpg" , - chan->csi_port_num); +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s-%d" ,"tpg" , + chan->csi_port_num); +else +snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s" , +kbasename (chan->of_node->full_name));v4l2_set_subdevdata (subdev, chan); subdev->fwnode =of_fwnode_handle (chan->of_node);
@@ -405,11 +427,13 @@ static int tegra_csi_init(struct host1x_client *client)INIT_LIST_HEAD (&csi->csi_chans); - ret =tegra_csi_tpg_channels_alloc (csi); -if (ret <0 ) { -dev_err (csi->dev, -"failed to allocate tpg channels: %d\n" , ret); - goto cleanup; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_csi_tpg_channels_alloc (csi); +if (ret <0 ) { +dev_err (csi->dev, +"failed to allocate tpg channels: %d\n" , ret); + goto cleanup; + } } ret =tegra_csi_channels_init (csi);
drivers/staging/media/tegra-video/tegra210.c +6 -0
@@ -631,7 +631,11 @@ const struct tegra_vi_soc tegra210_vi_soc = { .ops = &tegra210_vi_ops, .hw_revision = 3, .vi_max_channels = 6, +#if IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG ) .vi_max_clk_hz = 499200000, +#else + .vi_max_clk_hz = 998400000, +#endif };/* Tegra210 CSI PHY registers accessors */
@@ -957,7 +961,9 @@ static const char * const tegra210_csi_cil_clks[] = {"cilab" ,"cilcd" ,"cile" , +#if IS_ENABLED(CONFIG_VIDEO_TEGRA_TPG) "csi_tpg", +#endif };/* Tegra210 CSI operations */
drivers/staging/media/tegra-video/vi.c +9 -4
@@ -565,6 +565,7 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan) {int ret; +#if IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )/* add test pattern control handler to v4l2 device */ v4l2_ctrl_new_std_menu_items(&chan->ctrl_handler, &vi_ctrl_ops, V4L2_CID_TEST_PATTERN,
@@ -576,6 +577,7 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan)v4l2_ctrl_handler_free (&chan->ctrl_handler); return chan->ctrl_handler.error; } +#endif /* setup the controls */ ret =v4l2_ctrl_handler_setup (&chan->ctrl_handler);
@@ -918,10 +920,13 @@ static int tegra_vi_init(struct host1x_client *client)INIT_LIST_HEAD (&vi->vi_chans); - ret =tegra_vi_tpg_channels_alloc (vi); -if (ret <0 ) { -dev_err (vi->dev,"failed to allocate tpg channels: %d\n" , ret); - goto free_chans; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_vi_tpg_channels_alloc (vi); +if (ret <0 ) { +dev_err (vi->dev, +"failed to allocate tpg channels: %d\n" , ret); + goto free_chans; + } } ret =tegra_vi_channels_init (vi);
drivers/staging/media/tegra-video/video.c +13 -10
@@ -60,15 +60,17 @@ static int host1x_video_probe(struct host1x_device *dev)if (ret <0 ) goto unregister_v4l2; -/* -* Both vi and csi channels are available now. -* Register v4l2 nodes and create media links for TPG. -*/ - ret =tegra_v4l2_nodes_setup_tpg (vid); -if (ret <0 ) { -dev_err (&dev->dev, -"failed to setup tpg graph: %d\n" , ret); - goto device_exit; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { +/* +* Both vi and csi channels are available now. +* Register v4l2 nodes and create media links for TPG. +*/ + ret =tegra_v4l2_nodes_setup_tpg (vid); +if (ret <0 ) { +dev_err (&dev->dev, +"failed to setup tpg graph: %d\n" , ret); + goto device_exit; + } }return 0 ;
@@ -91,7 +93,8 @@ static int host1x_video_remove(struct host1x_device *dev) {struct tegra_video_device *vid =dev_get_drvdata (&dev->dev); -tegra_v4l2_nodes_cleanup_tpg (vid); +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +tegra_v4l2_nodes_cleanup_tpg (vid);host1x_device_exit (dev);
Signature · 1 line
2.7.4
Re: [RFC PATCH v2 08/18] media: tegra-video: Enable TPG based on kernel config
Quoted 21 lines · Sowjanya Komatineni
Tegra internal TPG mode is only for Tegra vi and csi testing without a real sensor and driver should default support real sensor.
So, This patch adds
CONFIG_VIDEO_TEGRA_TPGand enables Tegra internal TPG mode only when this config is selected.Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/Kconfig | 6 +++++ drivers/staging/media/tegra-video/csi.c | 38 +++++++++++++++++++++++----- drivers/staging/media/tegra-video/tegra210.c | 6 +++++ drivers/staging/media/tegra-video/vi.c | 13 +++++++--- drivers/staging/media/tegra-video/video.c | 23 +++++++++-------- 5 files changed, 65 insertions(+), 21 deletions(-)drivers/staging/media/tegra-video/Kconfig +0
-0
drivers/staging/media/tegra-video/Kconfig config VIDEO_TEGRA · line 18
Quoted 9 lines
drivers/staging/media/tegra-video/Kconfig +6
-0@@ -10,3 +10,9 @@ config VIDEO_TEGRA To compile this driver as a module, choose M here: the module will be called tegra-video. + +config VIDEO_TEGRA_TPG + bool "NVIDIA Tegra VI driver TPG mode" + depends on VIDEO_TEGRA + help + Say yes here to enable Tegra internal TPG mode
This is not clear: if this is enabled, will the driver use TPG for ALL CSI ports? Or just for those that are not connected to anything? (i.e. the unused ports).
I always assumed that the latter was intended, but it kind of looks from the code that this switches to TPG completely.
It would also be nice if you can still use the TPG even for connected CSI ports by just setting the TEST_PATTERN control. I believe that's also what happens in the driver that is in the L4T tree.
In any case, it is definitely not clear from this config description what it does.
Regards,
Hans
Quoted 204 lines
drivers/staging/media/tegra-video/csi.c +31
-7@@ -62,6 +62,9 @@ static int csi_enum_bus_code(struct v4l2_subdev *subdev, struct v4l2_subdev_pad_config *cfg, struct v4l2_subdev_mbus_code_enum *code) { +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +if (code->index >=ARRAY_SIZE (tegra_csi_tpg_fmts))return -EINVAL ;@@ -76,6 +79,9 @@ static int csi_get_format(struct v4l2_subdev *subdev, {struct tegra_csi_channel *csi_chan =to_csi_chan (subdev); +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + fmt->format = csi_chan->format;return 0 ;@@ -121,6 +127,9 @@ static int csi_enum_framesizes(struct v4l2_subdev *subdev, {unsigned int i; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +if (fse->index >=ARRAY_SIZE (tegra_csi_tpg_sizes))return -EINVAL ;@@ -148,6 +157,9 @@ static int csi_enum_frameintervals(struct v4l2_subdev *subdev,const struct tpg_framerate *frmrate = csi->soc->tpg_frmrate_table;int index; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +/* one framerate per format and resolution */ if (fie->index >0 )return -EINVAL ;@@ -172,6 +184,9 @@ static int csi_set_format(struct v4l2_subdev *subdev,const struct v4l2_frmsize_discrete *sizes;unsigned int i; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + sizes = v4l2_find_nearest_size(tegra_csi_tpg_sizes, ARRAY_SIZE(tegra_csi_tpg_sizes), width, height,@@ -208,6 +223,9 @@ static int tegra_csi_g_frame_interval(struct v4l2_subdev *subdev, {struct tegra_csi_channel *csi_chan =to_csi_chan (subdev); +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + vfi->interval.numerator =1 ; vfi->interval.denominator = csi_chan->framerate;@@ -311,8 +329,12 @@ static int tegra_csi_channel_init(struct tegra_csi_channel *chan) subdev = &chan->subdev;v4l2_subdev_init (subdev, &tegra_csi_ops); subdev->dev = csi->dev; -snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s-%d" ,"tpg" , - chan->csi_port_num); +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s-%d" ,"tpg" , + chan->csi_port_num); +else +snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s" , +kbasename (chan->of_node->full_name));v4l2_set_subdevdata (subdev, chan); subdev->fwnode =of_fwnode_handle (chan->of_node);@@ -405,11 +427,13 @@ static int tegra_csi_init(struct host1x_client *client)INIT_LIST_HEAD (&csi->csi_chans); - ret =tegra_csi_tpg_channels_alloc (csi); -if (ret <0 ) { -dev_err (csi->dev, -"failed to allocate tpg channels: %d\n" , ret); - goto cleanup; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_csi_tpg_channels_alloc (csi); +if (ret <0 ) { +dev_err (csi->dev, +"failed to allocate tpg channels: %d\n" , ret); + goto cleanup; + } } ret =tegra_csi_channels_init (csi);drivers/staging/media/tegra-video/tegra210.c +6
-0@@ -631,7 +631,11 @@ const struct tegra_vi_soc tegra210_vi_soc = { .ops = &tegra210_vi_ops, .hw_revision = 3, .vi_max_channels = 6, +#if IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG ) .vi_max_clk_hz = 499200000, +#else + .vi_max_clk_hz = 998400000, +#endif };/* Tegra210 CSI PHY registers accessors */ @@ -957,7 +961,9 @@ static const char * const tegra210_csi_cil_clks[] = {"cilab" ,"cilcd" ,"cile" , +#if IS_ENABLED(CONFIG_VIDEO_TEGRA_TPG) "csi_tpg", +#endif };/* Tegra210 CSI operations */ drivers/staging/media/tegra-video/vi.c +9
-4@@ -565,6 +565,7 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan) {int ret; +#if IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )/* add test pattern control handler to v4l2 device */ v4l2_ctrl_new_std_menu_items(&chan->ctrl_handler, &vi_ctrl_ops, V4L2_CID_TEST_PATTERN,@@ -576,6 +577,7 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan)v4l2_ctrl_handler_free (&chan->ctrl_handler); return chan->ctrl_handler.error; } +#endif /* setup the controls */ ret =v4l2_ctrl_handler_setup (&chan->ctrl_handler);@@ -918,10 +920,13 @@ static int tegra_vi_init(struct host1x_client *client)INIT_LIST_HEAD (&vi->vi_chans); - ret =tegra_vi_tpg_channels_alloc (vi); -if (ret <0 ) { -dev_err (vi->dev,"failed to allocate tpg channels: %d\n" , ret); - goto free_chans; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_vi_tpg_channels_alloc (vi); +if (ret <0 ) { +dev_err (vi->dev, +"failed to allocate tpg channels: %d\n" , ret); + goto free_chans; + } } ret =tegra_vi_channels_init (vi);drivers/staging/media/tegra-video/video.c +13
-10@@ -60,15 +60,17 @@ static int host1x_video_probe(struct host1x_device *dev)if (ret <0 ) goto unregister_v4l2; -/* -* Both vi and csi channels are available now. -* Register v4l2 nodes and create media links for TPG. -*/ - ret =tegra_v4l2_nodes_setup_tpg (vid); -if (ret <0 ) { -dev_err (&dev->dev, -"failed to setup tpg graph: %d\n" , ret); - goto device_exit; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { +/* +* Both vi and csi channels are available now. +* Register v4l2 nodes and create media links for TPG. +*/ + ret =tegra_v4l2_nodes_setup_tpg (vid); +if (ret <0 ) { +dev_err (&dev->dev, +"failed to setup tpg graph: %d\n" , ret); + goto device_exit; + } }return 0 ;@@ -91,7 +93,8 @@ static int host1x_video_remove(struct host1x_device *dev) {struct tegra_video_device *vid =dev_get_drvdata (&dev->dev); -tegra_v4l2_nodes_cleanup_tpg (vid); +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +tegra_v4l2_nodes_cleanup_tpg (vid);host1x_device_exit (dev);
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 08/18] media: tegra-video: Enable TPG based on kernel config
Quoted 42 lines · Hans Verkuil
Quoted 21 lines · Sowjanya Komatineni
Tegra internal TPG mode is only for Tegra vi and csi testing without a real sensor and driver should default support real sensor.
So, This patch adds
CONFIG_VIDEO_TEGRA_TPGand enables Tegra internal TPG mode only when this config is selected.Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/Kconfig | 6 +++++ drivers/staging/media/tegra-video/csi.c | 38 +++++++++++++++++++++++----- drivers/staging/media/tegra-video/tegra210.c | 6 +++++ drivers/staging/media/tegra-video/vi.c | 13 +++++++--- drivers/staging/media/tegra-video/video.c | 23 +++++++++-------- 5 files changed, 65 insertions(+), 21 deletions(-)drivers/staging/media/tegra-video/Kconfig +0
-0drivers/staging/media/tegra-video/Kconfig config VIDEO_TEGRA · line 18
Quoted 9 lines
drivers/staging/media/tegra-video/Kconfig +6
-0@@ -10,3 +10,9 @@ config VIDEO_TEGRA To compile this driver as a module, choose M here: the module will be called tegra-video. + +config VIDEO_TEGRA_TPG + bool "NVIDIA Tegra VI driver TPG mode" + depends on VIDEO_TEGRA + help + Say yes here to enable Tegra internal TPG modeThis is not clear: if this is enabled, will the driver use TPG for ALL CSI ports? Or just for those that are not connected to anything? (i.e. the unused ports).
I always assumed that the latter was intended, but it kind of looks from the code that this switches to TPG completely.
It would also be nice if you can still use the TPG even for connected CSI ports by just setting the
TEST_PATTERNcontrol. I believe that's also what happens in the driver that is in the L4T tree.
Quoted 6 lines
In any case, it is definitely not clear from this config description what it does.
Regards,
Hans
Same v4l2 test pattern control is used by sensor subdevices as well and we can't differentiate between Tegra Vs Sensor test patterns.
Current patches are based on our prior discussions where Tegra internal TPG is enabled for all channels/ports only when TPG Kconfig is set otherwise it will be for sensor capture based on the device graph.
To be clear, will update Kconfig description specifying all channels will be in TPG mode only when TPG Kconfig is set otherwise media links are purely based on the device graph from DT.
Thanks
Sowjanya
Quoted 205 lines
Quoted 205 lines
drivers/staging/media/tegra-video/csi.c +31
-7@@ -62,6 +62,9 @@ static int csi_enum_bus_code(struct v4l2_subdev *subdev, struct v4l2_subdev_pad_config *cfg, struct v4l2_subdev_mbus_code_enum *code) { +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +if (code->index >=ARRAY_SIZE (tegra_csi_tpg_fmts))return -EINVAL ;@@ -76,6 +79,9 @@ static int csi_get_format(struct v4l2_subdev *subdev, {struct tegra_csi_channel *csi_chan =to_csi_chan (subdev); +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + fmt->format = csi_chan->format;return 0 ;@@ -121,6 +127,9 @@ static int csi_enum_framesizes(struct v4l2_subdev *subdev, {unsigned int i; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +if (fse->index >=ARRAY_SIZE (tegra_csi_tpg_sizes))return -EINVAL ;@@ -148,6 +157,9 @@ static int csi_enum_frameintervals(struct v4l2_subdev *subdev,const struct tpg_framerate *frmrate = csi->soc->tpg_frmrate_table;int index; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; +/* one framerate per format and resolution */ if (fie->index >0 )return -EINVAL ;@@ -172,6 +184,9 @@ static int csi_set_format(struct v4l2_subdev *subdev,const struct v4l2_frmsize_discrete *sizes;unsigned int i; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + sizes = v4l2_find_nearest_size(tegra_csi_tpg_sizes, ARRAY_SIZE(tegra_csi_tpg_sizes), width, height,@@ -208,6 +223,9 @@ static int tegra_csi_g_frame_interval(struct v4l2_subdev *subdev, {struct tegra_csi_channel *csi_chan =to_csi_chan (subdev); +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOIOCTLCMD ; + vfi->interval.numerator =1 ; vfi->interval.denominator = csi_chan->framerate;@@ -311,8 +329,12 @@ static int tegra_csi_channel_init(struct tegra_csi_channel *chan) subdev = &chan->subdev;v4l2_subdev_init (subdev, &tegra_csi_ops); subdev->dev = csi->dev; -snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s-%d" ,"tpg" , - chan->csi_port_num); +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s-%d" ,"tpg" , + chan->csi_port_num); +else +snprintf (subdev->name,V4L2_SUBDEV_NAME_SIZE ,"%s" , +kbasename (chan->of_node->full_name));v4l2_set_subdevdata (subdev, chan); subdev->fwnode =of_fwnode_handle (chan->of_node);@@ -405,11 +427,13 @@ static int tegra_csi_init(struct host1x_client *client)INIT_LIST_HEAD (&csi->csi_chans); - ret =tegra_csi_tpg_channels_alloc (csi); -if (ret <0 ) { -dev_err (csi->dev, -"failed to allocate tpg channels: %d\n" , ret); - goto cleanup; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_csi_tpg_channels_alloc (csi); +if (ret <0 ) { +dev_err (csi->dev, +"failed to allocate tpg channels: %d\n" , ret); + goto cleanup; + } } ret =tegra_csi_channels_init (csi);drivers/staging/media/tegra-video/tegra210.c +6
-0@@ -631,7 +631,11 @@ const struct tegra_vi_soc tegra210_vi_soc = { .ops = &tegra210_vi_ops, .hw_revision = 3, .vi_max_channels = 6, +#if IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG ) .vi_max_clk_hz = 499200000, +#else + .vi_max_clk_hz = 998400000, +#endif };/* Tegra210 CSI PHY registers accessors */ @@ -957,7 +961,9 @@ static const char * const tegra210_csi_cil_clks[] = {"cilab" ,"cilcd" ,"cile" , +#if IS_ENABLED(CONFIG_VIDEO_TEGRA_TPG) "csi_tpg", +#endif };/* Tegra210 CSI operations */ drivers/staging/media/tegra-video/vi.c +9
-4@@ -565,6 +565,7 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan) {int ret; +#if IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )/* add test pattern control handler to v4l2 device */ v4l2_ctrl_new_std_menu_items(&chan->ctrl_handler, &vi_ctrl_ops, V4L2_CID_TEST_PATTERN,@@ -576,6 +577,7 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan)v4l2_ctrl_handler_free (&chan->ctrl_handler); return chan->ctrl_handler.error; } +#endif /* setup the controls */ ret =v4l2_ctrl_handler_setup (&chan->ctrl_handler);@@ -918,10 +920,13 @@ static int tegra_vi_init(struct host1x_client *client)INIT_LIST_HEAD (&vi->vi_chans); - ret =tegra_vi_tpg_channels_alloc (vi); -if (ret <0 ) { -dev_err (vi->dev,"failed to allocate tpg channels: %d\n" , ret); - goto free_chans; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_vi_tpg_channels_alloc (vi); +if (ret <0 ) { +dev_err (vi->dev, +"failed to allocate tpg channels: %d\n" , ret); + goto free_chans; + } } ret =tegra_vi_channels_init (vi);drivers/staging/media/tegra-video/video.c +13
-10@@ -60,15 +60,17 @@ static int host1x_video_probe(struct host1x_device *dev)if (ret <0 ) goto unregister_v4l2; -/* -* Both vi and csi channels are available now. -* Register v4l2 nodes and create media links for TPG. -*/ - ret =tegra_v4l2_nodes_setup_tpg (vid); -if (ret <0 ) { -dev_err (&dev->dev, -"failed to setup tpg graph: %d\n" , ret); - goto device_exit; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { +/* +* Both vi and csi channels are available now. +* Register v4l2 nodes and create media links for TPG. +*/ + ret =tegra_v4l2_nodes_setup_tpg (vid); +if (ret <0 ) { +dev_err (&dev->dev, +"failed to setup tpg graph: %d\n" , ret); + goto device_exit; + } }return 0 ;@@ -91,7 +93,8 @@ static int host1x_video_remove(struct host1x_device *dev) {struct tegra_video_device *vid =dev_get_drvdata (&dev->dev); -tegra_v4l2_nodes_cleanup_tpg (vid); +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +tegra_v4l2_nodes_cleanup_tpg (vid);host1x_device_exit (dev);
Sowjanya Komatineni
maintainerRFC PATCH v2 9/18 media: tegra-video: Update format lookup to offset based
In reply to Sowjanya KomatineniTegra VI supported video formats are more for non TPG and there can be multiple pixel formats for the same media bus format.
This patch updates the helper function for format lookup based on mbus code from pre-defined Tegra supported format list to look from the specified list index offset.
Offset based look up is used with sensor device graph (non TPG) where format enumeration can list all supported formats for the specific sensor mbus codes.
--- drivers/staging/media/tegra-video/vi.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
drivers/staging/media/tegra-video/vi.c +6 -4
@@ -53,11 +53,12 @@ to_tegra_channel_buffer(struct vb2_v4l2_buffer *vb) }static int tegra_get_format_idx_by_code (struct tegra_vi *vi, -unsigned int code) +unsigned int code, +unsigned int offset) {unsigned int i; -for (i =0 ; i < vi->soc->nformats; ++i) { +for (i = offset; i < vi->soc->nformats; ++i) {if (vi->soc->video_formats[i].code == code)return i; }
@@ -598,11 +599,12 @@ static void vi_tpg_fmts_bitmap_init(struct tegra_vi_channel *chan)bitmap_zero (chan->tpg_fmts_bitmap,MAX_FORMAT_NUM ); index =tegra_get_format_idx_by_code (chan->vi, -MEDIA_BUS_FMT_SRGGB10_1X10 ); +MEDIA_BUS_FMT_SRGGB10_1X10 ,0 );bitmap_set (chan->tpg_fmts_bitmap, index,1 ); index =tegra_get_format_idx_by_code (chan->vi, -MEDIA_BUS_FMT_RGB888_1X32_PADHI ); +MEDIA_BUS_FMT_RGB888_1X32_PADHI , +0 );bitmap_set (chan->tpg_fmts_bitmap, index,1 ); }
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 10/18 dt-bindings: tegra: Update VI and CSI bindings with port info
In reply to Sowjanya KomatineniUpdate VI and CSI bindings to add port and endpoint nodes as per media video-interfaces DT binding document.
--- .../display/tegra/nvidia,tegra20-host1x.txt | 92 +++++++++++++++++++++- 1 file changed, 90 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt +90 -2
@@ -51,8 +51,16 @@ of the following host1x client modules: - vi - Tegra210: - power-domains: Must include venc powergate node as vi is in VE partition. - - Tegra210 has CSI part of VI sharing same host interface and register space. - So, VI device node should have CSI child node. + + ports (optional node) + vi can have optional ports node and max 6 ports are supported. Each port + should have single 'endpoint' child node. All port nodes are grouped under + ports node. Please refer to the bindings defined in + Documentation/devicetree/bindings/media/video-interfaces.txt + + csi (required node) + Tegra210 has CSI part of VI sharing same host interface and register space. + So, VI device node should have CSI child node. - csi: mipi csi interface to vi
@@ -65,6 +73,46 @@ of the following host1x client modules: - power-domains: Must include sor powergate node as csicil is in SOR partition. + channel (optional nodes) + Maximum 6 channels are supported with each csi brick as either x4 or x2 + based on hw connectivity to sensor. + + Required properties: + - reg: csi port number. Valid port numbers are 0 through 5. + - nvidia,mipi-calibrate: Should contain a phandle and a specifier + specifying which pads are used by this CSI port and need to be + calibrated. See also ../display/tegra/nvidia,tegra114-mipi.txt. + + Each channel node must contain 2 port nodes which can be grouped + under 'ports' node and each port should have a single child 'endpoint' + node. + + ports node + Please refer to the bindings defined in + Documentation/devicetree/bindings/media/video-interfaces.txt + + ports node must contain below 2 port nodes. + port@0 with single child 'endpoint' node always a sink. + port@1 with single child 'endpoint' node always a source. + + port@0 (required node) + Required properties: + - reg: 0 + + endpoint (required node) + Required properties: + - data-lanes: an array of data lane from 1 to 4. Valid array + lengths are 1/2/4. + - remote-endpoint: phandle to sensor 'endpoint' node. + + port@1 (required node) + Required properties: + - reg: 1 + + endpoint (required node) + Required properties: + - remote-endpoint: phandle to vi port 'endpoint' node. + - epp: encoder pre-processor Required properties:
@@ -340,6 +388,18 @@ Example: ranges = <0x0 0x0 0x54080000 0x2000>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + imx219_vi_in0: endpoint { + remote-endpoint = <&imx219_csi_out0>; + }; + }; + }; + csi@838 { compatible = "nvidia,tegra210-csi"; reg = <0x838 0x1300>;
@@ -362,6 +422,34 @@ Example: <&tegra_car TEGRA210_CLK_CSI_TPG>; clock-names = "csi", "cilab", "cilcd", "cile", "csi_tpg"; power-domains = <&pd_sor>; + + #address-cells = <1>; + #size-cells = <0>; + + channel@0 { + reg = <0>; + nvidia,mipi-calibrate = <&mipi 0x001>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + imx219_csi_in0: endpoint { + data-lanes = <1 2>; + remote-endpoint = <&imx219_out0>; + }; + }; + + port@1 { + reg = <1>; + imx219_csi_out0: endpoint { + remote-endpoint = <&imx219_vi_in0>; + }; + }; + }; + }; }; };
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 11/18 media: tegra-video: Add support for external sensor capture
In reply to Sowjanya KomatineniThis patch adds support to capture from the external sensor based on device graph in the device tree.
Driver walks through the device graph to create media links between the entities and registers and unregisters video devices when the corresponding sub-devices are bound and unbound.
Channel formats are enumerated based on available formats from the sensor and the corresponding matched formats from the Tegra supported video formats list.
Each Tegra CSI instance can be configured as 4-lane or 2-lane based on supported lane configuration from the sensor through the device tree.
Currently this driver supports V4L2 video node centric only.
--- drivers/staging/media/tegra-video/Kconfig | 1 + drivers/staging/media/tegra-video/csi.c | 128 +++++- drivers/staging/media/tegra-video/csi.h | 1 + drivers/staging/media/tegra-video/tegra210.c | 2 +- drivers/staging/media/tegra-video/vi.c | 623 +++++++++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- 6 files changed, 726 insertions(+), 52 deletions(-)
drivers/staging/media/tegra-video/Kconfig +1 -0
@@ -5,6 +5,7 @@ config VIDEO_TEGRA depends on VIDEO_V4L2 select MEDIA_CONTROLLER select VIDEOBUF2_DMA_CONTIG + select V4L2_FWNODE help Choose this option if you have an NVIDIA Tegra SoC.
drivers/staging/media/tegra-video/csi.c +109 -19
172 lines not on this page · raw message
drivers/staging/media/tegra-video/csi.h +1 -0
@@ -7,6 +7,7 @@#define __TEGRA_CSI_H__#include <media/media-entity.h> +#include <media/v4l2-async.h> #include <media/v4l2-subdev.h> /*
drivers/staging/media/tegra-video/tegra210.c +1 -1
@@ -230,7 +230,7 @@ static void tegra_channel_capture_error_recover(struct tegra_vi_channel *chan)tegra_channel_capture_setup (chan);/* recover CSI block */ - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, false);tegra_csi_error_recover (subdev); }
drivers/staging/media/tegra-video/vi.c +592 -31
779 lines not on this page · raw message
drivers/staging/media/tegra-video/vi.h +22 -1
@@ -14,6 +14,7 @@#include <linux/wait.h> #include <media/media-entity.h> +#include <media/v4l2-async.h> #include <media/v4l2-ctrls.h> #include <media/v4l2-device.h> #include <media/v4l2-dev.h>
@@ -93,6 +94,19 @@ struct tegra_vi { };/** +* struct tegra_vi_graph_entity - Entity in the video graph +* +* @asd: subdev asynchronous registration information +* @entity: media entity from the corresponding V4L2 subdev +* @subdev: V4L2 subdev +*/ +struct tegra_vi_graph_entity { +struct v4l2_async_subdev asd; +struct media_entity *entity; +struct v4l2_subdev *subdev; +}; + +/** * struct tegra_vi_channel - Tegra video channel * * @list: list head for this entry
@@ -138,10 +152,13 @@ struct tegra_vi {* @done_lock: protects the capture done queue list * * @portno: VI channel port number +* @of_node: device node of VI channel * * @ctrl_handler: V4L2 control handler of this video channel +* @fmts_bitmap: a bitmap for supported formats matching v4l2 subdev formats * @tpg_fmts_bitmap: a bitmap for supported TPG formats * @pg_mode: test pattern generator mode (disabled/direct/patch) +* @notifier: V4L2 asynchronous subdevs notifier */ struct tegra_vi_channel {struct list_head list;
@@ -174,10 +191,14 @@ struct tegra_vi_channel {spinlock_t done_lock;unsigned char portno; +struct device_node *of_node;struct v4l2_ctrl_handler ctrl_handler; +DECLARE_BITMAP (fmts_bitmap,MAX_FORMAT_NUM );DECLARE_BITMAP (tpg_fmts_bitmap,MAX_FORMAT_NUM );enum tegra_vi_pg_mode pg_mode; + +struct v4l2_async_notifier notifier; };/**
@@ -249,7 +270,7 @@ extern const struct tegra_vi_soc tegra210_vi_soc;#endif struct v4l2_subdev * -tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan); +tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan,bool sensor);int tegra_channel_set_stream (struct tegra_vi_channel *chan,bool on);void tegra_channel_release_buffers (struct tegra_vi_channel *chan,enum vb2_buffer_state state);
Signature · 1 line
2.7.4
Re: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Hi Sowjanya,
As promised, here is the review of this remaining patch. I've now reviewed and tested the whole series.
I have some more patches pending for the imx274 but some of that needs a bit more testing. I hope to be able to post those soon.
Quoted 27 lines · Sowjanya Komatineni
This patch adds support to capture from the external sensor based on device graph in the device tree.
Driver walks through the device graph to create media links between the entities and registers and unregisters video devices when the corresponding sub-devices are bound and unbound.
Channel formats are enumerated based on available formats from the sensor and the corresponding matched formats from the Tegra supported video formats list.
Each Tegra CSI instance can be configured as 4-lane or 2-lane based on supported lane configuration from the sensor through the device tree.
Currently this driver supports V4L2 video node centric only.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/Kconfig | 1 + drivers/staging/media/tegra-video/csi.c | 128 +++++- drivers/staging/media/tegra-video/csi.h | 1 + drivers/staging/media/tegra-video/tegra210.c | 2 +- drivers/staging/media/tegra-video/vi.c | 623 +++++++++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- 6 files changed, 726 insertions(+), 52 deletions(-)
<snip>
Quoted 26 lines
drivers/staging/media/tegra-video/vi.c +7
-0@@ -12,6 +12,7 @@#include <linux/module.h> #include <linux/of.h> #include <linux/of_device.h> +#include <linux/of_graph.h> #include <linux/platform_device.h> #include <linux/regulator/consumer.h> #include <linux/pm_runtime.h> @@ -52,6 +53,12 @@ to_tegra_channel_buffer(struct vb2_v4l2_buffer *vb) return container_of(vb, struct tegra_channel_buffer, buf); } +static inline struct tegra_vi_graph_entity * +to_tegra_vi_graph_entity (struct v4l2_async_subdev *asd) +{ + return container_of(asd, struct tegra_vi_graph_entity, asd); +} +static int tegra_get_format_idx_by_code (struct tegra_vi *vi,unsigned int code,unsigned int offset)
drivers/staging/media/tegra-video/vi.c static void tegra_channel_buffer_queue(struct vb2_buffer *vb) · line 156
Quoted 5 lines
drivers/staging/media/tegra-video/vi.c +1
-1@@ -146,7 +153,7 @@ static void tegra_channel_buffer_queue(struct vb2_buffer *vb) }struct v4l2_subdev * -tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan) +tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan,bool sensor)
Hmm, this 'sensor' argument is, I think, a bit too obscure.
I would rename this function to tegra_channel_get_remote_csi_subdev, which is the equivalent of setting 'sensor' to false, and add a new tegra_channel_get_remote_sensor_subdev() function that calls this function and then does the 'while (1)' loop.
That will make the code more readable since it is clear what the intention is.
A better alternative to tegra_channel_get_remote_sensor_subdev() might be tegra_channel_get_remote_source_subdev() since that covers both the sensor and TPG case.
drivers/staging/media/tegra-video/vi.c tegra_channel_get_remote_subdev(struct tegra_vi_channel *chan) · line 168
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +3
-0{struct media_pad *pad;struct v4l2_subdev *subdev;@@ -156,6 +163,24 @@ tegra_channel_get_remote_subdev(struct tegra_vi_channel *chan) entity = pad->entity; subdev =media_entity_to_v4l2_subdev (entity); +if (sensor) { +while (1 ) { +if ((pad->index -1 ) <0 )
'index' is a u16, so I'd rewrite this as 'if (pad->index < 1)' to avoid signedness issues.
Quoted 19 lines
drivers/staging/media/tegra-video/vi.c +15
-0+break ; + + pad = &entity->pads[pad->index -1 ]; +if (!(pad->flags &MEDIA_PAD_FL_SINK )) +break ; + + pad =media_entity_remote_pad (pad); +if (!pad || !is_media_entity_v4l2_subdev (pad->entity)) +break ; + + entity = pad->entity; + subdev =media_entity_to_v4l2_subdev (entity); + } + } +return subdev; }
drivers/staging/media/tegra-video/vi.c int tegra_channel_set_stream(struct tegra_vi_channel *chan, bool on) · line 193
Quoted 5 lines
drivers/staging/media/tegra-video/vi.c +1
-1@@ -165,7 +190,15 @@ int tegra_channel_set_stream(struct tegra_vi_channel *chan, bool on)int ret;/* stream CSI */ - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, !on);
'!on' is a bit too obscure. I see what the intention is (to stream on, first enable the csi, then the sensor, and the reverse to stream off), but it is not exactly obvious at first reading, and it conflicts with the 'stream CSI' comment.
Quoted 107 lines
drivers/staging/media/tegra-video/vi.c +35
-8+ ret =v4l2_subdev_call (subdev, video, s_stream, on); +if (on && ret <0 && ret != -ENOIOCTLCMD ) +return ret; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return 0 ; + + subdev =tegra_channel_get_remote_subdev (chan, on); ret =v4l2_subdev_call (subdev, video, s_stream, on);if (on && ret <0 && ret != -ENOIOCTLCMD )return ret;@@ -252,7 +285,7 @@ static int tegra_channel_g_parm(struct file *file, void *fh,struct tegra_vi_channel *chan =video_drvdata (file);struct v4l2_subdev *subdev; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true);return v4l2_g_parm_cap (&chan->video, subdev, a); }@@ -262,7 +295,7 @@ static int tegra_channel_s_parm(struct file *file, void *fh,struct tegra_vi_channel *chan =video_drvdata (file);struct v4l2_subdev *subdev; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true);return v4l2_s_parm_cap (&chan->video, subdev, a); }@@ -284,7 +317,7 @@ static int tegra_channel_enum_framesizes(struct file *file, void *fh, fse.code = fmtinfo->code; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true); ret =v4l2_subdev_call (subdev, pad, enum_frame_size,NULL , &fse);if (ret)return ret;@@ -316,7 +349,7 @@ static int tegra_channel_enum_frameintervals(struct file *file, void *fh, fie.code = fmtinfo->code; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true); ret =v4l2_subdev_call (subdev, pad, enum_frame_interval,NULL , &fie);if (ret)return ret;@@ -335,6 +368,9 @@ static int tegra_channel_enum_format(struct file *file, void *fh,unsigned int index =0 , i;unsigned long *fmts_bitmap = chan->tpg_fmts_bitmap; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) + fmts_bitmap = chan->fmts_bitmap; +if (f->index >=bitmap_weight (fmts_bitmap,MAX_FORMAT_NUM ))return -EINVAL ;@@ -391,8 +427,9 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan,struct v4l2_subdev *subdev;struct v4l2_subdev_format fmt;struct v4l2_subdev_pad_config *pad_cfg; +int ret; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true); pad_cfg =v4l2_subdev_alloc_pad_config (subdev);if (!pad_cfg)return -ENOMEM ;@@ -412,7 +449,10 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan, fmt.which =V4L2_SUBDEV_FORMAT_TRY ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); -v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt); + ret =v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt); +if (ret <0 ) +return ret; +v4l2_fill_pix_format (pix, &fmt.format);tegra_channel_fmt_align (chan, pix, fmtinfo->bpp);@@ -452,8 +492,11 @@ static int tegra_channel_set_format(struct file *file, void *fh, fmt.which =V4L2_SUBDEV_FORMAT_ACTIVE ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); - subdev =tegra_channel_get_remote_subdev (chan); -v4l2_subdev_call (subdev, pad, set_fmt,NULL , &fmt); + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, set_fmt,NULL , &fmt); +if (ret <0 ) +return ret; +v4l2_fill_pix_format (pix, &fmt.format);tegra_channel_fmt_align (chan, pix, fmtinfo->bpp);@@ -463,15 +506,52 @@ static int tegra_channel_set_format(struct file *file, void *fh,return 0 ; } +static int tegra_channel_set_subdev_active_fmt (struct tegra_vi_channel *chan) +{ +int ret, index; +const struct tegra_video_format *fmtinfo; +struct v4l2_subdev *subdev; +struct v4l2_subdev_format fmt = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; +
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_format(struct file *file, void *fh, · line 527
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+/* +* Initialize channel format to the sub-device active format if there +* is corresponding match in the Tegra supported video formats. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, get_fmt,NULL , &fmt); +if (ret) +return ret; + + index =tegra_get_format_idx_by_code (chan->vi, fmt.format.code,0 );
index can be negative...
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_format(struct file *file, void *fh, · line 529
Quoted 2 lines
drivers/staging/media/tegra-video/vi.c +2
-0+ fmtinfo = &chan->vi->soc->video_formats[index]; +if (!fmtinfo)
... and fmtinfo can never be NULL
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_format(struct file *file, void *fh, · line 530
Quoted 1 line
drivers/staging/media/tegra-video/vi.c +1
-0+return -EINVAL ;
I'm not really sure what the intention is here, but I suspect something like this:
if (index < 0) return -EINVAL;
Quoted 88 lines
drivers/staging/media/tegra-video/vi.c +65
-2+ + chan->fmtinfo = fmtinfo; +v4l2_fill_pix_format (&chan->format, &fmt.format); + chan->format.pixelformat = chan->fmtinfo->fourcc; + chan->format.bytesperline = chan->format.width * chan->fmtinfo->bpp; + chan->format.sizeimage = chan->format.bytesperline * + chan->format.height; +tegra_channel_fmt_align (chan, &chan->format, chan->fmtinfo->bpp); + +return 0 ; +} +static int tegra_channel_enum_input (struct file *file,void *fh,struct v4l2_input *inp) { -/* currently driver supports internal TPG only */ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +if (inp->index)return -EINVAL ; inp->type =V4L2_INPUT_TYPE_CAMERA ; -strscpy (inp->name,"Tegra TPG" ,sizeof (inp->name)); + subdev =tegra_channel_get_remote_subdev (chan, true); +strscpy (inp->name, subdev->name,sizeof (inp->name));return 0 ; }@@ -578,6 +658,19 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan)v4l2_ctrl_handler_free (&chan->ctrl_handler); return chan->ctrl_handler.error; } +#else +struct v4l2_subdev *subdev; + + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_ctrl_add_handler (&chan->ctrl_handler, subdev->ctrl_handler, +NULL , true); +if (ret <0 ) { +dev_err (chan->vi->dev, +"failed to add subdev %s ctrl handler: %d\n" , + subdev->name, ret); +v4l2_ctrl_handler_free (&chan->ctrl_handler); +return ret; + }#endif /* setup the controls */ @@ -608,6 +701,57 @@ static void vi_tpg_fmts_bitmap_init(struct tegra_vi_channel *chan)bitmap_set (chan->tpg_fmts_bitmap, index,1 ); } +static void vi_fmts_bitmap_init (struct tegra_vi_channel *chan) +{ +int index, ret, match_code =0 ; +struct v4l2_subdev *subdev; +struct v4l2_subdev_mbus_code_enum code = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; + +bitmap_zero (chan->fmts_bitmap,MAX_FORMAT_NUM ); + +/* +* Set the bitmap bits based on all the matched formats between the +* available media bus formats of sub-device and the pre-defined Tegra +* supported video formats. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); +while (1 ) { + ret =v4l2_subdev_call (subdev, pad, enum_mbus_code, +NULL , &code); +if (ret <0 ) +break ; + + index =tegra_get_format_idx_by_code (chan->vi, code.code,0 ); +while (index >=0 ) { +bitmap_set (chan->fmts_bitmap, index,1 ); +if (!match_code) + match_code = code.code; +/* look for other formats with same mbus code */ + index =tegra_get_format_idx_by_code (chan->vi, + code.code, + index +1 ); + } + + code.index++; + }
drivers/staging/media/tegra-video/vi.c static void vi_tpg_fmts_bitmap_init(struct tegra_vi_channel *chan) · line 748
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+ +/* +* Set the bitmap bit corresponding to default tegra video format if +* there are no matched formats. +*/ +if (!match_code) { + match_code = tegra_default_format.code; + index =tegra_get_format_idx_by_code (chan->vi, match_code,0 ); +if (index >=0 ) +bitmap_set (chan->fmts_bitmap, index,1 );
If index < 0, then you end up with an all zero fmts_bitmap.
A WARN_ON is the minimum action to take in that case, but you should probably return an error since this really should not happen.
Quoted 247 lines
drivers/staging/media/tegra-video/vi.c +204
-13+ } + +/* initialize channel format to the sub-device active format */ +tegra_channel_set_subdev_active_fmt (chan); +} +static void tegra_channel_cleanup (struct tegra_vi_channel *chan) {v4l2_ctrl_handler_free (&chan->ctrl_handler);@@ -720,6 +864,9 @@ static int tegra_channel_init(struct tegra_vi_channel *chan) goto free_v4l2_ctrl_hdl; } +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +v4l2_async_notifier_init (&chan->notifier); +return 0 ; free_v4l2_ctrl_hdl:@@ -733,28 +880,84 @@ static int tegra_channel_init(struct tegra_vi_channel *chan)return ret; } -static int tegra_vi_tpg_channels_alloc (struct tegra_vi *vi) +static int tegra_vi_channel_alloc (struct tegra_vi *vi,unsigned int port_num, +struct device_node *node) {struct tegra_vi_channel *chan; + +/* +* Do not use devm_kzalloc as memory is freed immediately +* when device instance is unbound but application might still +* be holding the device node open. Channel memory allocated +* with kzalloc is freed during video device release callback. +*/ + chan =kzalloc (sizeof (*chan),GFP_KERNEL ); +if (!chan) +return -ENOMEM ; + + chan->vi = vi; + chan->portno = port_num; + chan->of_node = node; +list_add_tail (&chan->list, &vi->vi_chans); + +return 0 ; +} + +static int tegra_vi_tpg_channels_alloc (struct tegra_vi *vi) +{unsigned int port_num;unsigned int nchannels = vi->soc->vi_max_channels; +int ret;for (port_num =0 ; port_num < nchannels; port_num++) { -/* -* Do not use devm_kzalloc as memory is freed immediately -* when device instance is unbound but application might still -* be holding the device node open. Channel memory allocated -* with kzalloc is freed during video device release callback. -*/ - chan =kzalloc (sizeof (*chan),GFP_KERNEL ); -if (!chan) -return -ENOMEM ; + ret =tegra_vi_channel_alloc (vi, port_num, vi->dev->of_node); +if (ret <0 ) +return ret; + } + +return 0 ; +} + +static int tegra_vi_channels_alloc (struct tegra_vi *vi) +{ +struct device_node *node = vi->dev->of_node; +struct device_node *ep =NULL ; +struct device_node *ports; +struct device_node *port; +unsigned int port_num; +int ret; + + ports =of_get_child_by_name (node,"ports" ); +if (!ports) +return -ENODEV ; + +for_each_child_of_node (ports, port) { +if (!of_node_name_eq (port,"port" )) +continue ; + + ret =of_property_read_u32 (port,"reg" , &port_num); +if (ret <0 ) +continue ; + +if (port_num > vi->soc->vi_max_channels) { +of_node_put (ports); +dev_err (vi->dev,"invalid port num %d\n" , port_num); +return -EINVAL ; + } + + ep =of_get_child_by_name (port,"endpoint" ); +if (!ep) +continue ; - chan->vi = vi; - chan->portno = port_num; -list_add_tail (&chan->list, &vi->vi_chans); +of_node_put (ep); + ret =tegra_vi_channel_alloc (vi, port_num, port); +if (ret <0 ) { +of_node_put (ports); +return ret; + } } +of_node_put (ports);return 0 ; }@@ -909,6 +1112,352 @@ static int __maybe_unused vi_runtime_suspend(struct device *dev)return 0 ; } +/* +* Graph Management +*/ +static struct tegra_vi_graph_entity * +tegra_vi_graph_find_entity (struct tegra_vi_channel *chan, +const struct fwnode_handle *fwnode) +{ +struct tegra_vi_graph_entity *entity; +struct v4l2_async_subdev *asd; + +list_for_each_entry (asd, &chan->notifier.asd_list, asd_list) { + entity =to_tegra_vi_graph_entity (asd); +if (entity->asd.match.fwnode == fwnode) +return entity; + } + +return NULL ; +} + +static int tegra_vi_graph_build (struct tegra_vi_channel *chan, +struct tegra_vi_graph_entity *entity) +{ +struct tegra_vi *vi = chan->vi; +struct tegra_vi_graph_entity *ent; +struct fwnode_handle *ep =NULL ; +struct v4l2_fwnode_link link; +struct media_entity *local = entity->entity; +struct media_entity *remote; +struct media_pad *local_pad; +struct media_pad *remote_pad; +u32 link_flags =MEDIA_LNK_FL_ENABLED ; +int ret =0 ; + +dev_dbg (vi->dev,"creating links for entity %s\n" , local->name); + +while (1 ) { + ep =fwnode_graph_get_next_endpoint (entity->asd.match.fwnode, + ep); +if (!ep) +break ; + + ret =v4l2_fwnode_parse_link (ep, &link); +if (ret <0 ) { +dev_err (vi->dev,"failed to parse link for %pOF: %d\n" , +to_of_node (ep), ret); +continue ; + } + +if (link.local_port >= local->num_pads) { +dev_err (vi->dev,"invalid port number %u on %pOF\n" , + link.local_port,to_of_node (link.local_node)); +v4l2_fwnode_put_link (&link); + ret = -EINVAL ; +break ; + } + + local_pad = &local->pads[link.local_port]; +/* Remote node is vi node. So use channel video entity and pad +* as remote/sink. +*/ +if (link.remote_node ==of_fwnode_handle (vi->dev->of_node)) { + remote = &chan->video.entity; + remote_pad = &chan->pad; + goto create_link; + } + +/* +* Skip sink ports, they will be processed from the other end +* of the link. +*/ +if (local_pad->flags &MEDIA_PAD_FL_SINK ) { +dev_dbg (vi->dev,"skipping sink port %pOF:%u\n" , +to_of_node (link.local_node), link.local_port); +v4l2_fwnode_put_link (&link); +continue ; + } + +/* find the remote entity from notifier list */ + ent =tegra_vi_graph_find_entity (chan, link.remote_node); +if (!ent) { +dev_err (vi->dev,"no entity found for %pOF\n" , +to_of_node (link.remote_node)); +v4l2_fwnode_put_link (&link); + ret = -ENODEV ; +break ; + } + + remote = ent->entity; +if (link.remote_port >= remote->num_pads) { +dev_err (vi->dev,"invalid port number %u on %pOF\n" , + link.remote_port, +to_of_node (link.remote_node)); +v4l2_fwnode_put_link (&link); + ret = -EINVAL ; +break ; + } + + remote_pad = &remote->pads[link.remote_port]; + +create_link: +dev_dbg (vi->dev,"creating %s:%u -> %s:%u link\n" , + local->name, local_pad->index, + remote->name, remote_pad->index); + + ret =media_create_pad_link (local, local_pad->index, + remote, remote_pad->index, + link_flags); +v4l2_fwnode_put_link (&link); +if (ret <0 ) { +dev_err (vi->dev, +"failed to create %s:%u -> %s:%u link: %d\n" , + local->name, local_pad->index, + remote->name, remote_pad->index, ret); +break ; + } + } + +fwnode_handle_put (ep); +return ret; +} + +static int tegra_vi_graph_notify_complete (struct v4l2_async_notifier *notifier) +{ +struct tegra_vi_graph_entity *entity; +struct v4l2_async_subdev *asd; +struct v4l2_subdev *subdev;
drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1250
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan; +struct tegra_vi *vi; +int ret; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +dev_dbg (vi->dev,"notify complete, all subdevs registered\n" ); + + ret =video_register_device (&chan->video,VFL_TYPE_VIDEO ,-1 );
This should be done last after the tegra_vi_graph_build and tegra_channel_setup_ctrl_handler calls. The video device is immediately accessible after this call, so don't call it until everything is setup (i.e. until just before the 'return 0;' below).
Quoted 194 lines
drivers/staging/media/tegra-video/vi.c +194
-0+if (ret <0 ) { +dev_err (vi->dev, +"failed to register video device: %d\n" , ret); + goto unregister_video; + } + +/* create links between the entities */ +list_for_each_entry (asd, &chan->notifier.asd_list, asd_list) { + entity =to_tegra_vi_graph_entity (asd); + ret =tegra_vi_graph_build (chan, entity); +if (ret <0 ) + goto unregister_video; + } + + ret =tegra_channel_setup_ctrl_handler (chan); +if (ret <0 ) { +dev_err (vi->dev, +"failed to setup channel controls: %d\n" , ret); + goto unregister_video; + } + +vi_fmts_bitmap_init (chan); + subdev =tegra_channel_get_remote_subdev (chan, false); +v4l2_set_subdev_hostdata (subdev, chan); + +return 0 ; + +unregister_video: +video_unregister_device (&chan->video); +return ret; +} + +static int tegra_vi_graph_notify_bound (struct v4l2_async_notifier *notifier, +struct v4l2_subdev *subdev, +struct v4l2_async_subdev *asd) +{ +struct tegra_vi_graph_entity *entity; +struct tegra_vi *vi; +struct tegra_vi_channel *chan; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +/* +* Locate the entity corresponding to the bound subdev and store the +* subdev pointer. +*/ + entity =tegra_vi_graph_find_entity (chan, subdev->fwnode); +if (!entity) { +dev_err (vi->dev,"no entity for subdev %s\n" , subdev->name); +return -EINVAL ; + } + +if (entity->subdev) { +dev_err (vi->dev,"duplicate subdev for node %pOF\n" , +to_of_node (entity->asd.match.fwnode)); +return -EINVAL ; + } + +dev_dbg (vi->dev,"subdev %s bound\n" , subdev->name); + entity->entity = &subdev->entity; + entity->subdev = subdev; + +return 0 ; +} + +static void tegra_vi_graph_notify_unbind (struct v4l2_async_notifier *notifier, +struct v4l2_subdev *subdev, +struct v4l2_async_subdev *asd) +{ +struct tegra_vi_graph_entity *entity; +struct tegra_vi *vi; +struct tegra_vi_channel *chan; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +video_unregister_device (&chan->video); + +media_entity_remove_links (&chan->video.entity); + entity =tegra_vi_graph_find_entity (chan, subdev->fwnode); +if (entity) { +if (entity->entity) +media_entity_remove_links (entity->entity); + entity->entity =NULL ; + entity->subdev =NULL ; + } + +dev_dbg (vi->dev,"subdev %s unbind\n" , subdev->name); +} + +static const struct v4l2_async_notifier_operations tegra_vi_async_ops = { + .bound = tegra_vi_graph_notify_bound, + .complete = tegra_vi_graph_notify_complete, + .unbind = tegra_vi_graph_notify_unbind, +}; + +static int tegra_vi_graph_parse_one (struct tegra_vi_channel *chan, +struct fwnode_handle *fwnode) +{ +struct tegra_vi *vi = chan->vi; +struct fwnode_handle *ep =NULL ; +struct fwnode_handle *remote =NULL ; +struct v4l2_async_subdev *asd; +struct device_node *node =NULL ; +int ret; + +dev_dbg (vi->dev,"parsing node %pOF\n" ,to_of_node (fwnode)); + +/* parse all the remote entities and put them into the list */ +for_each_endpoint_of_node (to_of_node (fwnode), node) { + ep =of_fwnode_handle (node); + remote =fwnode_graph_get_remote_port_parent (ep); +if (!remote) { +dev_err (vi->dev, +"remote device at %pOF not found\n" , node); + ret = -EINVAL ; + goto cleanup; + } + +/* skip entities that are already processed */ +if (remote ==dev_fwnode (vi->dev) || +tegra_vi_graph_find_entity (chan, remote)) { +fwnode_handle_put (remote); +continue ; + } + + asd =v4l2_async_notifier_add_fwnode_subdev (&chan->notifier, + remote,sizeof (struct tegra_vi_graph_entity )); +if (IS_ERR (asd)) { + ret =PTR_ERR (asd); +dev_err (vi->dev, +"failed to add subdev to notifier: %d\n" , ret); +fwnode_handle_put (remote); + goto cleanup; + } + + ret =tegra_vi_graph_parse_one (chan, remote); +if (ret <0 ) { +fwnode_handle_put (remote); + goto cleanup; + } + +fwnode_handle_put (remote); + } + +return 0 ; + +cleanup: +dev_err (vi->dev,"failed parsing the graph: %d\n" , ret); +v4l2_async_notifier_cleanup (&chan->notifier); +of_node_put (node); +return ret; +} + +static int tegra_vi_graph_init (struct tegra_vi *vi) +{ +struct tegra_video_device *vid =dev_get_drvdata (vi->client.host); +struct tegra_vi_channel *chan; +struct fwnode_handle *fwnode =dev_fwnode (vi->dev); +int ret; +struct fwnode_handle *remote =NULL ; + +/* +* Walk the links to parse the full graph. Each channel will have +* one endpoint of the composite node. Start by parsing the +* composite node and parse the remote entities in turn. +* Each channel will register v4l2 async notifier to make the graph +* independent between the channels so we can the current channel +* in case of something wrong during graph parsing and continue with +* next channels. +*/ +list_for_each_entry (chan, &vi->vi_chans, list) { + remote =fwnode_graph_get_remote_node (fwnode, chan->portno,0 ); +if (!remote) +continue ; + + ret =tegra_vi_graph_parse_one (chan, remote); +fwnode_handle_put (remote); +if (ret <0 ||list_empty (&chan->notifier.asd_list)) +continue ; + + chan->notifier.ops = &tegra_vi_async_ops; + ret =v4l2_async_notifier_register (&vid->v4l2_dev, + &chan->notifier); +if (ret <0 ) { +dev_err (vi->dev, +"failed to register channel %d notifier: %d\n" , + chan->portno, ret); +v4l2_async_notifier_cleanup (&chan->notifier); + } + } + +return 0 ;
drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1454
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+} + +static void tegra_vi_graph_cleanup (struct tegra_vi *vi) +{ +struct tegra_vi_channel *chan; + +list_for_each_entry (chan, &vi->vi_chans, list) { +video_unregister_device (&chan->video); +mutex_lock (&chan->video_lock); +vb2_queue_release (&chan->queue);
No need for this since this is done in vb2_fop_release().
In fact, vb2_queue_release should never be called by drivers. Just using vb2_fop_release or __vb2_fop_release is sufficient.
The confusion is due to the fact that the name suggests that vb2_queue_release has to be balanced with vb2_queue_init, but that's not the case. Perhaps vb2_queue_stop or something like that might be a better name. I'll have to think about this since I see that a lot of drivers do this wrong.
Quoted 125 lines
drivers/staging/media/tegra-video/vi.c +24
-6+mutex_unlock (&chan->video_lock); +v4l2_async_notifier_unregister (&chan->notifier); +v4l2_async_notifier_cleanup (&chan->notifier); + } +} +static int tegra_vi_init (struct host1x_client *client) {struct tegra_video_device *vid =dev_get_drvdata (client->host);@@ -922,13 +1471,14 @@ static int tegra_vi_init(struct host1x_client *client)INIT_LIST_HEAD (&vi->vi_chans); -if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) ret =tegra_vi_tpg_channels_alloc (vi); -if (ret <0 ) { -dev_err (vi->dev, -"failed to allocate tpg channels: %d\n" , ret); - goto free_chans; - } +else + ret =tegra_vi_channels_alloc (vi); +if (ret <0 ) { +dev_err (vi->dev, +"failed to allocate vi channels: %d\n" , ret); + goto free_chans; } ret =tegra_vi_channels_init (vi);@@ -937,6 +1487,12 @@ static int tegra_vi_init(struct host1x_client *client) vid->vi = vi; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_vi_graph_init (vi); +if (ret <0 ) + goto free_chans; + } +return 0 ; free_chans:@@ -950,6 +1506,8 @@ static int tegra_vi_init(struct host1x_client *client)static int tegra_vi_exit (struct host1x_client *client) { +struct tegra_vi *vi =host1x_client_to_vi (client); +/* * Do not cleanup the channels here as application might still be * holding video device nodes. Channels cleanup will happen during @@ -957,6 +1515,9 @@ static int tegra_vi_exit(struct host1x_client *client)* device nodes are released. */ +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +tegra_vi_graph_cleanup (vi); +return 0 ; }drivers/staging/media/tegra-video/vi.h +21
-0@@ -14,6 +14,7 @@#include <linux/wait.h> #include <media/media-entity.h> +#include <media/v4l2-async.h> #include <media/v4l2-ctrls.h> #include <media/v4l2-device.h> #include <media/v4l2-dev.h> @@ -93,6 +94,19 @@ struct tegra_vi { };/** +* struct tegra_vi_graph_entity - Entity in the video graph +* +* @asd: subdev asynchronous registration information +* @entity: media entity from the corresponding V4L2 subdev +* @subdev: V4L2 subdev +*/ +struct tegra_vi_graph_entity { +struct v4l2_async_subdev asd; +struct media_entity *entity; +struct v4l2_subdev *subdev; +}; + +/** * struct tegra_vi_channel - Tegra video channel * * @list: list head for this entry @@ -138,10 +152,13 @@ struct tegra_vi {* @done_lock: protects the capture done queue list * * @portno: VI channel port number +* @of_node: device node of VI channel * * @ctrl_handler: V4L2 control handler of this video channel +* @fmts_bitmap: a bitmap for supported formats matching v4l2 subdev formats * @tpg_fmts_bitmap: a bitmap for supported TPG formats * @pg_mode: test pattern generator mode (disabled/direct/patch) +* @notifier: V4L2 asynchronous subdevs notifier */ struct tegra_vi_channel {struct list_head list;@@ -174,10 +191,14 @@ struct tegra_vi_channel {spinlock_t done_lock;unsigned char portno; +struct device_node *of_node;struct v4l2_ctrl_handler ctrl_handler; +DECLARE_BITMAP (fmts_bitmap,MAX_FORMAT_NUM );DECLARE_BITMAP (tpg_fmts_bitmap,MAX_FORMAT_NUM );enum tegra_vi_pg_mode pg_mode; + +struct v4l2_async_notifier notifier; };/**
drivers/staging/media/tegra-video/vi.h extern const struct tegra_vi_soc tegra210_vi_soc; · line 276
Quoted 8 lines
drivers/staging/media/tegra-video/vi.h +1
-1@@ -249,7 +270,7 @@ extern const struct tegra_vi_soc tegra210_vi_soc;#endif struct v4l2_subdev * -tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan); +tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan,bool sensor);int tegra_channel_set_stream (struct tegra_vi_channel *chan,bool on);void tegra_channel_release_buffers (struct tegra_vi_channel *chan,enum vb2_buffer_state state);
Regards,
Hans
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Quoted 7 lines · Hans Verkuil
Hi Sowjanya,
As promised, here is the review of this remaining patch. I've now reviewed and tested the whole series.
I have some more patches pending for the imx274 but some of that needs a bit more testing. I hope to be able to post those soon.
Thanks Hans. Will have v3 with all changes based on this feedback.
Quoted 961 lines · Sowjanya Komatineni
Quoted 27 lines
This patch adds support to capture from the external sensor based on device graph in the device tree.
Driver walks through the device graph to create media links between the entities and registers and unregisters video devices when the corresponding sub-devices are bound and unbound.
Channel formats are enumerated based on available formats from the sensor and the corresponding matched formats from the Tegra supported video formats list.
Each Tegra CSI instance can be configured as 4-lane or 2-lane based on supported lane configuration from the sensor through the device tree.
Currently this driver supports V4L2 video node centric only.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/Kconfig | 1 + drivers/staging/media/tegra-video/csi.c | 128 +++++- drivers/staging/media/tegra-video/csi.h | 1 + drivers/staging/media/tegra-video/tegra210.c | 2 +- drivers/staging/media/tegra-video/vi.c | 623 +++++++++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- 6 files changed, 726 insertions(+), 52 deletions(-)<snip>
Quoted 26 lines
drivers/staging/media/tegra-video/vi.c +7
-0@@ -12,6 +12,7 @@#include <linux/module.h> #include <linux/of.h> #include <linux/of_device.h> +#include <linux/of_graph.h> #include <linux/platform_device.h> #include <linux/regulator/consumer.h> #include <linux/pm_runtime.h> @@ -52,6 +53,12 @@ to_tegra_channel_buffer(struct vb2_v4l2_buffer *vb) return container_of(vb, struct tegra_channel_buffer, buf); } +static inline struct tegra_vi_graph_entity * +to_tegra_vi_graph_entity (struct v4l2_async_subdev *asd) +{ + return container_of(asd, struct tegra_vi_graph_entity, asd); +} +static int tegra_get_format_idx_by_code (struct tegra_vi *vi,unsigned int code,unsigned int offset)drivers/staging/media/tegra-video/vi.c static void tegra_channel_buffer_queue(struct vb2_buffer *vb) · line 156
Quoted 5 lines
drivers/staging/media/tegra-video/vi.c +1
-1@@ -146,7 +153,7 @@ static void tegra_channel_buffer_queue(struct vb2_buffer *vb) }struct v4l2_subdev * -tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan) +tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan,bool sensor)Hmm, this 'sensor' argument is, I think, a bit too obscure.
I would rename this function to
tegra_channel_get_remote_csi_subdev, which is the equivalent of setting 'sensor' to false, and add a newtegra_channel_get_remote_sensor_subdev()function that calls this function and then does the 'while (1)' loop.That will make the code more readable since it is clear what the intention is.
A better alternative to
tegra_channel_get_remote_sensor_subdev()might betegra_channel_get_remote_source_subdev()since that covers both the sensor and TPG case.drivers/staging/media/tegra-video/vi.c tegra_channel_get_remote_subdev(struct tegra_vi_channel *chan) · line 168
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +3
-0{struct media_pad *pad;struct v4l2_subdev *subdev;@@ -156,6 +163,24 @@ tegra_channel_get_remote_subdev(struct tegra_vi_channel *chan) entity = pad->entity; subdev =media_entity_to_v4l2_subdev (entity); +if (sensor) { +while (1 ) { +if ((pad->index -1 ) <0 )'index' is a u16, so I'd rewrite this as 'if (
pad->index< 1)' to avoid signedness issues.Quoted 19 lines
drivers/staging/media/tegra-video/vi.c +15
-0+break ; + + pad = &entity->pads[pad->index -1 ]; +if (!(pad->flags &MEDIA_PAD_FL_SINK )) +break ; + + pad =media_entity_remote_pad (pad); +if (!pad || !is_media_entity_v4l2_subdev (pad->entity)) +break ; + + entity = pad->entity; + subdev =media_entity_to_v4l2_subdev (entity); + } + } +return subdev; }drivers/staging/media/tegra-video/vi.c int tegra_channel_set_stream(struct tegra_vi_channel *chan, bool on) · line 193
Quoted 5 lines
drivers/staging/media/tegra-video/vi.c +1
-1@@ -165,7 +190,15 @@ int tegra_channel_set_stream(struct tegra_vi_channel *chan, bool on)int ret;/* stream CSI */ - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, !on);'!on' is a bit too obscure. I see what the intention is (to stream on, first enable the csi, then the sensor, and the reverse to stream off), but it is not exactly obvious at first reading, and it conflicts with the 'stream CSI' comment.
Quoted 107 lines
drivers/staging/media/tegra-video/vi.c +35
-8+ ret =v4l2_subdev_call (subdev, video, s_stream, on); +if (on && ret <0 && ret != -ENOIOCTLCMD ) +return ret; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return 0 ; + + subdev =tegra_channel_get_remote_subdev (chan, on); ret =v4l2_subdev_call (subdev, video, s_stream, on);if (on && ret <0 && ret != -ENOIOCTLCMD )return ret;@@ -252,7 +285,7 @@ static int tegra_channel_g_parm(struct file *file, void *fh,struct tegra_vi_channel *chan =video_drvdata (file);struct v4l2_subdev *subdev; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true);return v4l2_g_parm_cap (&chan->video, subdev, a); }@@ -262,7 +295,7 @@ static int tegra_channel_s_parm(struct file *file, void *fh,struct tegra_vi_channel *chan =video_drvdata (file);struct v4l2_subdev *subdev; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true);return v4l2_s_parm_cap (&chan->video, subdev, a); }@@ -284,7 +317,7 @@ static int tegra_channel_enum_framesizes(struct file *file, void *fh, fse.code = fmtinfo->code; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true); ret =v4l2_subdev_call (subdev, pad, enum_frame_size,NULL , &fse);if (ret)return ret;@@ -316,7 +349,7 @@ static int tegra_channel_enum_frameintervals(struct file *file, void *fh, fie.code = fmtinfo->code; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true); ret =v4l2_subdev_call (subdev, pad, enum_frame_interval,NULL , &fie);if (ret)return ret;@@ -335,6 +368,9 @@ static int tegra_channel_enum_format(struct file *file, void *fh,unsigned int index =0 , i;unsigned long *fmts_bitmap = chan->tpg_fmts_bitmap; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) + fmts_bitmap = chan->fmts_bitmap; +if (f->index >=bitmap_weight (fmts_bitmap,MAX_FORMAT_NUM ))return -EINVAL ;@@ -391,8 +427,9 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan,struct v4l2_subdev *subdev;struct v4l2_subdev_format fmt;struct v4l2_subdev_pad_config *pad_cfg; +int ret; - subdev =tegra_channel_get_remote_subdev (chan); + subdev =tegra_channel_get_remote_subdev (chan, true); pad_cfg =v4l2_subdev_alloc_pad_config (subdev);if (!pad_cfg)return -ENOMEM ;@@ -412,7 +449,10 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan, fmt.which =V4L2_SUBDEV_FORMAT_TRY ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); -v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt); + ret =v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt); +if (ret <0 ) +return ret; +v4l2_fill_pix_format (pix, &fmt.format);tegra_channel_fmt_align (chan, pix, fmtinfo->bpp);@@ -452,8 +492,11 @@ static int tegra_channel_set_format(struct file *file, void *fh, fmt.which =V4L2_SUBDEV_FORMAT_ACTIVE ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); - subdev =tegra_channel_get_remote_subdev (chan); -v4l2_subdev_call (subdev, pad, set_fmt,NULL , &fmt); + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, set_fmt,NULL , &fmt); +if (ret <0 ) +return ret; +v4l2_fill_pix_format (pix, &fmt.format);tegra_channel_fmt_align (chan, pix, fmtinfo->bpp);@@ -463,15 +506,52 @@ static int tegra_channel_set_format(struct file *file, void *fh,return 0 ; } +static int tegra_channel_set_subdev_active_fmt (struct tegra_vi_channel *chan) +{ +int ret, index; +const struct tegra_video_format *fmtinfo; +struct v4l2_subdev *subdev; +struct v4l2_subdev_format fmt = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; +drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_format(struct file *file, void *fh, · line 527
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+/* +* Initialize channel format to the sub-device active format if there +* is corresponding match in the Tegra supported video formats. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, get_fmt,NULL , &fmt); +if (ret) +return ret; + + index =tegra_get_format_idx_by_code (chan->vi, fmt.format.code,0 );index can be negative...
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_format(struct file *file, void *fh, · line 529
Quoted 2 lines
drivers/staging/media/tegra-video/vi.c +2
-0+ fmtinfo = &chan->vi->soc->video_formats[index]; +if (!fmtinfo)... and fmtinfo can never be NULL
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_format(struct file *file, void *fh, · line 530
Quoted 1 line
drivers/staging/media/tegra-video/vi.c +1
-0+return -EINVAL ;I'm not really sure what the intention is here, but I suspect something like this:
if (index < 0) return -EINVAL;Quoted 88 lines
drivers/staging/media/tegra-video/vi.c +65
-2+ + chan->fmtinfo = fmtinfo; +v4l2_fill_pix_format (&chan->format, &fmt.format); + chan->format.pixelformat = chan->fmtinfo->fourcc; + chan->format.bytesperline = chan->format.width * chan->fmtinfo->bpp; + chan->format.sizeimage = chan->format.bytesperline * + chan->format.height; +tegra_channel_fmt_align (chan, &chan->format, chan->fmtinfo->bpp); + +return 0 ; +} +static int tegra_channel_enum_input (struct file *file,void *fh,struct v4l2_input *inp) { -/* currently driver supports internal TPG only */ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +if (inp->index)return -EINVAL ; inp->type =V4L2_INPUT_TYPE_CAMERA ; -strscpy (inp->name,"Tegra TPG" ,sizeof (inp->name)); + subdev =tegra_channel_get_remote_subdev (chan, true); +strscpy (inp->name, subdev->name,sizeof (inp->name));return 0 ; }@@ -578,6 +658,19 @@ static int tegra_channel_setup_ctrl_handler(struct tegra_vi_channel *chan)v4l2_ctrl_handler_free (&chan->ctrl_handler); return chan->ctrl_handler.error; } +#else +struct v4l2_subdev *subdev; + + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_ctrl_add_handler (&chan->ctrl_handler, subdev->ctrl_handler, +NULL , true); +if (ret <0 ) { +dev_err (chan->vi->dev, +"failed to add subdev %s ctrl handler: %d\n" , + subdev->name, ret); +v4l2_ctrl_handler_free (&chan->ctrl_handler); +return ret; + }#endif /* setup the controls */ @@ -608,6 +701,57 @@ static void vi_tpg_fmts_bitmap_init(struct tegra_vi_channel *chan)bitmap_set (chan->tpg_fmts_bitmap, index,1 ); } +static void vi_fmts_bitmap_init (struct tegra_vi_channel *chan) +{ +int index, ret, match_code =0 ; +struct v4l2_subdev *subdev; +struct v4l2_subdev_mbus_code_enum code = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; + +bitmap_zero (chan->fmts_bitmap,MAX_FORMAT_NUM ); + +/* +* Set the bitmap bits based on all the matched formats between the +* available media bus formats of sub-device and the pre-defined Tegra +* supported video formats. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); +while (1 ) { + ret =v4l2_subdev_call (subdev, pad, enum_mbus_code, +NULL , &code); +if (ret <0 ) +break ; + + index =tegra_get_format_idx_by_code (chan->vi, code.code,0 ); +while (index >=0 ) { +bitmap_set (chan->fmts_bitmap, index,1 ); +if (!match_code) + match_code = code.code; +/* look for other formats with same mbus code */ + index =tegra_get_format_idx_by_code (chan->vi, + code.code, + index +1 ); + } + + code.index++; + }drivers/staging/media/tegra-video/vi.c static void vi_tpg_fmts_bitmap_init(struct tegra_vi_channel *chan) · line 748
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+ +/* +* Set the bitmap bit corresponding to default tegra video format if +* there are no matched formats. +*/ +if (!match_code) { + match_code = tegra_default_format.code; + index =tegra_get_format_idx_by_code (chan->vi, match_code,0 ); +if (index >=0 ) +bitmap_set (chan->fmts_bitmap, index,1 );If index < 0, then you end up with an all zero
fmts_bitmap.A
WARN_ONis the minimum action to take in that case, but you should probably return an error since this really should not happen.Quoted 247 lines
drivers/staging/media/tegra-video/vi.c +204
-13+ } + +/* initialize channel format to the sub-device active format */ +tegra_channel_set_subdev_active_fmt (chan); +} +static void tegra_channel_cleanup (struct tegra_vi_channel *chan) {v4l2_ctrl_handler_free (&chan->ctrl_handler);@@ -720,6 +864,9 @@ static int tegra_channel_init(struct tegra_vi_channel *chan) goto free_v4l2_ctrl_hdl; } +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +v4l2_async_notifier_init (&chan->notifier); +return 0 ; free_v4l2_ctrl_hdl:@@ -733,28 +880,84 @@ static int tegra_channel_init(struct tegra_vi_channel *chan)return ret; } -static int tegra_vi_tpg_channels_alloc (struct tegra_vi *vi) +static int tegra_vi_channel_alloc (struct tegra_vi *vi,unsigned int port_num, +struct device_node *node) {struct tegra_vi_channel *chan; + +/* +* Do not use devm_kzalloc as memory is freed immediately +* when device instance is unbound but application might still +* be holding the device node open. Channel memory allocated +* with kzalloc is freed during video device release callback. +*/ + chan =kzalloc (sizeof (*chan),GFP_KERNEL ); +if (!chan) +return -ENOMEM ; + + chan->vi = vi; + chan->portno = port_num; + chan->of_node = node; +list_add_tail (&chan->list, &vi->vi_chans); + +return 0 ; +} + +static int tegra_vi_tpg_channels_alloc (struct tegra_vi *vi) +{unsigned int port_num;unsigned int nchannels = vi->soc->vi_max_channels; +int ret;for (port_num =0 ; port_num < nchannels; port_num++) { -/* -* Do not use devm_kzalloc as memory is freed immediately -* when device instance is unbound but application might still -* be holding the device node open. Channel memory allocated -* with kzalloc is freed during video device release callback. -*/ - chan =kzalloc (sizeof (*chan),GFP_KERNEL ); -if (!chan) -return -ENOMEM ; + ret =tegra_vi_channel_alloc (vi, port_num, vi->dev->of_node); +if (ret <0 ) +return ret; + } + +return 0 ; +} + +static int tegra_vi_channels_alloc (struct tegra_vi *vi) +{ +struct device_node *node = vi->dev->of_node; +struct device_node *ep =NULL ; +struct device_node *ports; +struct device_node *port; +unsigned int port_num; +int ret; + + ports =of_get_child_by_name (node,"ports" ); +if (!ports) +return -ENODEV ; + +for_each_child_of_node (ports, port) { +if (!of_node_name_eq (port,"port" )) +continue ; + + ret =of_property_read_u32 (port,"reg" , &port_num); +if (ret <0 ) +continue ; + +if (port_num > vi->soc->vi_max_channels) { +of_node_put (ports); +dev_err (vi->dev,"invalid port num %d\n" , port_num); +return -EINVAL ; + } + + ep =of_get_child_by_name (port,"endpoint" ); +if (!ep) +continue ; - chan->vi = vi; - chan->portno = port_num; -list_add_tail (&chan->list, &vi->vi_chans); +of_node_put (ep); + ret =tegra_vi_channel_alloc (vi, port_num, port); +if (ret <0 ) { +of_node_put (ports); +return ret; + } } +of_node_put (ports);return 0 ; }@@ -909,6 +1112,352 @@ static int __maybe_unused vi_runtime_suspend(struct device *dev)return 0 ; } +/* +* Graph Management +*/ +static struct tegra_vi_graph_entity * +tegra_vi_graph_find_entity (struct tegra_vi_channel *chan, +const struct fwnode_handle *fwnode) +{ +struct tegra_vi_graph_entity *entity; +struct v4l2_async_subdev *asd; + +list_for_each_entry (asd, &chan->notifier.asd_list, asd_list) { + entity =to_tegra_vi_graph_entity (asd); +if (entity->asd.match.fwnode == fwnode) +return entity; + } + +return NULL ; +} + +static int tegra_vi_graph_build (struct tegra_vi_channel *chan, +struct tegra_vi_graph_entity *entity) +{ +struct tegra_vi *vi = chan->vi; +struct tegra_vi_graph_entity *ent; +struct fwnode_handle *ep =NULL ; +struct v4l2_fwnode_link link; +struct media_entity *local = entity->entity; +struct media_entity *remote; +struct media_pad *local_pad; +struct media_pad *remote_pad; +u32 link_flags =MEDIA_LNK_FL_ENABLED ; +int ret =0 ; + +dev_dbg (vi->dev,"creating links for entity %s\n" , local->name); + +while (1 ) { + ep =fwnode_graph_get_next_endpoint (entity->asd.match.fwnode, + ep); +if (!ep) +break ; + + ret =v4l2_fwnode_parse_link (ep, &link); +if (ret <0 ) { +dev_err (vi->dev,"failed to parse link for %pOF: %d\n" , +to_of_node (ep), ret); +continue ; + } + +if (link.local_port >= local->num_pads) { +dev_err (vi->dev,"invalid port number %u on %pOF\n" , + link.local_port,to_of_node (link.local_node)); +v4l2_fwnode_put_link (&link); + ret = -EINVAL ; +break ; + } + + local_pad = &local->pads[link.local_port]; +/* Remote node is vi node. So use channel video entity and pad +* as remote/sink. +*/ +if (link.remote_node ==of_fwnode_handle (vi->dev->of_node)) { + remote = &chan->video.entity; + remote_pad = &chan->pad; + goto create_link; + } + +/* +* Skip sink ports, they will be processed from the other end +* of the link. +*/ +if (local_pad->flags &MEDIA_PAD_FL_SINK ) { +dev_dbg (vi->dev,"skipping sink port %pOF:%u\n" , +to_of_node (link.local_node), link.local_port); +v4l2_fwnode_put_link (&link); +continue ; + } + +/* find the remote entity from notifier list */ + ent =tegra_vi_graph_find_entity (chan, link.remote_node); +if (!ent) { +dev_err (vi->dev,"no entity found for %pOF\n" , +to_of_node (link.remote_node)); +v4l2_fwnode_put_link (&link); + ret = -ENODEV ; +break ; + } + + remote = ent->entity; +if (link.remote_port >= remote->num_pads) { +dev_err (vi->dev,"invalid port number %u on %pOF\n" , + link.remote_port, +to_of_node (link.remote_node)); +v4l2_fwnode_put_link (&link); + ret = -EINVAL ; +break ; + } + + remote_pad = &remote->pads[link.remote_port]; + +create_link: +dev_dbg (vi->dev,"creating %s:%u -> %s:%u link\n" , + local->name, local_pad->index, + remote->name, remote_pad->index); + + ret =media_create_pad_link (local, local_pad->index, + remote, remote_pad->index, + link_flags); +v4l2_fwnode_put_link (&link); +if (ret <0 ) { +dev_err (vi->dev, +"failed to create %s:%u -> %s:%u link: %d\n" , + local->name, local_pad->index, + remote->name, remote_pad->index, ret); +break ; + } + } + +fwnode_handle_put (ep); +return ret; +} + +static int tegra_vi_graph_notify_complete (struct v4l2_async_notifier *notifier) +{ +struct tegra_vi_graph_entity *entity; +struct v4l2_async_subdev *asd; +struct v4l2_subdev *subdev;drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1250
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan; +struct tegra_vi *vi; +int ret; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +dev_dbg (vi->dev,"notify complete, all subdevs registered\n" ); + + ret =video_register_device (&chan->video,VFL_TYPE_VIDEO ,-1 );This should be done last after the
tegra_vi_graph_buildandtegra_channel_setup_ctrl_handlercalls. The video device is immediately accessible after this call, so don't call it until everything is setup (i.e. until just before the 'return 0;' below).Quoted 194 lines
drivers/staging/media/tegra-video/vi.c +194
-0+if (ret <0 ) { +dev_err (vi->dev, +"failed to register video device: %d\n" , ret); + goto unregister_video; + } + +/* create links between the entities */ +list_for_each_entry (asd, &chan->notifier.asd_list, asd_list) { + entity =to_tegra_vi_graph_entity (asd); + ret =tegra_vi_graph_build (chan, entity); +if (ret <0 ) + goto unregister_video; + } + + ret =tegra_channel_setup_ctrl_handler (chan); +if (ret <0 ) { +dev_err (vi->dev, +"failed to setup channel controls: %d\n" , ret); + goto unregister_video; + } + +vi_fmts_bitmap_init (chan); + subdev =tegra_channel_get_remote_subdev (chan, false); +v4l2_set_subdev_hostdata (subdev, chan); + +return 0 ; + +unregister_video: +video_unregister_device (&chan->video); +return ret; +} + +static int tegra_vi_graph_notify_bound (struct v4l2_async_notifier *notifier, +struct v4l2_subdev *subdev, +struct v4l2_async_subdev *asd) +{ +struct tegra_vi_graph_entity *entity; +struct tegra_vi *vi; +struct tegra_vi_channel *chan; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +/* +* Locate the entity corresponding to the bound subdev and store the +* subdev pointer. +*/ + entity =tegra_vi_graph_find_entity (chan, subdev->fwnode); +if (!entity) { +dev_err (vi->dev,"no entity for subdev %s\n" , subdev->name); +return -EINVAL ; + } + +if (entity->subdev) { +dev_err (vi->dev,"duplicate subdev for node %pOF\n" , +to_of_node (entity->asd.match.fwnode)); +return -EINVAL ; + } + +dev_dbg (vi->dev,"subdev %s bound\n" , subdev->name); + entity->entity = &subdev->entity; + entity->subdev = subdev; + +return 0 ; +} + +static void tegra_vi_graph_notify_unbind (struct v4l2_async_notifier *notifier, +struct v4l2_subdev *subdev, +struct v4l2_async_subdev *asd) +{ +struct tegra_vi_graph_entity *entity; +struct tegra_vi *vi; +struct tegra_vi_channel *chan; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +video_unregister_device (&chan->video); + +media_entity_remove_links (&chan->video.entity); + entity =tegra_vi_graph_find_entity (chan, subdev->fwnode); +if (entity) { +if (entity->entity) +media_entity_remove_links (entity->entity); + entity->entity =NULL ; + entity->subdev =NULL ; + } + +dev_dbg (vi->dev,"subdev %s unbind\n" , subdev->name); +} + +static const struct v4l2_async_notifier_operations tegra_vi_async_ops = { + .bound = tegra_vi_graph_notify_bound, + .complete = tegra_vi_graph_notify_complete, + .unbind = tegra_vi_graph_notify_unbind, +}; + +static int tegra_vi_graph_parse_one (struct tegra_vi_channel *chan, +struct fwnode_handle *fwnode) +{ +struct tegra_vi *vi = chan->vi; +struct fwnode_handle *ep =NULL ; +struct fwnode_handle *remote =NULL ; +struct v4l2_async_subdev *asd; +struct device_node *node =NULL ; +int ret; + +dev_dbg (vi->dev,"parsing node %pOF\n" ,to_of_node (fwnode)); + +/* parse all the remote entities and put them into the list */ +for_each_endpoint_of_node (to_of_node (fwnode), node) { + ep =of_fwnode_handle (node); + remote =fwnode_graph_get_remote_port_parent (ep); +if (!remote) { +dev_err (vi->dev, +"remote device at %pOF not found\n" , node); + ret = -EINVAL ; + goto cleanup; + } + +/* skip entities that are already processed */ +if (remote ==dev_fwnode (vi->dev) || +tegra_vi_graph_find_entity (chan, remote)) { +fwnode_handle_put (remote); +continue ; + } + + asd =v4l2_async_notifier_add_fwnode_subdev (&chan->notifier, + remote,sizeof (struct tegra_vi_graph_entity )); +if (IS_ERR (asd)) { + ret =PTR_ERR (asd); +dev_err (vi->dev, +"failed to add subdev to notifier: %d\n" , ret); +fwnode_handle_put (remote); + goto cleanup; + } + + ret =tegra_vi_graph_parse_one (chan, remote); +if (ret <0 ) { +fwnode_handle_put (remote); + goto cleanup; + } + +fwnode_handle_put (remote); + } + +return 0 ; + +cleanup: +dev_err (vi->dev,"failed parsing the graph: %d\n" , ret); +v4l2_async_notifier_cleanup (&chan->notifier); +of_node_put (node); +return ret; +} + +static int tegra_vi_graph_init (struct tegra_vi *vi) +{ +struct tegra_video_device *vid =dev_get_drvdata (vi->client.host); +struct tegra_vi_channel *chan; +struct fwnode_handle *fwnode =dev_fwnode (vi->dev); +int ret; +struct fwnode_handle *remote =NULL ; + +/* +* Walk the links to parse the full graph. Each channel will have +* one endpoint of the composite node. Start by parsing the +* composite node and parse the remote entities in turn. +* Each channel will register v4l2 async notifier to make the graph +* independent between the channels so we can the current channel +* in case of something wrong during graph parsing and continue with +* next channels. +*/ +list_for_each_entry (chan, &vi->vi_chans, list) { + remote =fwnode_graph_get_remote_node (fwnode, chan->portno,0 ); +if (!remote) +continue ; + + ret =tegra_vi_graph_parse_one (chan, remote); +fwnode_handle_put (remote); +if (ret <0 ||list_empty (&chan->notifier.asd_list)) +continue ; + + chan->notifier.ops = &tegra_vi_async_ops; + ret =v4l2_async_notifier_register (&vid->v4l2_dev, + &chan->notifier); +if (ret <0 ) { +dev_err (vi->dev, +"failed to register channel %d notifier: %d\n" , + chan->portno, ret); +v4l2_async_notifier_cleanup (&chan->notifier); + } + } + +return 0 ;drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1454
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+} + +static void tegra_vi_graph_cleanup (struct tegra_vi *vi) +{ +struct tegra_vi_channel *chan; + +list_for_each_entry (chan, &vi->vi_chans, list) { +video_unregister_device (&chan->video); +mutex_lock (&chan->video_lock); +vb2_queue_release (&chan->queue);No need for this since this is done in
vb2_fop_release().In fact,
vb2_queue_releaseshould never be called by drivers. Just usingvb2_fop_releaseor__vb2_fop_releaseis sufficient.The confusion is due to the fact that the name suggests that
vb2_queue_releasehas to be balanced withvb2_queue_init, but that's not the case. Perhapsvb2_queue_stopor something like that might be a better name. I'll have to think about this since I see that a lot of drivers do this wrong.Quoted 125 lines
drivers/staging/media/tegra-video/vi.c +24
-6+mutex_unlock (&chan->video_lock); +v4l2_async_notifier_unregister (&chan->notifier); +v4l2_async_notifier_cleanup (&chan->notifier); + } +} +static int tegra_vi_init (struct host1x_client *client) {struct tegra_video_device *vid =dev_get_drvdata (client->host);@@ -922,13 +1471,14 @@ static int tegra_vi_init(struct host1x_client *client)INIT_LIST_HEAD (&vi->vi_chans); -if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) ret =tegra_vi_tpg_channels_alloc (vi); -if (ret <0 ) { -dev_err (vi->dev, -"failed to allocate tpg channels: %d\n" , ret); - goto free_chans; - } +else + ret =tegra_vi_channels_alloc (vi); +if (ret <0 ) { +dev_err (vi->dev, +"failed to allocate vi channels: %d\n" , ret); + goto free_chans; } ret =tegra_vi_channels_init (vi);@@ -937,6 +1487,12 @@ static int tegra_vi_init(struct host1x_client *client) vid->vi = vi; +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) { + ret =tegra_vi_graph_init (vi); +if (ret <0 ) + goto free_chans; + } +return 0 ; free_chans:@@ -950,6 +1506,8 @@ static int tegra_vi_init(struct host1x_client *client)static int tegra_vi_exit (struct host1x_client *client) { +struct tegra_vi *vi =host1x_client_to_vi (client); +/* * Do not cleanup the channels here as application might still be * holding video device nodes. Channels cleanup will happen during @@ -957,6 +1515,9 @@ static int tegra_vi_exit(struct host1x_client *client)* device nodes are released. */ +if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +tegra_vi_graph_cleanup (vi); +return 0 ; }drivers/staging/media/tegra-video/vi.h +21
-0@@ -14,6 +14,7 @@#include <linux/wait.h> #include <media/media-entity.h> +#include <media/v4l2-async.h> #include <media/v4l2-ctrls.h> #include <media/v4l2-device.h> #include <media/v4l2-dev.h> @@ -93,6 +94,19 @@ struct tegra_vi { };/** +* struct tegra_vi_graph_entity - Entity in the video graph +* +* @asd: subdev asynchronous registration information +* @entity: media entity from the corresponding V4L2 subdev +* @subdev: V4L2 subdev +*/ +struct tegra_vi_graph_entity { +struct v4l2_async_subdev asd; +struct media_entity *entity; +struct v4l2_subdev *subdev; +}; + +/** * struct tegra_vi_channel - Tegra video channel * * @list: list head for this entry @@ -138,10 +152,13 @@ struct tegra_vi {* @done_lock: protects the capture done queue list * * @portno: VI channel port number +* @of_node: device node of VI channel * * @ctrl_handler: V4L2 control handler of this video channel +* @fmts_bitmap: a bitmap for supported formats matching v4l2 subdev formats * @tpg_fmts_bitmap: a bitmap for supported TPG formats * @pg_mode: test pattern generator mode (disabled/direct/patch) +* @notifier: V4L2 asynchronous subdevs notifier */ struct tegra_vi_channel {struct list_head list;@@ -174,10 +191,14 @@ struct tegra_vi_channel {spinlock_t done_lock;unsigned char portno; +struct device_node *of_node;struct v4l2_ctrl_handler ctrl_handler; +DECLARE_BITMAP (fmts_bitmap,MAX_FORMAT_NUM );DECLARE_BITMAP (tpg_fmts_bitmap,MAX_FORMAT_NUM );enum tegra_vi_pg_mode pg_mode; + +struct v4l2_async_notifier notifier; };/** drivers/staging/media/tegra-video/vi.h extern const struct tegra_vi_soc tegra210_vi_soc; · line 276
Quoted 8 lines
drivers/staging/media/tegra-video/vi.h +1
-1@@ -249,7 +270,7 @@ extern const struct tegra_vi_soc tegra210_vi_soc;#endif struct v4l2_subdev * -tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan); +tegra_channel_get_remote_subdev (struct tegra_vi_channel *chan,bool sensor);int tegra_channel_set_stream (struct tegra_vi_channel *chan,bool on);void tegra_channel_release_buffers (struct tegra_vi_channel *chan,enum vb2_buffer_state state);Regards,
Hans
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Quoted 44 lines · Sowjanya Komatineni
Quoted 19 lines · Hans Verkuil
Quoted 5 lines
drivers/staging/media/tegra-video/vi.c +5
-0+static int tegra_vi_graph_notify_complete (struct v4l2_async_notifier *notifier) +{ +struct tegra_vi_graph_entity *entity; +struct v4l2_async_subdev *asd; +struct v4l2_subdev *subdev;drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1250
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan; +struct tegra_vi *vi; +int ret; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +dev_dbg (vi->dev,"notify complete, all subdevs registered\n" ); + + ret =video_register_device (&chan->video,VFL_TYPE_VIDEO ,-1 );This should be done last after the
tegra_vi_graph_buildandtegra_channel_setup_ctrl_handlercalls. The video device is immediately accessible after this call, so don't call it until everything is setup (i.e. until just before the 'return 0;' below).Quoted 14 lines
Quoted 4 lines
drivers/staging/media/tegra-video/vi.c +4
-0+if (ret <0 ) { +dev_err (vi->dev, +"failed to register video device: %d\n" , ret); + goto unregister_video;drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1264
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+ } + +/* create links between the entities */ +list_for_each_entry (asd, &chan->notifier.asd_list, asd_list) { + entity =to_tegra_vi_graph_entity (asd); + ret =tegra_vi_graph_build (chan, entity); +if (ret <0 ) + goto unregister_video; + } +Hi Hans,
Currently Tegra video driver sets
v4l2_dev->mdevprior to graph parse and building links to letmedia_device_register_entity()to happen duringvideo_register_device()->video_register_media_controller()andmedia_device_unregister_entity()to happen duringv4l2_device_release()TPG also does the same of letting media entity register/unregister to happen during video device register and release callback.
So, registering video device prior to media links creation as
media_device_register_entity()will happen duringvideo_register_device()
Quoted 8 lines
To register video device after creating media links, it need to change for both TPG and Non-TPG to not set
v4l2_dev->mdevand Tegra video driver should explicitly take care ofmedia_device_register_entity()andmedia_device_unregister_entity().Prior to making this change to both TPG and Non-TPG, would like to understand on possibility of using video device node prior to finishing complete driver
probe()As video device register happens during async notifier complete callback, and all the device graph build happens during video driver
probe()what exactly will be the issue of having video device node prior to creating media links?
It's not the 'create links between the entities' bit that's the problem, it is what follows:
+ ret = tegra_channel_setup_ctrl_handler(chan);
+ if (ret < 0) {
+ dev_err(vi->dev,
+ "failed to setup channel controls: %d\n", ret);
+ goto unregister_video;
+ }
+
+ vi_fmts_bitmap_init(chan);
+ subdev = tegra_channel_get_remote_subdev(chan, false);
+ v4l2_set_subdev_hostdata(subdev, chan);
That should be done before the video_register_device call.
Because otherwise the /dev/videoX doesn't have the full set of controls, and I am also not certain which ioctls might use the subdev hostdata.
The core problem is really that video_register_device should have been split into an init function and a register function, so it is possible to set everything up before registering the video device. Oh well...
Regards,
Hans
Quoted 9 lines
I see some other drivers also doing the same order of registering video device prior to creating media links and also we are doing the same in L4T driver as well.
Thanks
Sowjanya
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Quoted 65 lines · Hans Verkuil
Quoted 43 lines · Sowjanya Komatineni
Quoted 19 lines · Hans Verkuil
Quoted 5 lines
drivers/staging/media/tegra-video/vi.c +5
-0+static int tegra_vi_graph_notify_complete (struct v4l2_async_notifier *notifier) +{ +struct tegra_vi_graph_entity *entity; +struct v4l2_async_subdev *asd; +struct v4l2_subdev *subdev;drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1250
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan; +struct tegra_vi *vi; +int ret; + + chan = container_of(notifier, struct tegra_vi_channel, notifier); + vi = chan->vi; + +dev_dbg (vi->dev,"notify complete, all subdevs registered\n" ); + + ret =video_register_device (&chan->video,VFL_TYPE_VIDEO ,-1 );This should be done last after the
tegra_vi_graph_buildandtegra_channel_setup_ctrl_handlercalls. The video device is immediately accessible after this call, so don't call it until everything is setup (i.e. until just before the 'return 0;' below).Quoted 14 lines
Quoted 4 lines
drivers/staging/media/tegra-video/vi.c +4
-0+if (ret <0 ) { +dev_err (vi->dev, +"failed to register video device: %d\n" , ret); + goto unregister_video;drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1264
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+ } + +/* create links between the entities */ +list_for_each_entry (asd, &chan->notifier.asd_list, asd_list) { + entity =to_tegra_vi_graph_entity (asd); + ret =tegra_vi_graph_build (chan, entity); +if (ret <0 ) + goto unregister_video; + } +Hi Hans,
Currently Tegra video driver sets
v4l2_dev->mdevprior to graph parse and building links to letmedia_device_register_entity()to happen duringvideo_register_device()->video_register_media_controller()andmedia_device_unregister_entity()to happen duringv4l2_device_release()TPG also does the same of letting media entity register/unregister to happen during video device register and release callback.
So, registering video device prior to media links creation as
media_device_register_entity()will happen duringvideo_register_device()Quoted 8 lines
To register video device after creating media links, it need to change for both TPG and Non-TPG to not set
v4l2_dev->mdevand Tegra video driver should explicitly take care ofmedia_device_register_entity()andmedia_device_unregister_entity().Prior to making this change to both TPG and Non-TPG, would like to understand on possibility of using video device node prior to finishing complete driver
probe()As video device register happens during async notifier complete callback, and all the device graph build happens during video driver
probe()what exactly will be the issue of having video device node prior to creating media links?It's not the 'create links between the entities' bit that's the problem, it is what follows:
drivers/staging/media/tegra-video/vi.c +10
-0+ ret =tegra_channel_setup_ctrl_handler (chan); +if (ret <0 ) { +dev_err (vi->dev, +"failed to setup channel controls: %d\n" , ret); + goto unregister_video; + } + +vi_fmts_bitmap_init (chan); + subdev =tegra_channel_get_remote_subdev (chan, false); +v4l2_set_subdev_hostdata (subdev, chan);
Quoted 1 line
That should be done before the
video_register_devicecall.
v4l2_subdev is retrieved in tegra_channel_get_remote_subdev() through media pad entity links which are setup only during media_create_pad_link()
Currently as driver lets media_device_register_entity() to happen during video_device_register(), media_create_pad_link() is done after video_register_device.
media_create_pad_link() need to happen prior to using tegra_channel_get_remote_subdev() with current implementation.
Probably I can move tegra_channel_setup_ctrl_handler() and vi_fmts_bitmap_init() into subdev bound notifier callback to invoke them for subdev entity not MEDIA_ENT_F_VID_IF_BRIDGE.
With this by the time video_register_device happens during complete callback, ctrl handler and bitmaps both will be setup/initialized.
Quoted 3 lines
Because otherwise the
/dev/videoXdoesn't have the full set of controls, and I am also not certain which ioctls might use the subdev hostdata.
csi driver gets hostdata as it needs channel pg_mode selection value and this is used only during streaming.
Quoted 16 lines
The core problem is really that
video_register_deviceshould have been split into an init function and a register function, so it is possible to set everything up before registering the video device. Oh well...Regards,
Hans
Quoted 8 lines
I see some other drivers also doing the same order of registering video device prior to creating media links and also we are doing the same in L4T driver as well.
Thanks
Sowjanya
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Quoted 37 lines · Sowjanya Komatineni
Quoted 31 lines · Sowjanya Komatineni
Quoted 18 lines · Hans Verkuil
drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1454
Quoted 8 lines
drivers/staging/media/tegra-video/vi.c +8
-0+static void tegra_vi_graph_cleanup (struct tegra_vi *vi) +{ +struct tegra_vi_channel *chan; + +list_for_each_entry (chan, &vi->vi_chans, list) { +video_unregister_device (&chan->video); +mutex_lock (&chan->video_lock); +vb2_queue_release (&chan->queue);No need for this since this is done in
vb2_fop_release().In fact,
vb2_queue_releaseshould never be called by drivers. Just usingvb2_fop_releaseor__vb2_fop_releaseis sufficient.The confusion is due to the fact that the name suggests that
vb2_queue_releasehas to be balanced withvb2_queue_init, but that's not the case. Perhapsvb2_queue_stopor something like that might be a better name. I'll have to think about this since I see that a lot of drivers do this wrong.Quoted 6 lines
drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1460
Quoted 6 lines
drivers/staging/media/tegra-video/vi.c +6
-0+mutex_unlock (&chan->video_lock); +v4l2_async_notifier_unregister (&chan->notifier); +v4l2_async_notifier_cleanup (&chan->notifier); + } +} +
vb2_queue_release()here is called to stop streaming a head before media links are removed in case of when driver unbind happens while userspace application holds video device with active streaming in progress.Quoted 4 lines
Without
vb2_queue_release()here streaming will be active during the driver unbind and by the timevb2_queue_release()happens fromvb2_fop_release(), async notifiers gets unregistered and media links will be removed which causes channel stop stream to crash as we can't retrieve sensor subdev thru media entity pads to executes_streamon subdev.
Quoted 7 lines
I think we don't need async notifier unbind. Currently media links are removed during unbind so during notifier unregister all subdevs gets unbind and links removed.
media_device_unregisterduring video device release callback takes care of media entity unregister and removing links.So, will try by removing notifier unbind along with removing
vb2_queue_releaseduring cleanup.
I actually wonder if vb2_queue_release shouldn't be called from video_unregister_device.
I'll look into this tomorrow.
Regards,
Hans
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Quoted 42 lines · Hans Verkuil
Quoted 34 lines · Sowjanya Komatineni
Quoted 29 lines · Sowjanya Komatineni
Quoted 18 lines · Hans Verkuil
drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1454
Quoted 8 lines
drivers/staging/media/tegra-video/vi.c +8
-0+static void tegra_vi_graph_cleanup (struct tegra_vi *vi) +{ +struct tegra_vi_channel *chan; + +list_for_each_entry (chan, &vi->vi_chans, list) { +video_unregister_device (&chan->video); +mutex_lock (&chan->video_lock); +vb2_queue_release (&chan->queue);No need for this since this is done in
vb2_fop_release().In fact,
vb2_queue_releaseshould never be called by drivers. Just usingvb2_fop_releaseor__vb2_fop_releaseis sufficient.The confusion is due to the fact that the name suggests that
vb2_queue_releasehas to be balanced withvb2_queue_init, but that's not the case. Perhapsvb2_queue_stopor something like that might be a better name. I'll have to think about this since I see that a lot of drivers do this wrong.Quoted 6 lines
drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1460
Quoted 6 lines
drivers/staging/media/tegra-video/vi.c +6
-0+mutex_unlock (&chan->video_lock); +v4l2_async_notifier_unregister (&chan->notifier); +v4l2_async_notifier_cleanup (&chan->notifier); + } +} +
vb2_queue_release()here is called to stop streaming a head before media links are removed in case of when driver unbind happens while userspace application holds video device with active streaming in progress.Quoted 4 lines
Without
vb2_queue_release()here streaming will be active during the driver unbind and by the timevb2_queue_release()happens fromvb2_fop_release(), async notifiers gets unregistered and media links will be removed which causes channel stop stream to crash as we can't retrieve sensor subdev thru media entity pads to executes_streamon subdev.Quoted 7 lines
I think we don't need async notifier unbind. Currently media links are removed during unbind so during notifier unregister all subdevs gets unbind and links removed.
media_device_unregisterduring video device release callback takes care of media entity unregister and removing links.So, will try by removing notifier unbind along with removing
vb2_queue_releaseduring cleanup.
Quoted 7 lines
I actually wonder if
vb2_queue_releaseshouldn't be called fromvideo_unregister_device.I'll look into this tomorrow.
Regards,
Hans
Thanks Hans.
Tried without notifier unbind to remove media links and I still see crash due to below diff reason now.
With userspace app holding video device node with active streaming in progress when I do driver unbind, v4l2_device release callback tegra_v4l2_dev_release() happens prior to vb2_fops_release() -> vb2_queue_release().
All channels resources and channel memory is freed during v4l2_device release callback.
Letting vb2_queue_release() to happen thru vb2_fops_release() causes crash as stop streaming tries to retrieve subdev thru channel media pads and channel memory is freed by that time.
So, doing vb2_queue_release() during driver unbind -> tegra_vi_exit() -> tegra_vi_graph_cleanup(), stops subdev stream properly and then on v4l2_device release channel memory gets freed and this works which is the existing implementation in the patch.
I remember adding vb2_queue_release() during graph cleanup for TPG as well for the same reason to allow driver unbind while holding video device from user space so media pad can be accessible to stop stream before channel cleanup.
Regards,
Sowjanya
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Quoted 60 lines · Sowjanya Komatineni
Quoted 42 lines · Hans Verkuil
Quoted 34 lines · Sowjanya Komatineni
Quoted 29 lines · Sowjanya Komatineni
Quoted 18 lines · Hans Verkuil
drivers/staging/media/tegra-video/vi.c static int __maybe_unused vi_runtime_suspend(struct device *dev) · line 1454
Quoted 8 lines
drivers/staging/media/tegra-video/vi.c +8
-0+static void tegra_vi_graph_cleanup (struct tegra_vi *vi) +{ + struct tegra_vi_channel *chan; + + list_for_each_entry(chan, &vi->vi_chans, list) { + video_unregister_device(&chan->video); + mutex_lock(&chan->video_lock); + vb2_queue_release(&chan->queue);No need for this since this is done in
vb2_fop_release().In fact,
vb2_queue_releaseshould never be called by drivers. Just usingvb2_fop_releaseor__vb2_fop_releaseis sufficient.The confusion is due to the fact that the name suggests that
vb2_queue_releasehas to be balanced withvb2_queue_init, but that's not the case. Perhapsvb2_queue_stopor something like that might be a better name. I'll have to think about this since I see that a lot of drivers do this wrong.Quoted 6 lines
Review
Quoted 6 lines
+
mutex_unlock(&chan->video_lock);
+v4l2_async_notifier_unregister(&chan->notifier);
+v4l2_async_notifier_cleanup(&chan->notifier); + }(quoted diff) +2
-0+} +
vb2_queue_release()here is called to stop streaming a head before media links are removed in case of when driver unbind happens while userspace application holds video device with active streaming in progress.Quoted 4 lines
Without
vb2_queue_release()here streaming will be active during the driver unbind and by the timevb2_queue_release()happens fromvb2_fop_release(), async notifiers gets unregistered and media links will be removed which causes channel stop stream to crash as we can't retrieve sensor subdev thru media entity pads to executes_streamon subdev.Quoted 7 lines
I think we don't need async notifier unbind. Currently media links are removed during unbind so during notifier unregister all subdevs gets unbind and links removed.
media_device_unregisterduring video device release callback takes care of media entity unregister and removing links.So, will try by removing notifier unbind along with removing
vb2_queue_releaseduring cleanup.Quoted 7 lines
I actually wonder if
vb2_queue_releaseshouldn't be called fromvideo_unregister_device.I'll look into this tomorrow.
Regards,
Hans
Thanks Hans.
Tried without notifier unbind to remove media links and I still see crash due to below diff reason now.
With userspace app holding video device node with active streaming in progress when I do driver unbind,
v4l2_devicerelease callbacktegra_v4l2_dev_release()happens prior tovb2_fops_release()->vb2_queue_release().All channels resources and channel memory is freed during
v4l2_devicerelease callback.
Quoted 7 lines
Letting
vb2_queue_release()to happen thruvb2_fops_release()causes crash as stop streaming tries to retrieve subdev thru channel media pads and channel memory is freed by that time.So, doing
vb2_queue_release()during driver unbind ->tegra_vi_exit()
->tegra_vi_graph_cleanup(), stops subdev stream properly and then onv4l2_devicerelease channel memory gets freed and this works which is the existing implementation in the patch.I remember adding
vb2_queue_release()during graph cleanup for TPG as well for the same reason to allow driver unbind while holding video device from user space so media pad can be accessible to stop stream before channel cleanup.
v4l2_dev release() should definitely happen in the last after vb2_fops_release(). Will add more debugs and confirm on what I observed as something happened with timestamps on log on my side so I doubt my above observation after removing notifier unbind to remove media links.
Will check and get back..
Quoted 5 lines
Regards,
Sowjanya
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
Quoted 68 lines · Sowjanya Komatineni
Quoted 66 lines · Sowjanya Komatineni
Quoted 42 lines · Hans Verkuil
Quoted 34 lines · Sowjanya Komatineni
Quoted 29 lines · Sowjanya Komatineni
Quoted 18 lines · Hans Verkuil
Review
Quoted 8 lines
(quoted diff) +8
-0+static void tegra_vi_graph_cleanup(struct tegra_vi *vi) +{ + struct tegra_vi_channel *chan; + + list_for_each_entry(chan, &vi->vi_chans, list) { + video_unregister_device(&chan->video); + mutex_lock(&chan->video_lock); + vb2_queue_release(&chan->queue);No need for this since this is done in
vb2_fop_release().In fact,
vb2_queue_releaseshould never be called by drivers. Just usingvb2_fop_releaseor__vb2_fop_releaseis sufficient.The confusion is due to the fact that the name suggests that
vb2_queue_releasehas to be balanced withvb2_queue_init, but that's not the case. Perhapsvb2_queue_stopor something like that might be a better name. I'll have to think about this since I see that a lot of drivers do this wrong.Quoted 6 lines
Review
Quoted 6 lines
+
mutex_unlock(&chan->video_lock);
+v4l2_async_notifier_unregister(&chan->notifier);
+v4l2_async_notifier_cleanup(&chan->notifier); + }(quoted diff) +2
-0+} +
vb2_queue_release()here is called to stop streaming a head before media links are removed in case of when driver unbind happens while userspace application holds video device with active streaming in progress.Quoted 4 lines
Without
vb2_queue_release()here streaming will be active during the driver unbind and by the timevb2_queue_release()happens fromvb2_fop_release(), async notifiers gets unregistered and media links will be removed which causes channel stop stream to crash as we can't retrieve sensor subdev thru media entity pads to executes_streamon subdev.Quoted 7 lines
I think we don't need async notifier unbind. Currently media links are removed during unbind so during notifier unregister all subdevs gets unbind and links removed.
media_device_unregisterduring video device release callback takes care of media entity unregister and removing links.So, will try by removing notifier unbind along with removing
vb2_queue_releaseduring cleanup.Quoted 7 lines
I actually wonder if
vb2_queue_releaseshouldn't be called fromvideo_unregister_device.I'll look into this tomorrow.
Regards,
Hans
Thanks Hans.
Tried without notifier unbind to remove media links and I still see crash due to below diff reason now.
With userspace app holding video device node with active streaming in progress when I do driver unbind,
v4l2_devicerelease callbacktegra_v4l2_dev_release()happens prior tovb2_fops_release()->vb2_queue_release().All channels resources and channel memory is freed during
v4l2_devicerelease callback.Letting
vb2_queue_release()to happen thruvb2_fops_release()causes crash as stop streaming tries to retrieve subdev thru channel media pads and channel memory is freed by that time.So, doing
vb2_queue_release()during driver unbind ->tegra_vi_exit()
->tegra_vi_graph_cleanup(), stops subdev stream properly and then onv4l2_devicerelease channel memory gets freed and this works which is the existing implementation in the patch.
Quoted 6 lines
Quoted 1 line
I remember adding
vb2_queue_release()during graph cleanup for TPG as well for the same reason to allow driver unbind while holding video device from user space so media pad can be accessible to stop stream before channel cleanup.
v4l2_devrelease()should definitely happen in the last aftervb2_fops_release(). Will add more debugs and confirm on what I observed as something happened with timestamps on log on my side so I doubt my above observation after removing notifier unbind to remove media links.Will check and get back..
Hi Hans,
Please ignore above observation on channel cleanup during v4l2_dev release and vb2_fops_release. I misunderstood from timestamps.
Looking into vdev->dev release callback v4l2_device_release(), it unregisters media entity and links gets removed.
So, by the time vb2_queue_release() happen thru vb2_fops_release(), links are removed so subdev can't be retrieve thru media entity pads unless video driver maintains subdev pointers to use them instead of retrieving from media entity pads.
To fix this, instead of maintaining subdev pointers in Tegra video driver channel structure, probably we can leave vb2_queue_release() call to happen during driver unbind graph cleanup which does stream stop where Tegra channel stop stream retrieves subdev thru media pad entities when media links are still present.
Thanks
Sowjanya
Quoted 5 lines
Quoted 5 lines
Regards,
Sowjanya
Re: [RFC PATCH v2 11/18] media: tegra-video: Add support for external sensor capture
In reply to Sowjanya KomatineniQuoted 27 lines · Sowjanya Komatineni
This patch adds support to capture from the external sensor based on device graph in the device tree.
Driver walks through the device graph to create media links between the entities and registers and unregisters video devices when the corresponding sub-devices are bound and unbound.
Channel formats are enumerated based on available formats from the sensor and the corresponding matched formats from the Tegra supported video formats list.
Each Tegra CSI instance can be configured as 4-lane or 2-lane based on supported lane configuration from the sensor through the device tree.
Currently this driver supports V4L2 video node centric only.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/Kconfig | 1 + drivers/staging/media/tegra-video/csi.c | 128 +++++- drivers/staging/media/tegra-video/csi.h | 1 + drivers/staging/media/tegra-video/tegra210.c | 2 +- drivers/staging/media/tegra-video/vi.c | 623 +++++++++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- 6 files changed, 726 insertions(+), 52 deletions(-)
<snip>
drivers/staging/media/tegra-video/csi.c static const struct v4l2_subdev_ops tegra_csi_ops = { · line 338
Quoted 4 lines
drivers/staging/media/tegra-video/csi.c +4
-0+static int tegra_csi_channels_alloc (struct tegra_csi *csi) +{ +struct device_node *node = csi->dev->of_node; +struct v4l2_fwnode_endpoint v4l2_ep = { .bus_type =0 };
A bus_type value of 0 is deprecated, this should be set to a valid bus_type (probably V4L2_MBUS_CSI2_DPHY).
Regards,
Hans
Sowjanya Komatineni
maintainerRFC PATCH v2 12/18 media: tegra-video: Add support for selection ioctl ops
In reply to Sowjanya KomatineniThis patch adds selection v4l2 ioctl operations to allow configuring a selection rectangle in the sensor through the Tegra video device node.
Some sensor drivers supporting crop uses try_crop rectangle from v4l2_subdev_pad_config during try format for computing binning.
So with selection ops support, this patch also updates try format to use try crop rectangle either from subdev frame size enumeration or from subdev crop boundary.
--- drivers/staging/media/tegra-video/vi.c | 106 +++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+)
drivers/staging/media/tegra-video/vi.c +106 -0
@@ -427,6 +427,13 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan,struct v4l2_subdev *subdev;struct v4l2_subdev_format fmt;struct v4l2_subdev_pad_config *pad_cfg; +struct v4l2_subdev_frame_size_enum fse = { + .which =V4L2_SUBDEV_FORMAT_TRY , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target =V4L2_SEL_TGT_CROP_BOUNDS , + };int ret; subdev =tegra_channel_get_remote_subdev (chan, true);
@@ -449,6 +456,24 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan, fmt.which =V4L2_SUBDEV_FORMAT_TRY ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); + +/* +* Attempt to obtain the format size from subdev. +* If not available, try to get crop boundary from subdev. +*/ + fse.code = fmtinfo->code; + ret =v4l2_subdev_call (subdev, pad, enum_frame_size, pad_cfg, &fse); +if (ret) { + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (ret) +return -EINVAL ; + pad_cfg->try_crop.width = sdsel.r.width; + pad_cfg->try_crop.height = sdsel.r.height; + }else { + pad_cfg->try_crop.width = fse.max_width; + pad_cfg->try_crop.height = fse.max_height; + } + ret =v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt);if (ret <0 )return ret;
@@ -540,6 +565,85 @@ static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan)return 0 ; } +static int tegra_channel_g_selection (struct file *file,void *priv, +struct v4l2_selection *sel) +{ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +struct v4l2_subdev_format fmt = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + }; +int ret; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; +/* +* Try the get selection operation and fallback to get format if not +* implemented. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (!ret) + sel->r = sdsel.r; +if (ret != -ENOIOCTLCMD ) +return ret; + + ret =v4l2_subdev_call (subdev, pad, get_fmt,NULL , &fmt); +if (ret <0 ) +return ret; + + sel->r.left =0 ; + sel->r.top =0 ; + sel->r.width = fmt.format.width; + sel->r.height = fmt.format.height; + +return 0 ; +} + +static int tegra_channel_s_selection (struct file *file,void *fh, +struct v4l2_selection *sel) +{ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +int ret; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + .flags = sel->flags, + .r = sel->r, + }; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; + +if (vb2_is_busy (&chan->queue)) +return -EBUSY ; + + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, set_selection,NULL , &sdsel); +if (!ret) { + sel->r = sdsel.r; +/* +* Subdev active format resolution may have changed during +* set selection operation. So, update channel format to +* the sub-device active format. +*/ +return tegra_channel_set_subdev_active_fmt (chan); + } + +return ret; +} +static int tegra_channel_enum_input (struct file *file,void *fh,struct v4l2_input *inp) {
@@ -597,6 +701,8 @@ static const struct v4l2_ioctl_ops tegra_channel_ioctl_ops = { .vidioc_streamoff = vb2_ioctl_streamoff, .vidioc_subscribe_event = v4l2_ctrl_subscribe_event, .vidioc_unsubscribe_event = v4l2_event_unsubscribe, + .vidioc_g_selection = tegra_channel_g_selection, + .vidioc_s_selection = tegra_channel_s_selection, };/*
Signature · 1 line
2.7.4
Re: [RFC PATCH v2 12/18] media: tegra-video: Add support for selection ioctl ops
Quoted 108 lines · Sowjanya Komatineni
This patch adds selection v4l2 ioctl operations to allow configuring a selection rectangle in the sensor through the Tegra video device node.
Some sensor drivers supporting crop uses
try_croprectangle fromv4l2_subdev_pad_configduring try format for computing binning.So with selection ops support, this patch also updates try format to use try crop rectangle either from subdev frame size enumeration or from subdev crop boundary.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/vi.c | 106 +++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+)drivers/staging/media/tegra-video/vi.c +70
-0@@ -427,6 +427,13 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan,struct v4l2_subdev *subdev;struct v4l2_subdev_format fmt;struct v4l2_subdev_pad_config *pad_cfg; +struct v4l2_subdev_frame_size_enum fse = { + .which =V4L2_SUBDEV_FORMAT_TRY , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target =V4L2_SEL_TGT_CROP_BOUNDS , + };int ret; subdev =tegra_channel_get_remote_subdev (chan, true);@@ -449,6 +456,24 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan, fmt.which =V4L2_SUBDEV_FORMAT_TRY ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); + +/* +* Attempt to obtain the format size from subdev. +* If not available, try to get crop boundary from subdev. +*/ + fse.code = fmtinfo->code; + ret =v4l2_subdev_call (subdev, pad, enum_frame_size, pad_cfg, &fse); +if (ret) { + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (ret) +return -EINVAL ; + pad_cfg->try_crop.width = sdsel.r.width; + pad_cfg->try_crop.height = sdsel.r.height; + }else { + pad_cfg->try_crop.width = fse.max_width; + pad_cfg->try_crop.height = fse.max_height; + } + ret =v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt);if (ret <0 )return ret;@@ -540,6 +565,85 @@ static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan)return 0 ; } +static int tegra_channel_g_selection (struct file *file,void *priv, +struct v4l2_selection *sel) +{ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +struct v4l2_subdev_format fmt = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + }; +int ret; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; +/* +* Try the get selection operation and fallback to get format if not +* implemented. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (!ret) + sel->r = sdsel.r; +if (ret != -ENOIOCTLCMD ) +return ret; + + ret =v4l2_subdev_call (subdev, pad, get_fmt,NULL , &fmt); +if (ret <0 ) +return ret; + + sel->r.left =0 ; + sel->r.top =0 ; + sel->r.width = fmt.format.width; + sel->r.height = fmt.format.height; + +return 0 ; +} + +static int tegra_channel_s_selection (struct file *file,void *fh, +struct v4l2_selection *sel) +{
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 622
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +int ret; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + .flags = sel->flags, + .r = sel->r, + }; +
This function doesn't check if the subdev actually supports set_selection. The imx219 is one such driver: it supports get_selection, but not set_selection.
So this code should add these lines to fix the v4l2-compliance fail:
subdev = tegra_channel_get_remote_subdev(chan, true);
if (!v4l2_subdev_has_op(subdev, pad, set_selection))
return -ENOTTY;drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 632
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; + +if (vb2_is_busy (&chan->queue)) +return -EBUSY ; + + subdev =tegra_channel_get_remote_subdev (chan, true);
And this line can be dropped.
Regards,
Hans
Quoted 27 lines
drivers/staging/media/tegra-video/vi.c +16
-0+ ret =v4l2_subdev_call (subdev, pad, set_selection,NULL , &sdsel); +if (!ret) { + sel->r = sdsel.r; +/* +* Subdev active format resolution may have changed during +* set selection operation. So, update channel format to +* the sub-device active format. +*/ +return tegra_channel_set_subdev_active_fmt (chan); + } + +return ret; +} +static int tegra_channel_enum_input (struct file *file,void *fh,struct v4l2_input *inp) {@@ -597,6 +701,8 @@ static const struct v4l2_ioctl_ops tegra_channel_ioctl_ops = { .vidioc_streamoff = vb2_ioctl_streamoff, .vidioc_subscribe_event = v4l2_ctrl_subscribe_event, .vidioc_unsubscribe_event = v4l2_event_unsubscribe, + .vidioc_g_selection = tegra_channel_g_selection, + .vidioc_s_selection = tegra_channel_s_selection, };/*
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 12/18] media: tegra-video: Add support for selection ioctl ops
Quoted 122 lines · Hans Verkuil
Quoted 108 lines · Sowjanya Komatineni
This patch adds selection v4l2 ioctl operations to allow configuring a selection rectangle in the sensor through the Tegra video device node.
Some sensor drivers supporting crop uses
try_croprectangle fromv4l2_subdev_pad_configduring try format for computing binning.So with selection ops support, this patch also updates try format to use try crop rectangle either from subdev frame size enumeration or from subdev crop boundary.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/vi.c | 106 +++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+)drivers/staging/media/tegra-video/vi.c +70
-0@@ -427,6 +427,13 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan,struct v4l2_subdev *subdev;struct v4l2_subdev_format fmt;struct v4l2_subdev_pad_config *pad_cfg; +struct v4l2_subdev_frame_size_enum fse = { + .which =V4L2_SUBDEV_FORMAT_TRY , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target =V4L2_SEL_TGT_CROP_BOUNDS , + };int ret; subdev =tegra_channel_get_remote_subdev (chan, true);@@ -449,6 +456,24 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan, fmt.which =V4L2_SUBDEV_FORMAT_TRY ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); + +/* +* Attempt to obtain the format size from subdev. +* If not available, try to get crop boundary from subdev. +*/ + fse.code = fmtinfo->code; + ret =v4l2_subdev_call (subdev, pad, enum_frame_size, pad_cfg, &fse); +if (ret) { + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (ret) +return -EINVAL ; + pad_cfg->try_crop.width = sdsel.r.width; + pad_cfg->try_crop.height = sdsel.r.height; + }else { + pad_cfg->try_crop.width = fse.max_width; + pad_cfg->try_crop.height = fse.max_height; + } + ret =v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt);if (ret <0 )return ret;@@ -540,6 +565,85 @@ static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan)return 0 ; } +static int tegra_channel_g_selection (struct file *file,void *priv, +struct v4l2_selection *sel) +{ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +struct v4l2_subdev_format fmt = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + }; +int ret; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; +/* +* Try the get selection operation and fallback to get format if not +* implemented. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (!ret) + sel->r = sdsel.r; +if (ret != -ENOIOCTLCMD ) +return ret; + + ret =v4l2_subdev_call (subdev, pad, get_fmt,NULL , &fmt); +if (ret <0 ) +return ret; + + sel->r.left =0 ; + sel->r.top =0 ; + sel->r.width = fmt.format.width; + sel->r.height = fmt.format.height; + +return 0 ; +} + +static int tegra_channel_s_selection (struct file *file,void *fh, +struct v4l2_selection *sel) +{drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 622
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +int ret; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + .flags = sel->flags, + .r = sel->r, + }; +This function doesn't check if the subdev actually supports
set_selection. The imx219 is one such driver: it supportsget_selection, but notset_selection.
Quoted 7 lines
So this code should add these lines to fix the v4l2-compliance fail:
subdev = tegra_channel_get_remote_subdev(chan, true); if (!v4l2_subdev_has_op(subdev, pad, set_selection)) return -ENOTTY;
v4l2_subdev_call() does that check and returns -ENOIOCTLCMD when specified subdev ops does not exist.
Quoted 43 lines
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 632
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; + +if (vb2_is_busy (&chan->queue)) +return -EBUSY ; + + subdev =tegra_channel_get_remote_subdev (chan, true);And this line can be dropped.
Regards,
Hans
Quoted 27 lines
drivers/staging/media/tegra-video/vi.c +16
-0+ ret =v4l2_subdev_call (subdev, pad, set_selection,NULL , &sdsel); +if (!ret) { + sel->r = sdsel.r; +/* +* Subdev active format resolution may have changed during +* set selection operation. So, update channel format to +* the sub-device active format. +*/ +return tegra_channel_set_subdev_active_fmt (chan); + } + +return ret; +} +static int tegra_channel_enum_input (struct file *file,void *fh,struct v4l2_input *inp) {@@ -597,6 +701,8 @@ static const struct v4l2_ioctl_ops tegra_channel_ioctl_ops = { .vidioc_streamoff = vb2_ioctl_streamoff, .vidioc_subscribe_event = v4l2_ctrl_subscribe_event, .vidioc_unsubscribe_event = v4l2_event_unsubscribe, + .vidioc_g_selection = tegra_channel_g_selection, + .vidioc_s_selection = tegra_channel_s_selection, };/*
Re: [RFC PATCH v2 12/18] media: tegra-video: Add support for selection ioctl ops
Quoted 126 lines · Sowjanya Komatineni
Quoted 124 lines · Hans Verkuil
Quoted 108 lines · Sowjanya Komatineni
This patch adds selection v4l2 ioctl operations to allow configuring a selection rectangle in the sensor through the Tegra video device node.
Some sensor drivers supporting crop uses
try_croprectangle fromv4l2_subdev_pad_configduring try format for computing binning.So with selection ops support, this patch also updates try format to use try crop rectangle either from subdev frame size enumeration or from subdev crop boundary.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/vi.c | 106 +++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+)drivers/staging/media/tegra-video/vi.c +70
-0@@ -427,6 +427,13 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan,struct v4l2_subdev *subdev;struct v4l2_subdev_format fmt;struct v4l2_subdev_pad_config *pad_cfg; +struct v4l2_subdev_frame_size_enum fse = { + .which =V4L2_SUBDEV_FORMAT_TRY , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target =V4L2_SEL_TGT_CROP_BOUNDS , + };int ret; subdev =tegra_channel_get_remote_subdev (chan, true);@@ -449,6 +456,24 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan, fmt.which =V4L2_SUBDEV_FORMAT_TRY ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); + +/* +* Attempt to obtain the format size from subdev. +* If not available, try to get crop boundary from subdev. +*/ + fse.code = fmtinfo->code; + ret =v4l2_subdev_call (subdev, pad, enum_frame_size, pad_cfg, &fse); +if (ret) { + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (ret) +return -EINVAL ; + pad_cfg->try_crop.width = sdsel.r.width; + pad_cfg->try_crop.height = sdsel.r.height; + }else { + pad_cfg->try_crop.width = fse.max_width; + pad_cfg->try_crop.height = fse.max_height; + } + ret =v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt);if (ret <0 )return ret;@@ -540,6 +565,85 @@ static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan)return 0 ; } +static int tegra_channel_g_selection (struct file *file,void *priv, +struct v4l2_selection *sel) +{ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +struct v4l2_subdev_format fmt = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + }; +int ret; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; +/* +* Try the get selection operation and fallback to get format if not +* implemented. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (!ret) + sel->r = sdsel.r; +if (ret != -ENOIOCTLCMD ) +return ret; + + ret =v4l2_subdev_call (subdev, pad, get_fmt,NULL , &fmt); +if (ret <0 ) +return ret; + + sel->r.left =0 ; + sel->r.top =0 ; + sel->r.width = fmt.format.width; + sel->r.height = fmt.format.height; + +return 0 ; +} + +static int tegra_channel_s_selection (struct file *file,void *fh, +struct v4l2_selection *sel) +{drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 622
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +int ret; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + .flags = sel->flags, + .r = sel->r, + }; +This function doesn't check if the subdev actually supports
set_selection. The imx219 is one such driver: it supportsget_selection, but notset_selection.So this code should add these lines to fix the v4l2-compliance fail:
Quoted 7 lines
Quoted 5 lines
subdev = tegra_channel_get_remote_subdev(chan, true); if (!v4l2_subdev_has_op(subdev, pad, set_selection)) return -ENOTTY;
v4l2_subdev_call()does that check and returns-ENOIOCTLCMDwhen specified subdev ops does not exist.
But that test happens too late. In the v4l2-compliance test it fails in the sel->type test below, so it returns EINVAL instead of ENOTTY.
Quoted 2 lines
Quoted 2 lines
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 624
Quoted 2 lines
drivers/staging/media/tegra-video/vi.c +2
-0+if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ;
I think this test should come before the v4l2_subdev_has_op test since there is probably no subdev if the TPG is enabled. So:
if (IS_ENABLED(CONFIG_VIDEO_TEGRA_TPG))
return -ENOTTY;
subdev = tegra_channel_get_remote_subdev(chan, true);
if (!v4l2_subdev_has_op(subdev, pad, set_selection))
return -ENOTTY;Regards,
Hans
Quoted 41 lines
Quoted 41 lines
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 632
Quoted 8 lines
drivers/staging/media/tegra-video/vi.c +8
-0+ +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; + +if (vb2_is_busy (&chan->queue)) +return -EBUSY ; + + subdev =tegra_channel_get_remote_subdev (chan, true);And this line can be dropped.
Regards,
Hans
Quoted 27 lines
drivers/staging/media/tegra-video/vi.c +16
-0+ ret =v4l2_subdev_call (subdev, pad, set_selection,NULL , &sdsel); +if (!ret) { + sel->r = sdsel.r; +/* +* Subdev active format resolution may have changed during +* set selection operation. So, update channel format to +* the sub-device active format. +*/ +return tegra_channel_set_subdev_active_fmt (chan); + } + +return ret; +} +static int tegra_channel_enum_input (struct file *file,void *fh,struct v4l2_input *inp) {@@ -597,6 +701,8 @@ static const struct v4l2_ioctl_ops tegra_channel_ioctl_ops = { .vidioc_streamoff = vb2_ioctl_streamoff, .vidioc_subscribe_event = v4l2_ctrl_subscribe_event, .vidioc_unsubscribe_event = v4l2_event_unsubscribe, + .vidioc_g_selection = tegra_channel_g_selection, + .vidioc_s_selection = tegra_channel_s_selection, };/*
Sowjanya Komatineni
maintainerRe: [RFC PATCH v2 12/18] media: tegra-video: Add support for selection ioctl ops
Quoted 149 lines · Hans Verkuil
Quoted 125 lines · Sowjanya Komatineni
Quoted 124 lines · Hans Verkuil
Quoted 108 lines · Sowjanya Komatineni
This patch adds selection v4l2 ioctl operations to allow configuring a selection rectangle in the sensor through the Tegra video device node.
Some sensor drivers supporting crop uses
try_croprectangle fromv4l2_subdev_pad_configduring try format for computing binning.So with selection ops support, this patch also updates try format to use try crop rectangle either from subdev frame size enumeration or from subdev crop boundary.
Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/staging/media/tegra-video/vi.c | 106 +++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+)drivers/staging/media/tegra-video/vi.c +70
-0@@ -427,6 +427,13 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan,struct v4l2_subdev *subdev;struct v4l2_subdev_format fmt;struct v4l2_subdev_pad_config *pad_cfg; +struct v4l2_subdev_frame_size_enum fse = { + .which =V4L2_SUBDEV_FORMAT_TRY , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target =V4L2_SEL_TGT_CROP_BOUNDS , + };int ret; subdev =tegra_channel_get_remote_subdev (chan, true);@@ -449,6 +456,24 @@ static int __tegra_channel_try_format(struct tegra_vi_channel *chan, fmt.which =V4L2_SUBDEV_FORMAT_TRY ; fmt.pad =0 ;v4l2_fill_mbus_format (&fmt.format, pix, fmtinfo->code); + +/* +* Attempt to obtain the format size from subdev. +* If not available, try to get crop boundary from subdev. +*/ + fse.code = fmtinfo->code; + ret =v4l2_subdev_call (subdev, pad, enum_frame_size, pad_cfg, &fse); +if (ret) { + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (ret) +return -EINVAL ; + pad_cfg->try_crop.width = sdsel.r.width; + pad_cfg->try_crop.height = sdsel.r.height; + }else { + pad_cfg->try_crop.width = fse.max_width; + pad_cfg->try_crop.height = fse.max_height; + } + ret =v4l2_subdev_call (subdev, pad, set_fmt, pad_cfg, &fmt);if (ret <0 )return ret;@@ -540,6 +565,85 @@ static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan)return 0 ; } +static int tegra_channel_g_selection (struct file *file,void *priv, +struct v4l2_selection *sel) +{ +struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +struct v4l2_subdev_format fmt = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + }; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + }; +int ret; + +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ; + +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; +/* +* Try the get selection operation and fallback to get format if not +* implemented. +*/ + subdev =tegra_channel_get_remote_subdev (chan, true); + ret =v4l2_subdev_call (subdev, pad, get_selection,NULL , &sdsel); +if (!ret) + sel->r = sdsel.r; +if (ret != -ENOIOCTLCMD ) +return ret; + + ret =v4l2_subdev_call (subdev, pad, get_fmt,NULL , &fmt); +if (ret <0 ) +return ret; + + sel->r.left =0 ; + sel->r.top =0 ; + sel->r.width = fmt.format.width; + sel->r.height = fmt.format.height; + +return 0 ; +} + +static int tegra_channel_s_selection (struct file *file,void *fh, +struct v4l2_selection *sel) +{drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 622
Quoted 10 lines
drivers/staging/media/tegra-video/vi.c +10
-0+struct tegra_vi_channel *chan =video_drvdata (file); +struct v4l2_subdev *subdev; +int ret; +struct v4l2_subdev_selection sdsel = { + .which =V4L2_SUBDEV_FORMAT_ACTIVE , + .target = sel->target, + .flags = sel->flags, + .r = sel->r, + }; +This function doesn't check if the subdev actually supports
set_selection. The imx219 is one such driver: it supportsget_selection, but notset_selection.So this code should add these lines to fix the v4l2-compliance fail:
Quoted 7 lines
Quoted 5 lines
subdev = tegra_channel_get_remote_subdev(chan, true); if (!v4l2_subdev_has_op(subdev, pad, set_selection)) return -ENOTTY;
v4l2_subdev_call()does that check and returns-ENOIOCTLCMDwhen specified subdev ops does not exist.But that test happens too late. In the v4l2-compliance test it fails in the
sel->typetest below, so it returns EINVAL instead of ENOTTY.Quoted 2 lines
Quoted 2 lines
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 624
Quoted 2 lines
drivers/staging/media/tegra-video/vi.c +2
-0+if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return -ENOTTY ;I think this test should come before the
v4l2_subdev_has_optest since there is probably no subdev if the TPG is enabled. So:if (IS_ENABLED(CONFIG_VIDEO_TEGRA_TPG)) return -ENOTTY; subdev = tegra_channel_get_remote_subdev(chan, true); if (!v4l2_subdev_has_op(subdev, pad, set_selection)) return -ENOTTY;
Quoted 3 lines
Regards,
Hans
OK Will update in v3. Thanks Hans
Quoted 41 lines
Quoted 41 lines
Quoted 41 lines
drivers/staging/media/tegra-video/vi.c static int tegra_channel_set_subdev_active_fmt(struct tegra_vi_channel *chan) · line 632
Quoted 8 lines
drivers/staging/media/tegra-video/vi.c +8
-0+ +if (sel->type !=V4L2_BUF_TYPE_VIDEO_CAPTURE ) +return -EINVAL ; + +if (vb2_is_busy (&chan->queue)) +return -EBUSY ; + + subdev =tegra_channel_get_remote_subdev (chan, true);And this line can be dropped.
Regards,
Hans
Quoted 27 lines
drivers/staging/media/tegra-video/vi.c +16
-0+ ret =v4l2_subdev_call (subdev, pad, set_selection,NULL , &sdsel); +if (!ret) { + sel->r = sdsel.r; +/* +* Subdev active format resolution may have changed during +* set selection operation. So, update channel format to +* the sub-device active format. +*/ +return tegra_channel_set_subdev_active_fmt (chan); + } + +return ret; +} +static int tegra_channel_enum_input (struct file *file,void *fh,struct v4l2_input *inp) {@@ -597,6 +701,8 @@ static const struct v4l2_ioctl_ops tegra_channel_ioctl_ops = { .vidioc_streamoff = vb2_ioctl_streamoff, .vidioc_subscribe_event = v4l2_ctrl_subscribe_event, .vidioc_unsubscribe_event = v4l2_event_unsubscribe, + .vidioc_g_selection = tegra_channel_g_selection, + .vidioc_s_selection = tegra_channel_s_selection, };/*
Sowjanya Komatineni
maintainerRFC PATCH v2 13/18 gpu: host1x: mipi: Update tegra_mipi_request() to be node based
In reply to Sowjanya KomatineniTegra CSI driver need a separate MIPI device for each channel as calibration of corresponding MIPI pads for each channel should happen independently.
So, this patch updates tegra_mipi_request() API to add a device_node pointer argument to allow creating mipi device for specific device node rather than a device.
--- drivers/gpu/drm/tegra/dsi.c | 2 +- drivers/gpu/host1x/mipi.c | 7 +++++-- include/linux/host1x.h | 3 ++- 3 files changed, 8 insertions(+), 4 deletions(-)
drivers/gpu/drm/tegra/dsi.c +1 -1
@@ -1618,7 +1618,7 @@ static int tegra_dsi_probe(struct platform_device *pdev)if (IS_ERR (dsi->regs))return PTR_ERR (dsi->regs); - dsi->mipi =tegra_mipi_request (&pdev->dev); + dsi->mipi =tegra_mipi_request (&pdev->dev,NULL );if (IS_ERR (dsi->mipi))return PTR_ERR (dsi->mipi);
drivers/gpu/host1x/mipi.c +5 -2
@@ -206,13 +206,16 @@ static int tegra_mipi_power_down(struct tegra_mipi *mipi)return 0 ; } -struct tegra_mipi_device *tegra_mipi_request (struct device *device) +struct tegra_mipi_device *tegra_mipi_request (struct device *device, +struct device_node *np) { -struct device_node *np = device->of_node;struct tegra_mipi_device *dev;struct of_phandle_args args;int err; +if (!np) + np = device->of_node; + err =of_parse_phandle_with_args (np,"nvidia,mipi-calibrate" ,"#nvidia,mipi-calibrate-cells" ,0 , &args);
include/linux/host1x.h +2 -1
@@ -325,7 +325,8 @@ int host1x_client_resume(struct host1x_client *client);struct tegra_mipi_device ; -struct tegra_mipi_device *tegra_mipi_request (struct device *device); +struct tegra_mipi_device *tegra_mipi_request (struct device *device, +struct device_node *np);void tegra_mipi_free (struct tegra_mipi_device *device);int tegra_mipi_enable (struct tegra_mipi_device *device);int tegra_mipi_disable (struct tegra_mipi_device *device);
Signature · 1 line
2.7.4
Dmitry Osipenko
reviewerRe: [RFC PATCH v2 13/18] gpu: host1x: mipi: Update tegra_mipi_request() to be node based
17.06.2020 04:41, Sowjanya Komatineni пишет:
Quoted 37 lines
Tegra CSI driver need a separate MIPI device for each channel as calibration of corresponding MIPI pads for each channel should happen independently.
So, this patch updates
tegra_mipi_request()API to add adevice_nodepointer argument to allow creating mipi device for specific device node rather than a device.Signed-off-by Sowjanya Komatineni <[email protected]>--- drivers/gpu/drm/tegra/dsi.c | 2 +- drivers/gpu/host1x/mipi.c | 7 +++++-- include/linux/host1x.h | 3 ++- 3 files changed, 8 insertions(+), 4 deletions(-)drivers/gpu/drm/tegra/dsi.c +1
-1@@ -1618,7 +1618,7 @@ static int tegra_dsi_probe(struct platform_device *pdev)if (IS_ERR (dsi->regs))return PTR_ERR (dsi->regs); - dsi->mipi =tegra_mipi_request (&pdev->dev); + dsi->mipi =tegra_mipi_request (&pdev->dev,NULL );if (IS_ERR (dsi->mipi))return PTR_ERR (dsi->mipi);drivers/gpu/host1x/mipi.c +0
-1@@ -206,13 +206,16 @@ static int tegra_mipi_power_down(struct tegra_mipi *mipi)return 0 ; } -struct tegra_mipi_device *tegra_mipi_request (struct device *device)
drivers/gpu/host1x/mipi.c static int tegra_mipi_power_down(struct tegra_mipi *mipi) · line 217
Quoted 10 lines
drivers/gpu/host1x/mipi.c +4
-1+struct tegra_mipi_device *tegra_mipi_request (struct device *device, +struct device_node *np) { -struct device_node *np = device->of_node;struct tegra_mipi_device *dev;struct of_phandle_args args;int err; +if (!np) + np = device->of_node;
Will be nicer if DSI panel could pass the device's node directly, instead of this.
Sowjanya Komatineni
maintainerRFC PATCH v2 14/18 gpu: host1x: mipi: Split tegra_mipi_calibrate and tegra_mipi_wait
In reply to Sowjanya KomatineniSW can trigger MIPI pads calibration any time after power on but calibration results will be latched and applied to the pads by MIPI CAL unit only when the link is in LP-11 state and then status register will be updated.
For CSI, trigger of pads calibration happen during CSI stream enable where CSI receiver is kept ready prior to sensor or CSI transmitter stream start.
So, pads may not be in LP-11 at this time and waiting for the calibration to be done immediate after calibration start will result in timeout.
This patch splits tegra_mipi_calibrate() and tegra_mipi_wait() so triggering for calibration and waiting for it to complete can happen at different stages.
--- drivers/gpu/drm/tegra/dsi.c | 7 ++++++- drivers/gpu/host1x/mipi.c | 23 +++++++++++++++++------ include/linux/host1x.h | 1 + 3 files changed, 24 insertions(+), 7 deletions(-)
drivers/gpu/drm/tegra/dsi.c +6 -1
@@ -670,6 +670,7 @@ static int tegra_dsi_pad_enable(struct tegra_dsi *dsi)static int tegra_dsi_pad_calibrate (struct tegra_dsi *dsi) {u32 value; +int ret;/* * XXX Is this still needed? The module reset is deasserted right
@@ -693,7 +694,11 @@ static int tegra_dsi_pad_calibrate(struct tegra_dsi *dsi)DSI_PAD_PREEMP_PD (0x03 ) |DSI_PAD_PREEMP_PU (0x3 );tegra_dsi_writel (dsi, value,DSI_PAD_CONTROL_3 ); -return tegra_mipi_calibrate (dsi->mipi); + ret =tegra_mipi_calibrate (dsi->mipi); +if (ret <0 ) +return ret; + +return tegra_mipi_wait (dsi->mipi); } static void tegra_dsi_set_timeout(struct tegra_dsi *dsi, unsigned long bclk,
drivers/gpu/host1x/mipi.c +17 -6
@@ -296,22 +296,35 @@ int tegra_mipi_disable(struct tegra_mipi_device *dev) }EXPORT_SYMBOL (tegra_mipi_disable); -static int tegra_mipi_wait (struct tegra_mipi *mipi) +int tegra_mipi_wait (struct tegra_mipi_device *device) { +struct tegra_mipi *mipi = device->mipi;unsigned long timeout = jiffies +msecs_to_jiffies (250 );u32 value; +int err; + + err =clk_enable (device->mipi->clk); +if (err <0 ) +return err; + +mutex_lock (&device->mipi->lock);while (time_before (jiffies, timeout)) { value =tegra_mipi_readl (mipi,MIPI_CAL_STATUS );if ((value &MIPI_CAL_STATUS_ACTIVE ) ==0 && (value &MIPI_CAL_STATUS_DONE ) !=0 ) -return 0 ; + goto done;usleep_range (10 ,50 ); } -return -ETIMEDOUT ; + err = -ETIMEDOUT ; +done: +mutex_unlock (&device->mipi->lock); +clk_disable (device->mipi->clk); +return err; } +EXPORT_SYMBOL (tegra_mipi_wait);int tegra_mipi_calibrate (struct tegra_mipi_device *device) {
@@ -377,12 +390,10 @@ int tegra_mipi_calibrate(struct tegra_mipi_device *device) value |=MIPI_CAL_CTRL_START ;tegra_mipi_writel (device->mipi, value,MIPI_CAL_CTRL ); - err =tegra_mipi_wait (device->mipi); -mutex_unlock (&device->mipi->lock);clk_disable (device->mipi->clk); -return err; +return 0 ; }EXPORT_SYMBOL (tegra_mipi_calibrate);
include/linux/host1x.h +1 -0
@@ -331,5 +331,6 @@ void tegra_mipi_free(struct tegra_mipi_device *device);int tegra_mipi_enable (struct tegra_mipi_device *device);int tegra_mipi_disable (struct tegra_mipi_device *device);int tegra_mipi_calibrate (struct tegra_mipi_device *device); +int tegra_mipi_wait (struct tegra_mipi_device *device);#endif
Signature · 1 line
2.7.4
Dmitry Osipenko
reviewerRe: [RFC PATCH v2 14/18] gpu: host1x: mipi: Split tegra_mipi_calibrate and tegra_mipi_wait
17.06.2020 04:41, Sowjanya Komatineni пишет:
...
drivers/gpu/host1x/mipi.c int tegra_mipi_disable(struct tegra_mipi_device *dev) · line 310
Quoted 13 lines
drivers/gpu/host1x/mipi.c +9
-1-static int tegra_mipi_wait (struct tegra_mipi *mipi) +int tegra_mipi_wait (struct tegra_mipi_device *device) { +struct tegra_mipi *mipi = device->mipi;unsigned long timeout = jiffies +msecs_to_jiffies (250 );u32 value; +int err; + + err =clk_enable (device->mipi->clk); +if (err <0 ) +return err; + +mutex_lock (&device->mipi->lock);
The timeout variable should be assigned *after* taking the lock.
It will be better if you could use the read_poll_timeout() or readl_relaxed_poll_timeout() here.
Quoted 18 lines
drivers/gpu/host1x/mipi.c +7
-2while (time_before (jiffies, timeout)) { value =tegra_mipi_readl (mipi,MIPI_CAL_STATUS );if ((value &MIPI_CAL_STATUS_ACTIVE ) ==0 && (value &MIPI_CAL_STATUS_DONE ) !=0 ) -return 0 ; + goto done;usleep_range (10 ,50 ); } -return -ETIMEDOUT ; + err = -ETIMEDOUT ; +done: +mutex_unlock (&device->mipi->lock); +clk_disable (device->mipi->clk); +return err; } +EXPORT_SYMBOL (tegra_mipi_wait);
Sowjanya Komatineni
maintainerRFC PATCH v2 15/18 media: tegra-video: Add CSI MIPI pads calibration
In reply to Sowjanya KomatineniCSI MIPI pads need to be enabled and calibrated for capturing from the external sensor or transmitter.
MIPI CAL unit calibrates MIPI pads pull-up, pull-down and termination impedances. Calibration is done by co-work of MIPI BIAS pad and MIPI CAL control unit.
Triggering calibration start can happen any time after MIPI pads are enabled but calibration results will be latched and applied to MIPI pads by MIPI CAL unit only when the link is in LP11 state and then calibration status register gets updated.
This patch enables CSI MIPI pads and calibrates them during streaming.
Tegra CSI receiver is able to catch the very first clock transition. So, CSI receiver is always enabled prior to sensor streaming and trigger of calibration start is done during CSI subdev streaming and status of calibration is verified after sensor stream on.
--- drivers/staging/media/tegra-video/csi.c | 44 +++++++++++++++++++++++++++++++-- drivers/staging/media/tegra-video/csi.h | 2 ++ drivers/staging/media/tegra-video/vi.c | 18 ++++++++++++++ 3 files changed, 62 insertions(+), 2 deletions(-)
drivers/staging/media/tegra-video/csi.c +42 -2
@@ -252,15 +252,42 @@ static int tegra_csi_s_stream(struct v4l2_subdev *subdev, int enable)return ret; } +if (csi_chan->mipi) { + ret =tegra_mipi_enable (csi_chan->mipi); +if (ret <0 ) { +dev_err (csi->dev, +"failed to enable MIPI pads: %d\n" , + ret); + goto rpm_put; + } + +/* +* CSI MIPI pads PULLUP, PULLDN and TERM impedances +* need to be calibrated after power on. +* So, trigger the calibration start here and results +* will be latched and applied to the pads when link is +* in LP11 state during start of sensor streaming. +*/ +tegra_mipi_calibrate (csi_chan->mipi); + } + ret = csi->ops->csi_start_streaming (csi_chan);if (ret <0 ) - goto rpm_put; + goto disable_mipi;return 0 ; } csi->ops->csi_stop_streaming (csi_chan); +disable_mipi: +if (csi_chan->mipi) { + ret =tegra_mipi_disable (csi_chan->mipi); +if (ret <0 ) +dev_err (csi->dev, +"failed to disable MIPI pads: %d\n" , ret); + } + rpm_put:pm_runtime_put (csi->dev);return ret;
@@ -294,6 +321,7 @@ static int tegra_csi_channel_alloc(struct tegra_csi *csi, unsigned int num_pads) {struct tegra_csi_channel *chan; +int ret =0 ; chan =kzalloc (sizeof (*chan),GFP_KERNEL );if (!chan)
@@ -312,7 +340,16 @@ static int tegra_csi_channel_alloc(struct tegra_csi *csi, chan->pads[0 ].flags =MEDIA_PAD_FL_SOURCE ; } -return 0 ; +if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG )) +return 0 ; + + chan->mipi =tegra_mipi_request (csi->dev, node); +if (IS_ERR (chan->mipi)) { + ret =PTR_ERR (chan->mipi); +dev_err (csi->dev,"failed to get mipi device: %d\n" , ret); + } + +return ret; }static int tegra_csi_tpg_channels_alloc (struct tegra_csi *csi)
@@ -473,6 +510,9 @@ static void tegra_csi_channels_cleanup(struct tegra_csi *csi)struct tegra_csi_channel *chan, *tmp;list_for_each_entry_safe (chan, tmp, &csi->csi_chans, list) { +if (chan->mipi) +tegra_mipi_free (chan->mipi); + subdev = &chan->subdev;if (subdev->dev) {if (!IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG ))
drivers/staging/media/tegra-video/csi.h +2 -0
@@ -50,6 +50,7 @@ struct tegra_csi;* @framerate: active framerate for TPG * @h_blank: horizontal blanking for TPG active format * @v_blank: vertical blanking for TPG active format +* @mipi: mipi device for corresponding csi channel pads */ struct tegra_csi_channel {struct list_head list;
@@ -65,6 +66,7 @@ struct tegra_csi_channel {unsigned int framerate;unsigned int h_blank;unsigned int v_blank; +struct tegra_mipi_device *mipi; };/**
drivers/staging/media/tegra-video/vi.c +18 -0
@@ -187,6 +187,7 @@ tegra_channel_get_remote_subdev(struct tegra_vi_channel *chan, bool sensor)int tegra_channel_set_stream (struct tegra_vi_channel *chan,bool on) {struct v4l2_subdev *subdev; +struct tegra_csi_channel *csi_chan;int ret;/* stream CSI */
@@ -198,11 +199,28 @@ int tegra_channel_set_stream(struct tegra_vi_channel *chan, bool on)if (IS_ENABLED (CONFIG_VIDEO_TEGRA_TPG ))return 0 ; +if (on) + csi_chan =v4l2_get_subdevdata (subdev); + subdev =tegra_channel_get_remote_subdev (chan, on); ret =v4l2_subdev_call (subdev, video, s_stream, on);if (on && ret <0 && ret != -ENOIOCTLCMD )return ret; +/* +* CSI subdev stream on triggers start of MIPI pads calibration. +* Calibration results are latched and applied to the pads when +* link is in LP11 state which will hapen during sensor streaming. +* So, wait for calibration to complete here. +*/ +if (on && csi_chan->mipi) { + ret =tegra_mipi_wait (csi_chan->mipi); +if (ret <0 ) +dev_err (csi_chan->csi->dev, +"MIPI calibration failed: %d\n" , ret); +return ret; + } +return 0 ; }
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 16/18 media: tegra-video: Compute settle times based on the clock rate
In reply to Sowjanya KomatineniSettle time determines the number of cil clock cyles to wait after LP00 when moving from LP to HS.
This patch computes T-CLK-SETTLE and T-HS-SETTLE times based on cil clock rate and pixel rate from the sensor and programs them during streaming.
T-CLK-SETTLE time is the interval during which receiver will ignore any HS transitions on clock lane starting from the beginning of T-CLK-PREPARE.
T-HS-SETTLE time is the interval during which recevier will ignore any HS transitions on data lane starting from the beginning of T-HS-PREPARE.
--- drivers/staging/media/tegra-video/csi.c | 55 ++++++++++++++++++++++++++++ drivers/staging/media/tegra-video/csi.h | 5 +++ drivers/staging/media/tegra-video/tegra210.c | 17 ++++++++- 3 files changed, 75 insertions(+), 2 deletions(-)
drivers/staging/media/tegra-video/csi.c +55 -0
@@ -19,6 +19,8 @@#include "csi.h" #include "video.h" +#define MHZ 1000000 +static inline struct tegra_csi *host1x_client_to_csi (struct host1x_client *client) {
@@ -235,6 +237,59 @@ static int tegra_csi_g_frame_interval(struct v4l2_subdev *subdev,return 0 ; } +static unsigned int csi_get_pixel_rate (struct tegra_csi_channel *csi_chan) +{ +struct tegra_vi_channel *chan; +struct v4l2_subdev *src_subdev; +struct v4l2_ctrl *ctrl; + + chan =v4l2_get_subdev_hostdata (&csi_chan->subdev); + src_subdev =tegra_channel_get_remote_subdev (chan, true); + ctrl =v4l2_ctrl_find (src_subdev->ctrl_handler,V4L2_CID_PIXEL_RATE ); +if (ctrl) +return v4l2_ctrl_g_ctrl_int64 (ctrl); + +return 0 ; +} + +void tegra_csi_calc_settle_time (struct tegra_csi_channel *csi_chan, +u8 *clk_settle_time, +u8 *ths_settle_time) +{ +struct tegra_csi *csi = csi_chan->csi; +unsigned int cil_clk_mhz; +unsigned int pix_clk_mhz; +int clk_idx = (csi_chan->csi_port_num >>1 ) +1 ; + + cil_clk_mhz =clk_get_rate (csi->clks[clk_idx].clk) /MHZ ; + pix_clk_mhz =csi_get_pixel_rate (csi_chan) /MHZ ; + +/* +* CLK Settle time is the interval during which HS receiver should +* ignore any clock lane HS transitions, starting from the beginning +* of T-CLK-PREPARE. +* Per DPHY specification, T-CLK-SETTLE should be between 95ns ~ 300ns +* +* 95ns < (clk-settle-programmed + 7) * lp clk period < 300ns +* midpoint = 197.5 ns +*/ + *clk_settle_time = ((95 +300 ) * cil_clk_mhz -14000 ) /2000 ; + +/* +* THS Settle time is the interval during which HS receiver should +* ignore any data lane HS transitions, starting from the beginning +* of THS-PREPARE. +* +* Per DPHY specification, T-HS-SETTLE should be between 85ns + 6UI +* and 145ns+10UI. +* 85ns + 6UI < (Ths-settle-prog + 5) * lp_clk_period < 145ns + 10UI +* midpoint = 115ns + 8UI +*/ +if (pix_clk_mhz) + *ths_settle_time = (115 * cil_clk_mhz +8000 * cil_clk_mhz + / (2 * pix_clk_mhz) -5000 ) /1000 ; +} +static int tegra_csi_s_stream (struct v4l2_subdev *subdev,int enable) {struct tegra_vi_channel *chan =v4l2_get_subdev_hostdata (subdev);
drivers/staging/media/tegra-video/csi.h +5 -0
@@ -51,6 +51,7 @@ struct tegra_csi;* @h_blank: horizontal blanking for TPG active format * @v_blank: vertical blanking for TPG active format * @mipi: mipi device for corresponding csi channel pads +* @pixel_rate: active pixel rate from the sensor on this channel */ struct tegra_csi_channel {struct list_head list;
@@ -67,6 +68,7 @@ struct tegra_csi_channel {unsigned int h_blank;unsigned int v_blank;struct tegra_mipi_device *mipi; +unsigned int pixel_rate; };/**
@@ -147,4 +149,7 @@ extern const struct tegra_csi_soc tegra210_csi_soc;#endif void tegra_csi_error_recover (struct v4l2_subdev *subdev); +void tegra_csi_calc_settle_time (struct tegra_csi_channel *csi_chan, +u8 *clk_settle_time, +u8 *ths_settle_time);#endif
drivers/staging/media/tegra-video/tegra210.c +15 -2
@@ -7,6 +7,7 @@* This source file contains Tegra210 supported video formats, * VI and CSI SoC specific data, operations and registers accessors. */ +#include <linux/bitfield.h> #include <linux/clk.h> #include <linux/clk/tegra.h> #include <linux/delay.h>
@@ -98,6 +99,8 @@#define BRICK_CLOCK_B_4X (0x2 << 16)#define TEGRA_CSI_CIL_PAD_CONFIG1 0x004#define TEGRA_CSI_CIL_PHY_CONTROL 0x008 +#define CLK_SETTLE_MASK GENMASK(13, 8) +#define THS_SETTLE_MASK GENMASK(5, 0)#define TEGRA_CSI_CIL_INTERRUPT_MASK 0x00c#define TEGRA_CSI_CIL_STATUS 0x010#define TEGRA_CSI_CILX_STATUS 0x014
@@ -770,8 +773,14 @@ static int tegra210_csi_start_streaming(struct tegra_csi_channel *csi_chan) {struct tegra_csi *csi = csi_chan->csi;unsigned int portno = csi_chan->csi_port_num; +u8 clk_settle_time =0 ; +u8 ths_settle_time =10 ;u32 val; +if (!csi_chan->pg_mode) +tegra_csi_calc_settle_time (csi_chan, &clk_settle_time, + &ths_settle_time); +csi_write (csi, portno,TEGRA_CSI_CLKEN_OVERRIDE ,0 );/* clean up status */
@@ -782,7 +791,9 @@ static int tegra210_csi_start_streaming(struct tegra_csi_channel *csi_chan)/* CIL PHY registers setup */ cil_write (csi, portno,TEGRA_CSI_CIL_PAD_CONFIG0 ,0x0 ); -cil_write (csi, portno,TEGRA_CSI_CIL_PHY_CONTROL ,0xa ); +cil_write (csi, portno,TEGRA_CSI_CIL_PHY_CONTROL , +FIELD_PREP (CLK_SETTLE_MASK , clk_settle_time) | +FIELD_PREP (THS_SETTLE_MASK , ths_settle_time));/* * The CSI unit provides for connection of up to six cameras in
@@ -801,7 +812,9 @@ static int tegra210_csi_start_streaming(struct tegra_csi_channel *csi_chan) BRICK_CLOCK_A_4X);cil_write (csi, portno +1 ,TEGRA_CSI_CIL_PAD_CONFIG0 ,0x0 );cil_write (csi, portno +1 ,TEGRA_CSI_CIL_INTERRUPT_MASK ,0x0 ); -cil_write (csi, portno +1 ,TEGRA_CSI_CIL_PHY_CONTROL ,0xa ); +cil_write (csi, portno +1 ,TEGRA_CSI_CIL_PHY_CONTROL , +FIELD_PREP (CLK_SETTLE_MASK , clk_settle_time) | +FIELD_PREP (THS_SETTLE_MASK , ths_settle_time));csi_write (csi, portno,TEGRA_CSI_PHY_CIL_COMMAND ,CSI_A_PHY_CIL_ENABLE |CSI_B_PHY_CIL_ENABLE ); }else {
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 17/18 arm64: tegra: jetson-tx1: Add camera supplies
In reply to Sowjanya KomatineniJetson TX1 development board has a camera expansion connector which has 2V8, 1V8 and 1V2 supplies to power up the camera sensor on the supported camera modules.
Camera module designed as per Jetson TX1 camera expansion connector may use these supplies for camera sensor avdd 2V8, digital core 1V8, and digital interface 1V2 voltages.
These supplies are from fixed regulators on TX1 carrier board with enable control signals from I2C GPIO expanders.
This patch adds these camera supplies to Jetson TX1 device tree to allow using these when a camera module is used.
--- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++++++++++++++++++++++++++ 1 file changed, 41 insertions(+)
arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi +41 -0
@@ -1323,6 +1323,14 @@ #gpio-cells = <2>; gpio-controller; }; + + exp2: gpio@77 { + compatible = "ti,tca9539"; + reg = <0x77>; + + #gpio-cells = <2>; + gpio-controller; + }; }; /* HDMI DDC */
@@ -1667,6 +1675,39 @@ enable-active-high; vin-supply = <&vdd_5v0_sys>; }; + + vdd_cam_1v2: regulator@12 { + compatible = "regulator-fixed"; + reg = <12>; + regulator-name = "vdd-cam-1v2"; + regulator-min-microvolt = <1200000>; + regulator-max-microvolt = <1200000>; + gpio = <&exp2 10 GPIO_ACTIVE_HIGH>; + enable-active-high; + vin-supply = <&vdd_3v3_sys>; + }; + + vdd_cam_2v8: regulator@13 { + compatible = "regulator-fixed"; + reg = <13>; + regulator-name = "vdd-cam-2v8"; + regulator-min-microvolt = <2800000>; + regulator-max-microvolt = <2800000>; + gpio = <&exp1 13 GPIO_ACTIVE_HIGH>; + enable-active-high; + vin-supply = <&vdd_3v3_sys>; + }; + + vdd_cam_1v8: regulator@14 { + compatible = "regulator-fixed"; + reg = <14>; + regulator-name = "vdd-cam-1v8"; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <1800000>; + gpio = <&exp2 9 GPIO_ACTIVE_HIGH>; + enable-active-high; + vin-supply = <&vdd_3v3_sys>; + }; }; gpio-keys {
Signature · 1 line
2.7.4
Sowjanya Komatineni
maintainerRFC PATCH v2 18/18 arm64: tegra: Enable Tegra VI CSI support for Jetson Nano
In reply to Sowjanya KomatineniThis patch enables VI and CSI in device tree for Jetson Nano.
--- arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 ++++++++++ 1 file changed, 10 insertions(+)
arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts +10 -0
@@ -64,6 +64,16 @@ status = "okay"; }; + vi@54080000 { + status = "okay"; + + avdd-dsi-csi-supply = <&vdd_sys_1v2>; + + csi@838 { + status = "okay"; + }; + }; + sor@54540000 { status = "okay";
Signature · 1 line
2.7.4
Quoted 10 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
Which tree did you base this on? The media_tree master? Or the mainline kernel?
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11
And then everything hangs and I need to reset.
I'm testing with the media_tree master with your patches on top.
Regards,
Hans
Quoted 73 lines
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and
power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++ arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770 +++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +- 16 files changed, 1251 insertions(+), 100 deletions(-)
Sowjanya Komatineni
maintainerQuoted 4 lines · Hans Verkuil
Quoted 3 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Quoted 8 lines
Quoted 7 lines
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?
These patches are with linux-next base at the time I sent them out which are on 20200616
Quoted 9 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11
Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Does you setup also uses CSI-A as x2 for IMX219?
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson TX1 + IMX274.
I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Quoted 73 lines
Quoted 73 lines
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and
power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++ arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770 +++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +- 16 files changed, 1251 insertions(+), 100 deletions(-)
Quoted 35 lines · Sowjanya Komatineni
Quoted 4 lines · Hans Verkuil
Quoted 3 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Quoted 8 lines
Quoted 7 lines
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?These patches are with linux-next base at the time I sent them out which are on 20200616
Quoted 9 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Quoted 8 lines
Does you setup also uses CSI-A as x2 for IMX219?
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson TX1 + IMX274.
I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Please use the media_tree master, that's what I use as well.
I did some more testing and there is something weird going on.
I have a Leopard Imaging camera expansion board (LI-JTX1-MIPI-ADPT) with three camera connectors. See here for the datasheet:
https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
The first connector (with an IMX274) causes this error:
$ v4l2-ctl -d1 --stream-mmap [ 599.265885] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.473883] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.681904] video4linux video1: frame start syncpt timeout: -11 [ 599.681909] video4linux video1: MW_ACK_DONE syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 599.897884] video4linux video1: MW_ACK_DONE syncpt timeout: -11
Similar to the test above where I had an IMX219 connected. Except it didn't hang with the IMX274 (I'm beginning to suspect a locking issue in the imx219 driver that is causing the hang, I'll look at that tomorrow).
If I connect the IMX219 to the middle camera connector, then it works fine. I think I tested this with the IMX274 as well, but I'm not 100% certain, also something to double check tomorrow.
If I connect the IMX219 or IMX274 to the third camera connector, then I get this:
$ v4l2-ctl -d0 --stream-mmap [ 820.513866] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.525354] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.536780] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.548222] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.559639] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <[ 820.646931] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.658355] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.669797] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.681216] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.692601] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
<<<<<<<<<<<<<<< 14.50 fps
<<<<<<<<<<<<<<< 14.75 fps
<<<<<<<<<<<<<<< 14.73 fps
<<<<<<<<<<<<<<< 14.80 fps
<<<<<<<<<<<<<[ 825.517854] tegra_mc_irq: 133437 callbacks suppressed
[ 825.517874] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.534395] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.545833] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.557280] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.579346] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.590764] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.602188] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.613649] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.625075] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.645983] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
< 14.64 fps
<<<<<<<<<<<<<<<< 14.87 fps
<<<<<<<<<<<<<<< 14.89 fps
Something is producing EMEM address decode errors. But it is streaming.
If I enable the TPG then everything is fine.
So I have currently three different behaviors for three camera connectors.
Do you have a datasheet for your Jetson TX1 camera board? It could be useful to compare the two.
Regards,
Hans
Quoted 74 lines
Quoted 74 lines
Quoted 74 lines
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and
power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++ arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770 +++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +- 16 files changed, 1251 insertions(+), 100 deletions(-)
Sowjanya Komatineni
maintainerQuoted 64 lines · Hans Verkuil
Quoted 32 lines · Sowjanya Komatineni
Quoted 4 lines · Hans Verkuil
Quoted 3 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Quoted 8 lines
Quoted 7 lines
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?These patches are with linux-next base at the time I sent them out which are on 20200616
Quoted 8 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Quoted 8 lines
Does you setup also uses CSI-A as x2 for IMX219?
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson TX1 + IMX274.
I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Please use the
media_treemaster, that's what I use as well.I did some more testing and there is something weird going on.
I have a Leopard Imaging camera expansion board (LI-JTX1-MIPI-ADPT) with three camera connectors. See here for the datasheet:
https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
The first connector (with an IMX274) causes this error:
$ v4l2-ctl -d1 --stream-mmap [ 599.265885] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.473883] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.681904] video4linux video1: frame start syncpt timeout: -11 [ 599.681909] video4linux video1: MW_ACK_DONE syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 599.897884] video4linux video1: MW_ACK_DONE syncpt timeout: -11Similar to the test above where I had an IMX219 connected. Except it didn't hang with the IMX274 (I'm beginning to suspect a locking issue in the imx219 driver that is causing the hang, I'll look at that tomorrow).
Quoted 5 lines
If I connect the IMX219 to the middle camera connector, then it works fine. I think I tested this with the IMX274 as well, but I'm not 100% certain, also something to double check tomorrow.
If I connect the IMX219 or IMX274 to the third camera connector, then I get this:
Would like to know CSI port mapping to connectors as mipi calibrate pads cells need to be updated in device tree based on CSI port in use.
Will see if I can find that from DS link you sent above.
Quoted 31 lines
$ v4l2-ctl -d0 --stream-mmap [ 820.513866] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.525354] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.536780] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.548222] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.559639] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <[ 820.646931] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.658355] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.669797] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.681216] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.692601] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)<<<<<<<<<<<<<<< 14.50 fps
<<<<<<<<<<<<<<< 14.75 fps
<<<<<<<<<<<<<<< 14.73 fps
<<<<<<<<<<<<<<< 14.80 fps
<<<<<<<<<<<<<[ 825.517854]tegra_mc_irq: 133437 callbacks suppressed[ 825.517874] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.534395] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.545833] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.557280] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.579346] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.590764] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.602188] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.613649] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.625075] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.645983] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
Quoted 5 lines
< 14.64 fps
<<<<<<<<<<<<<<<< 14.87 fps
<<<<<<<<<<<<<<< 14.89 fpsSomething is producing EMEM address decode errors. But it is streaming.
above memory controller errors may be due to access faults and not sure why these show up on your setup. I never have these with my testing.
Also I am using CMA alloc of 256MB and not sure if low CMA alloc size is causing this. Can you try with CMA alloc size of 256MB?
Quoted 7 lines
If I enable the TPG then everything is fine.
So I have currently three different behaviors for three camera connectors.
Do you have a datasheet for your Jetson TX1 camera board? It could be useful to compare the two.
Yeah we have and will send it offline.
Also based on connector mapping to corresponding CSI port, mipi-calibrate pad cell value also need to be changed.
Below is for CSI-A
nvidia,mipi-calibrate = <&mipi 0x001>
Quoted 76 lines
Regards,
Hans
Quoted 72 lines
Quoted 72 lines
Quoted 72 lines
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and
power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++ arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770 +++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +- 16 files changed, 1251 insertions(+), 100 deletions(-)
Sowjanya Komatineni
maintainerQuoted 146 lines · Sowjanya Komatineni
Quoted 65 lines · Hans Verkuil
Quoted 32 lines · Sowjanya Komatineni
Quoted 4 lines · Hans Verkuil
Quoted 3 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Quoted 8 lines
Quoted 7 lines
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?These patches are with linux-next base at the time I sent them out which are on 20200616
Quoted 8 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Quoted 8 lines
Does you setup also uses CSI-A as x2 for IMX219?
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson TX1 + IMX274.
I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Please use the
media_treemaster, that's what I use as well.I did some more testing and there is something weird going on.
I have a Leopard Imaging camera expansion board (LI-JTX1-MIPI-ADPT) with three camera connectors. See here for the datasheet:
https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
The first connector (with an IMX274) causes this error:
$ v4l2-ctl -d1 --stream-mmap [ 599.265885] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.473883] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.681904] video4linux video1: frame start syncpt timeout: -11 [ 599.681909] video4linux video1: MW_ACK_DONE syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 599.897884] video4linux video1: MW_ACK_DONE syncpt timeout: -11Similar to the test above where I had an IMX219 connected. Except it didn't hang with the IMX274 (I'm beginning to suspect a locking issue in the imx219 driver that is causing the hang, I'll look at that tomorrow).
Quoted 5 lines
If I connect the IMX219 to the middle camera connector, then it works fine. I think I tested this with the IMX274 as well, but I'm not 100% certain, also something to double check tomorrow.
If I connect the IMX219 or IMX274 to the third camera connector, then I get this:
Would like to know CSI port mapping to connectors as mipi calibrate pads cells need to be updated in device tree based on CSI port in use.
Will see if I can find that from DS link you sent above.
Quoted 55 lines
$ v4l2-ctl -d0 --stream-mmap [ 820.513866] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.525354] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.536780] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.548222] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.559639] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <[ 820.646931] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.658355] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.669797] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.681216] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.692601] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <<<<<<<<<<<<<<< 14.50 fps
<<<<<<<<<<<<<<< 14.75 fps
<<<<<<<<<<<<<<< 14.73 fps
<<<<<<<<<<<<<<< 14.80 fps
<<<<<<<<<<<<<[ 825.517854]tegra_mc_irq: 133437 callbacks suppressed [ 825.517874] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.534395] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.545833] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.557280] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.579346] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.590764] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.602188] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.613649] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.625075] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.645983] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) < 14.64 fps
<<<<<<<<<<<<<<<< 14.87 fps
<<<<<<<<<<<<<<< 14.89 fpsQuoted 1 line
Something is producing EMEM address decode errors. But it is streaming.
above memory controller errors may be due to access faults and not sure why these show up on your setup. I never have these with my testing.
Also I am using CMA alloc of 256MB and not sure if low CMA alloc size is causing this. Can you try with CMA alloc size of 256MB?
Quoted 7 lines
If I enable the TPG then everything is fine.
So I have currently three different behaviors for three camera connectors.
Do you have a datasheet for your Jetson TX1 camera board? It could be useful to compare the two.
Quoted 10 lines
Yeah we have and will send it offline.
Also based on connector mapping to corresponding CSI port, mipi-calibrate pad cell value also need to be changed.
Below is for CSI-A
nvidia,mipi-calibrate = <&mipi
0x001>Quoted 3 lines
Regards,
Hans
Connector-1 is CSI-AB where you had timeouts.
Connector-2 is CSI-CD and this works for you.
Connector-3 is CSI-EF and this works for streaming from above but there's memory access fault errors (EMEM address decode errors)
These EMEM decode errors are not related to connector but its just they showed up during connector-3 testing I believe. Can you also keep CMA size to 256MB and try?
Not sure if CSI-AB issue with FS and MW_ACK sp timeouts are due to some HW/setup issue. Streaming should work on CSI-AB ports as well just like CSI-CD/EF with proper device tree change for port index and mipi calibrate cells for corresponding ports.
On my setup that I tested IMX274 is on CSI-AB.
Will update my side test results with today's linux-next
Quoted 78 lines
Quoted 78 lines
Quoted 78 lines
Quoted 78 lines
Quoted 78 lines
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++-
.../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt| 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts| 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770
+++++++++++++++++++--
drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +-16 files changed, 1251 insertions(+), 100 deletions(-)
Sowjanya Komatineni
maintainerQuoted 164 lines · Sowjanya Komatineni
Quoted 146 lines · Sowjanya Komatineni
Quoted 65 lines · Hans Verkuil
Quoted 32 lines · Sowjanya Komatineni
Quoted 4 lines · Hans Verkuil
Quoted 3 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Quoted 8 lines
Quoted 7 lines
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?These patches are with linux-next base at the time I sent them out which are on 20200616
Quoted 8 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Quoted 8 lines
Does you setup also uses CSI-A as x2 for IMX219?
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson TX1 + IMX274.
I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Please use the
media_treemaster, that's what I use as well.I did some more testing and there is something weird going on.
I have a Leopard Imaging camera expansion board (LI-JTX1-MIPI-ADPT) with three camera connectors. See here for the datasheet:
https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
The first connector (with an IMX274) causes this error:
$ v4l2-ctl -d1 --stream-mmap [ 599.265885] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.473883] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.681904] video4linux video1: frame start syncpt timeout: -11 [ 599.681909] video4linux video1: MW_ACK_DONE syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 599.897884] video4linux video1: MW_ACK_DONE syncpt timeout: -11Similar to the test above where I had an IMX219 connected. Except it didn't hang with the IMX274 (I'm beginning to suspect a locking issue in the imx219 driver that is causing the hang, I'll look at that tomorrow).
Quoted 5 lines
If I connect the IMX219 to the middle camera connector, then it works fine. I think I tested this with the IMX274 as well, but I'm not 100% certain, also something to double check tomorrow.
If I connect the IMX219 or IMX274 to the third camera connector, then I get this:
Would like to know CSI port mapping to connectors as mipi calibrate pads cells need to be updated in device tree based on CSI port in use.
Will see if I can find that from DS link you sent above.
Quoted 55 lines
$ v4l2-ctl -d0 --stream-mmap [ 820.513866] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.525354] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.536780] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.548222] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.559639] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <[ 820.646931] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.658355] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.669797] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.681216] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.692601] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <<<<<<<<<<<<<<< 14.50 fps
<<<<<<<<<<<<<<< 14.75 fps
<<<<<<<<<<<<<<< 14.73 fps
<<<<<<<<<<<<<<< 14.80 fps
<<<<<<<<<<<<<[ 825.517854]tegra_mc_irq: 133437 callbacks suppressed [ 825.517874] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.534395] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.545833] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.557280] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.579346] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.590764] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.602188] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.613649] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.625075] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.645983] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) < 14.64 fps
<<<<<<<<<<<<<<<< 14.87 fps
<<<<<<<<<<<<<<< 14.89 fpsQuoted 1 line
Something is producing EMEM address decode errors. But it is streaming.
above memory controller errors may be due to access faults and not sure why these show up on your setup. I never have these with my testing.
Also I am using CMA alloc of 256MB and not sure if low CMA alloc size is causing this. Can you try with CMA alloc size of 256MB?
Quoted 7 lines
If I enable the TPG then everything is fine.
So I have currently three different behaviors for three camera connectors.
Do you have a datasheet for your Jetson TX1 camera board? It could be useful to compare the two.
Quoted 10 lines
Yeah we have and will send it offline.
Also based on connector mapping to corresponding CSI port, mipi-calibrate pad cell value also need to be changed.
Below is for CSI-A
nvidia,mipi-calibrate = <&mipi
0x001>Quoted 3 lines
Regards,
Hans
Connector-1 is CSI-AB where you had timeouts.
Connector-2 is CSI-CD and this works for you.
Connector-3 is CSI-EF and this works for streaming from above but there's memory access fault errors (EMEM address decode errors)
Quoted 7 lines
These EMEM decode errors are not related to connector but its just they showed up during connector-3 testing I believe. Can you also keep CMA size to 256MB and try?
Not sure if CSI-AB issue with FS and
MW_ACKsp timeouts are due to some HW/setup issue. Streaming should work on CSI-AB ports as well just like CSI-CD/EF with proper device tree change for port index and mipi calibrate cells for corresponding ports.On my setup that I tested IMX274 is on CSI-AB.
Will update my side test results with today's linux-next
Hans,
We have this module as well. Will try to get this today for testing and will update just to make sure of this combo as well on my side.
https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
Thanks
Sowjanya
Quoted 80 lines
Quoted 80 lines
Quoted 80 lines
Quoted 80 lines
Quoted 80 lines
Quoted 80 lines
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++-
.../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt| 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts| 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770
+++++++++++++++++++--
drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +-16 files changed, 1251 insertions(+), 100 deletions(-)
Quoted 197 lines · Sowjanya Komatineni
Quoted 195 lines · Sowjanya Komatineni
Quoted 166 lines · Sowjanya Komatineni
Quoted 76 lines · Hans Verkuil
Quoted 40 lines · Sowjanya Komatineni
Quoted 9 lines · Hans Verkuil
Quoted 8 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to
Tegra video driver.Jetson TX1 has camera expansion connector and supports custom camera module
designed as per TX1 design specification.Quoted 7 lines
Quoted 5 lines
This series also enables camera capture support for Jetson Nano which has
Raspberry PI camera header.This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?These patches are with linux-next base at the time I sent them out which
are on 20200616Quoted 8 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Does you setup also uses CSI-A as x2 for IMX219?
Quoted 8 lines
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson
TX1 + IMX274.I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Please use the
media_treemaster, that's what I use as well.I did some more testing and there is something weird going on.
I have a Leopard Imaging camera expansion board (LI-JTX1-MIPI-ADPT) with
three camera connectors. See here for the datasheet:https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
The first connector (with an IMX274) causes this error:
$ v4l2-ctl -d1 --stream-mmap [ 599.265885] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.473883] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.681904] video4linux video1: frame start syncpt timeout: -11 [ 599.681909] video4linux video1: MW_ACK_DONE syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 599.897884] video4linux video1: MW_ACK_DONE syncpt timeout: -11Similar to the test above where I had an IMX219 connected. Except it didn't
hang with the IMX274 (I'm beginning to suspect a locking issue in the imx219
driver that is causing the hang, I'll look at that tomorrow).Quoted 8 lines
If I connect the IMX219 to the middle camera connector, then it works fine.
I think I tested this with the IMX274 as well, but I'm not 100% certain, also
something to double check tomorrow.If I connect the IMX219 or IMX274 to the third camera connector, then I get this:
Would like to know CSI port mapping to connectors as mipi calibrate pads cells need to be updated in device tree based on CSI port in use.
Will see if I can find that from DS link you sent above.
Quoted 55 lines
$ v4l2-ctl -d0 --stream-mmap [ 820.513866] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.525354] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.536780] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.548222] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.559639] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <[ 820.646931] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.658355] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.669797] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.681216] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.692601] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <<<<<<<<<<<<<<< 14.50 fps
<<<<<<<<<<<<<<< 14.75 fps
<<<<<<<<<<<<<<< 14.73 fps
<<<<<<<<<<<<<<< 14.80 fps
<<<<<<<<<<<<<[ 825.517854]tegra_mc_irq: 133437 callbacks suppressed [ 825.517874] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.534395] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.545833] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.557280] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.579346] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.590764] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.602188] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.613649] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.625075] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.645983] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) < 14.64 fps
<<<<<<<<<<<<<<<< 14.87 fps
<<<<<<<<<<<<<<< 14.89 fpsQuoted 1 line
Something is producing EMEM address decode errors. But it is streaming.
above memory controller errors may be due to access faults and not sure why these show up on your setup. I never have these with my testing.
Also I am using CMA alloc of 256MB and not sure if low CMA alloc size is causing this. Can you try with CMA alloc size of 256MB?
Quoted 9 lines
If I enable the TPG then everything is fine.
So I have currently three different behaviors for three camera connectors.
Do you have a datasheet for your Jetson TX1 camera board? It could be useful
to compare the two.Quoted 11 lines
Yeah we have and will send it offline.
Also based on connector mapping to corresponding CSI port, mipi-calibrate pad cell value also need to be changed.
Below is for CSI-A
nvidia,mipi-calibrate = <&mipi
0x001>Quoted 3 lines
Regards,
Hans
Connector-1 is CSI-AB where you had timeouts.
Connector-2 is CSI-CD and this works for you.
Connector-3 is CSI-EF and this works for streaming from above but there's memory access fault errors (EMEM address decode errors)
These EMEM decode errors are not related to connector but its just they showed up during connector-3 testing I believe. Can you also keep CMA size to 256MB and try?
Not sure if CSI-AB issue with FS and
MW_ACKsp timeouts are due to some HW/setup issue. Streaming should work on CSI-AB ports as well just like CSI-CD/EF with proper device tree change for port index and mipi calibrate cells for corresponding ports.
Quoted 8 lines
Quoted 3 lines
On my setup that I tested IMX274 is on CSI-AB.
Will update my side test results with today's linux-next
Hans,
We have this module as well. Will try to get this today for testing and will update just to make sure of this combo as well on my side.
Sowjanya,
A quick update: I had to update my u-boot and I ended up reinstalling everything.
And now the problems I described just disappeared. Very strange.
I have yet to verify if the issue with the third camera connector is also solved, I'll do that tomorrow.
But for now you don't have to take any action.
Regards,
Hans
Sowjanya Komatineni
maintainerQuoted 203 lines · Hans Verkuil
Quoted 189 lines · Sowjanya Komatineni
Quoted 188 lines · Sowjanya Komatineni
Quoted 160 lines · Sowjanya Komatineni
Quoted 76 lines · Hans Verkuil
Quoted 40 lines · Sowjanya Komatineni
Quoted 9 lines · Hans Verkuil
Quoted 8 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to
Tegra video driver.Jetson TX1 has camera expansion connector and supports custom camera module
designed as per TX1 design specification.Quoted 7 lines
Quoted 5 lines
This series also enables camera capture support for Jetson Nano which has
Raspberry PI camera header.This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?These patches are with linux-next base at the time I sent them out which
are on 20200616Quoted 8 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Does you setup also uses CSI-A as x2 for IMX219?
Quoted 8 lines
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson
TX1 + IMX274.I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Please use the
media_treemaster, that's what I use as well.I did some more testing and there is something weird going on.
I have a Leopard Imaging camera expansion board (LI-JTX1-MIPI-ADPT) with
three camera connectors. See here for the datasheet:https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
The first connector (with an IMX274) causes this error:
$ v4l2-ctl -d1 --stream-mmap [ 599.265885] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.473883] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.681904] video4linux video1: frame start syncpt timeout: -11 [ 599.681909] video4linux video1: MW_ACK_DONE syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 599.897884] video4linux video1: MW_ACK_DONE syncpt timeout: -11Similar to the test above where I had an IMX219 connected. Except it didn't
hang with the IMX274 (I'm beginning to suspect a locking issue in the imx219
driver that is causing the hang, I'll look at that tomorrow).Quoted 8 lines
If I connect the IMX219 to the middle camera connector, then it works fine.
I think I tested this with the IMX274 as well, but I'm not 100% certain, also
something to double check tomorrow.If I connect the IMX219 or IMX274 to the third camera connector, then I get this:
Would like to know CSI port mapping to connectors as mipi calibrate pads cells need to be updated in device tree based on CSI port in use.
Will see if I can find that from DS link you sent above.
Quoted 54 lines
$ v4l2-ctl -d0 --stream-mmap [ 820.513866] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.525354] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.536780] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.548222] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.559639] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <[ 820.646931] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.658355] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.669797] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.681216] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.692601] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <<<<<<<<<<<<<<< 14.50 fps
<<<<<<<<<<<<<<< 14.75 fps
<<<<<<<<<<<<<<< 14.73 fps
<<<<<<<<<<<<<<< 14.80 fps
<<<<<<<<<<<<<[ 825.517854]tegra_mc_irq: 133437 callbacks suppressed [ 825.517874] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.534395] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.545833] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.557280] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.579346] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.590764] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.602188] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.613649] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.625075] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.645983] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) < 14.64 fps
<<<<<<<<<<<<<<<< 14.87 fps
<<<<<<<<<<<<<<< 14.89 fpsQuoted 1 line
Something is producing EMEM address decode errors. But it is streaming.
above memory controller errors may be due to access faults and not sure why these show up on your setup. I never have these with my testing.
Also I am using CMA alloc of 256MB and not sure if low CMA alloc size is causing this. Can you try with CMA alloc size of 256MB?
Quoted 8 lines
If I enable the TPG then everything is fine.
So I have currently three different behaviors for three camera connectors.
Do you have a datasheet for your Jetson TX1 camera board? It could be useful
to compare the two.Quoted 11 lines
Yeah we have and will send it offline.
Also based on connector mapping to corresponding CSI port, mipi-calibrate pad cell value also need to be changed.
Below is for CSI-A
nvidia,mipi-calibrate = <&mipi
0x001>Quoted 3 lines
Regards,
Hans
Connector-1 is CSI-AB where you had timeouts.
Connector-2 is CSI-CD and this works for you.
Connector-3 is CSI-EF and this works for streaming from above but there's memory access fault errors (EMEM address decode errors)
These EMEM decode errors are not related to connector but its just they showed up during connector-3 testing I believe. Can you also keep CMA size to 256MB and try?
Not sure if CSI-AB issue with FS and
MW_ACKsp timeouts are due to some HW/setup issue. Streaming should work on CSI-AB ports as well just like CSI-CD/EF with proper device tree change for port index and mipi calibrate cells for corresponding ports.Quoted 7 lines
Quoted 3 lines
On my setup that I tested IMX274 is on CSI-AB.
Will update my side test results with today's linux-next
Hans,
We have this module as well. Will try to get this today for testing and will update just to make sure of this combo as well on my side.
Sowjanya,
A quick update: I had to update my u-boot and I ended up reinstalling everything.
And now the problems I described just disappeared. Very strange.
Quoted 8 lines
I have yet to verify if the issue with the third camera connector is also solved, I'll do that tomorrow.
But for now you don't have to take any action.
Regards,
Hans
OK. Thanks Hans.
Quoted 207 lines · Hans Verkuil
Quoted 197 lines · Sowjanya Komatineni
Quoted 195 lines · Sowjanya Komatineni
Quoted 166 lines · Sowjanya Komatineni
Quoted 76 lines · Hans Verkuil
Quoted 40 lines · Sowjanya Komatineni
Quoted 9 lines · Hans Verkuil
Quoted 8 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to
Tegra video driver.Jetson TX1 has camera expansion connector and supports custom camera module
designed as per TX1 design specification.Quoted 7 lines
Quoted 5 lines
This series also enables camera capture support for Jetson Nano which has
Raspberry PI camera header.This series is tested with IMX219 camera sensor.
Which tree did you base this on? The
media_treemaster? Or the mainline kernel?These patches are with linux-next base at the time I sent them out which
are on 20200616Quoted 8 lines
I now have the imx219 detected, but if I try to stream I get this:
$ v4l2-ctl --stream-mmap <[ 512.840944] video4linux video0: MW_ACK_DONE syncpt timeout: -11 [ 512.972975] video4linux video0: frame start syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 513.180770] video4linux video0: MW_ACK_DONE syncpt timeout: -11Quoted 7 lines
And then everything hangs and I need to reset.
I'm testing with the
media_treemaster with your patches on top.Regards,
Hans
Are you using same device tree as I sent offline? It uses CSI A for IMX219.
Does you setup also uses CSI-A as x2 for IMX219?
Quoted 8 lines
I tested them on Jetson Nano + IMX219 rasp PI module and also on Jetson
TX1 + IMX274.I did not see any issue and am able to capture from both.
Will try again on my side with today's latest linux-next and update result.
Please use the
media_treemaster, that's what I use as well.I did some more testing and there is something weird going on.
I have a Leopard Imaging camera expansion board (LI-JTX1-MIPI-ADPT) with
three camera connectors. See here for the datasheet:https://www.leopardimaging.com/uploads/LI-TX1-KIT-IMX274M12-T_datasheet.pdf
The first connector (with an IMX274) causes this error:
$ v4l2-ctl -d1 --stream-mmap [ 599.265885] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.473883] video4linux video1: MW_ACK_DONE syncpt timeout: -11 [ 599.681904] video4linux video1: frame start syncpt timeout: -11 [ 599.681909] video4linux video1: MW_ACK_DONE syncpt timeout: -11 <VIDIOC_DQBUF: failed: Input/output error [ 599.897884] video4linux video1: MW_ACK_DONE syncpt timeout: -11Similar to the test above where I had an IMX219 connected. Except it didn't
hang with the IMX274 (I'm beginning to suspect a locking issue in the imx219
driver that is causing the hang, I'll look at that tomorrow).Quoted 8 lines
If I connect the IMX219 to the middle camera connector, then it works fine.
I think I tested this with the IMX274 as well, but I'm not 100% certain, also
something to double check tomorrow.If I connect the IMX219 or IMX274 to the third camera connector, then I get this:
Would like to know CSI port mapping to connectors as mipi calibrate pads cells need to be updated in device tree based on CSI port in use.
Will see if I can find that from DS link you sent above.
Quoted 55 lines
$ v4l2-ctl -d0 --stream-mmap [ 820.513866] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)[ 820.525354] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.536780] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.548222] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error)
[ 820.559639] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <[ 820.646931] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.658355] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.669797] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.681216] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 820.692601] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) <<<<<<<<<<<<<<< 14.50 fps
<<<<<<<<<<<<<<< 14.75 fps
<<<<<<<<<<<<<<< 14.73 fps
<<<<<<<<<<<<<<< 14.80 fps
<<<<<<<<<<<<<[ 825.517854]tegra_mc_irq: 133437 callbacks suppressed [ 825.517874] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.534395] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.545833] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.557280] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.579346] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.590764] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.602188] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.613649] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.625075] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) [ 825.645983] tegra-mc 70019000.memory-controller: viw: write @0x00000001b5fd08c0: EMEM address decode error (EMEM decode error) < 14.64 fps
<<<<<<<<<<<<<<<< 14.87 fps
<<<<<<<<<<<<<<< 14.89 fpsQuoted 1 line
Something is producing EMEM address decode errors. But it is streaming.
above memory controller errors may be due to access faults and not sure why these show up on your setup. I never have these with my testing.
Also I am using CMA alloc of 256MB and not sure if low CMA alloc size is causing this. Can you try with CMA alloc size of 256MB?
Quoted 9 lines
If I enable the TPG then everything is fine.
So I have currently three different behaviors for three camera connectors.
Do you have a datasheet for your Jetson TX1 camera board? It could be useful
to compare the two.Quoted 11 lines
Yeah we have and will send it offline.
Also based on connector mapping to corresponding CSI port, mipi-calibrate pad cell value also need to be changed.
Below is for CSI-A
nvidia,mipi-calibrate = <&mipi
0x001>Quoted 3 lines
Regards,
Hans
Connector-1 is CSI-AB where you had timeouts.
Connector-2 is CSI-CD and this works for you.
Connector-3 is CSI-EF and this works for streaming from above but there's memory access fault errors (EMEM address decode errors)
These EMEM decode errors are not related to connector but its just they showed up during connector-3 testing I believe. Can you also keep CMA size to 256MB and try?
Not sure if CSI-AB issue with FS and
MW_ACKsp timeouts are due to some HW/setup issue. Streaming should work on CSI-AB ports as well just like CSI-CD/EF with proper device tree change for port index and mipi calibrate cells for corresponding ports.Quoted 8 lines
Quoted 3 lines
On my setup that I tested IMX274 is on CSI-AB.
Will update my side test results with today's linux-next
Hans,
We have this module as well. Will try to get this today for testing and will update just to make sure of this combo as well on my side.
Quoted 8 lines
Sowjanya,
A quick update: I had to update my u-boot and I ended up reinstalling everything.
And now the problems I described just disappeared. Very strange.
I have yet to verify if the issue with the third camera connector is also solved, I'll do that tomorrow.
I've now verified the third camera connector with the imx274, and that too works fine.
I did find a few compliance issues in several places, so expect to see some patches (mostly in the sensor drivers).
It's all looking pretty good, so thank you for working on this!
Regards,
Hans
Quoted 7 lines
But for now you don't have to take any action.
Regards,
Hans
Hi Sowjanya,
Quoted 24 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.
Quoted 7 lines
Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.
I tested all this with imx219 and imx274. It all looks good. I'll do a last code review on Monday.
I posted a few imx219 and imx274 patches to fix v4l2-compliance issues (also updated that tool itself since it had a bug).
There is one remaining compliance failure with the imx274, but that is also due to a bug in the imx274: it's missing a bunch of enum ops and it is doing weird things with the COMPOSE selection. I think that's completely wrong, but I need more time to dig into that.
Regards,
Hans
Quoted 52 lines
Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and
power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++ arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770 +++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +- 16 files changed, 1251 insertions(+), 100 deletions(-)
Sowjanya Komatineni
maintainerQuoted 40 lines · Hans Verkuil
Hi Sowjanya,
Quoted 24 lines · Sowjanya Komatineni
This series adds support for video capture from external camera sensor to Tegra video driver.
Jetson TX1 has camera expansion connector and supports custom camera module designed as per TX1 design specification.
This series also enables camera capture support for Jetson Nano which has Raspberry PI camera header.
This series is tested with IMX219 camera sensor.
This series include,
VI I2C related fixes
- Camera sensor programming happens through VI I2C which is on host1x bus.
- These patches includes device tree and I2C driver fixes for VI I2C.Tegra video driver updates
- TPG Vs Non-TPG based onKconfig
- Support for external sensor video capture based on device graph from DT.
- Support for selection ioctl operations
- Tegra MIPI CSI pads calibration
- CSI T-CLK and T-HS settle time computation based on clock rates.Quoted 7 lines
Host1x driver updates
- Adds API to allow creating mipi device for specific device node.
- Splits MIPI pads calibrate start and waiting for calibration to be done.Device tree updates
- Adds camera connector 2V8, 1V8, 1V2 regulator supplies to Jetson TX1 DT.
- Enabled VI and CSI support in Jetson Nano DT.I tested all this with imx219 and imx274. It all looks good. I'll do a last code review on Monday.
I posted a few imx219 and imx274 patches to fix v4l2-compliance issues (also updated that tool itself since it had a bug).
Quoted 8 lines
There is one remaining compliance failure with the imx274, but that is also due to a bug in the imx274: it's missing a bunch of enum ops and it is doing weird things with the COMPOSE selection. I think that's completely wrong, but I need more time to dig into that.
Regards,
Hans
Thanks Hans.
Quoted 52 lines
Quoted 52 lines
Delta between patch versions:
[v2]: Includes below changes based on v1 feedback
- dt-binding document and the driver update for device graph to use separate ports for sink endpoint and source endpoint for csi.
- Use data-lanes endpoint property for csi.
- Updatetegra_mipi_request()to take device node pointer argument rather than adding extra API.
- Remove checking for clk pointer beforeclk_disable.Sowjanya Komatineni (18):
dt-bindings: i2c: tegra: Document Tegra210 VI I2C clocks and
power-domains
arm64: tegra: Add missing clocks and power-domains to Tegra210 VI I2C
i2c: tegra: Don't mark VI I2C as IRQ safe runtime PM
i2c: tegra: Fix the error path integra_i2c_runtime_resume
i2c: tegra: Fix runtime resume to re-init VI I2C
i2c: tegra: Avoidtegra_i2c_init_dma()for Tegra210 vi i2c
media: tegra-video: Fix channel format alignment
media: tegra-video: Enable TPG based on kernel config
media: tegra-video: Update format lookup to offset based
dt-bindings: tegra: Update VI and CSI bindings with port info
media: tegra-video: Add support for external sensor capture
media: tegra-video: Add support for selection ioctl ops
gpu: host1x: mipi: Updatetegra_mipi_request()to be node based
gpu: host1x: mipi: Splittegra_mipi_calibrateandtegra_mipi_wait
media: tegra-video: Add CSI MIPI pads calibration
media: tegra-video: Compute settle times based on the clock rate
arm64: tegra: jetson-tx1: Add camera supplies
arm64: tegra: Enable Tegra VI CSI support for Jetson Nano.../display/tegra/nvidia,tegra20-host1x.txt | 92 ++- .../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 19 +- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 41 ++ arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 10 + arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 + drivers/gpu/drm/tegra/dsi.c | 9 +- drivers/gpu/host1x/mipi.c | 30 +- drivers/i2c/busses/i2c-tegra.c | 39 +- drivers/staging/media/tegra-video/Kconfig | 7 + drivers/staging/media/tegra-video/csi.c | 245 ++++++- drivers/staging/media/tegra-video/csi.h | 8 + drivers/staging/media/tegra-video/tegra210.c | 25 +- drivers/staging/media/tegra-video/vi.c | 770 +++++++++++++++++++-- drivers/staging/media/tegra-video/vi.h | 23 +- drivers/staging/media/tegra-video/video.c | 23 +- include/linux/host1x.h | 4 +- 16 files changed, 1251 insertions(+), 100 deletions(-)