On Sun Jul 6 11:47:22 2025 +0200, Hans de Goede wrote:
> Add support for the selection API as expected by libcamera.
>
> Note the driver only supports a single fixed resolution and
> no cropping, so this is a simple read-only implementation.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy S
On Sat May 17 13:40:59 2025 +0200, Hans de Goede wrote:
> Implement internal_ops.init_state to fill in the v4l2_mbus_framefmt
> struct in newly allocated sd-state structs.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/20250517114106.43494-17-ha
On Sun Jul 6 11:53:24 2025 +0200, Hans de Goede wrote:
> Add support for the vblank and hblank controls, these controls
> are mandatory for using the sensor driver with libcamera.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/20250517114106.434
On Fri Jul 4 11:20:46 2025 +0200, Hans de Goede wrote:
> When v4l2_subdev_call(sensor, s_stream, 1) fails atomisp_start_streaming()
> was not properly returning the buffer ownership back to the videobuf2-core
> code, resulting in:
>
> [ 1318.153447] [ cut here ]
> [ 1318.15
On Sat May 17 13:41:04 2025 +0200, Hans de Goede wrote:
> On raw camera sensors the framerate is controlled through vblank
> (and optional) hblank controls.
>
> Having a get_frame_interval makes no sense in this case, drop it.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Kieran Bingham
> Rev
On Sat May 17 13:40:54 2025 +0200, Hans de Goede wrote:
> Add a check_hwcfg() function to check if the external clk-freq, CSI
> link-freq and lane-count match the driver's expectations.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/202505171141
On Sat May 17 13:41:03 2025 +0200, Hans de Goede wrote:
> The i2c-client's power-domain has already been powered up when probe()
> gets called. So e.g. ACPI resources for regulators and clks have
> already been enabled and only the GPIOs need to be set to the on state.
>
> Instead of calling pm_ru
On Sun Jul 6 11:53:53 2025 +0200, Hans de Goede wrote:
> When an exposure value > (mode-height + vblank) gets set the sensor will
> automatically increase vblank, lowering the framerate.
>
> This is not desirable, limit exposure the maximum exposure to mode-height +
> vblank to avoid the unwanted
On Sat May 17 13:41:01 2025 +0200, Hans de Goede wrote:
> Stop having a v4l2_mbus_framefmt mode.fmt driver-data member to store
> the fmt for the active-state, instead use sd.active_state fmt.
>
> This also removes the need for gc0310_get_pad_format() since
> v4l2_subdev_state_get_format() now wil
On Sat May 17 13:41:02 2025 +0200, Hans de Goede wrote:
> Move the suspend()/resume() functions to above gc0310_detect() and rename
> the functions to power_off()/power_on().
>
> No functional changes, this is a preparation patch for reworking
> the runtime-pm handling in probe() and remove().
>
On Sat May 3 17:00:30 2025 -0300, Pablo wrote:
> Fix a coding style:
> "ERROR: that open brace { should be on the previous line"
> issue reported in ia_css_vf.host.c:94.
>
> Signed-off-by: Pablo
> Link: https://lore.kernel.org/r/20250503200030.5982-1-pa...@pablo.ct.ws
> Signed-off-by: Hans de Goe
On Fri Jul 4 11:20:56 2025 +0200, Hans de Goede wrote:
> atomisp_start_streaming() starts the media pipeline before calling
> atomisp_css_start(). On atomisp_css_start() failures stop the pipeline
> before returning the error.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Lin
On Fri Jun 27 13:06:04 2025 +0300, Abdelrahman Fekry wrote:
> The sysfs attributes active_bo and free_bo expose internal buffer
> state used only for debugging purposes. These are not part of
> any standard kernel ABI, and need to be removed before this
> driver may be moved out of drivers/staging.
On Sat May 17 13:40:57 2025 +0200, Hans de Goede wrote:
> Switch from s_stream() to enable_streams() and disable_streams() pad
> operations. They are preferred and required for streams support.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/2025
On Fri Jul 4 21:17:29 2025 +0200, Hans de Goede wrote:
> Many functions on the gc0310 driver use a function local variable called
> "dev" but these variable's type is not "struct device *" type as one would
> expect based on the name. Instead they point to the gc0310 driver data
> struct.
>
> Rena
On Sat May 17 13:41:05 2025 +0200, Hans de Goede wrote:
> The g_skip_frames sensor-op is obsolete, drop it.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Kieran Bingham
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/20250517114106.43494-23-ha...@kernel.org
> Signed-off-by: M
On Fri Jul 4 11:21:34 2025 +0200, Hans de Goede wrote:
> Commit c7194b21809e ("media: atomisp: On streamoff wait for buffers owned
> by the CSS to be given back") added draining of the CSS buffer queue to
> the beginning of atomisp_stop_stream().
>
> But it turns out that when telling the CSS to s
On Fri Jul 4 21:20:16 2025 +0200, Hans de Goede wrote:
> Switch the GC0310 driver over to the CCI register access helpers.
>
> While at it also add a _REG prefix to all register address defines
> to make clear they are register addresses and group register value
> defines together with the address
On Thu Jun 19 10:44:22 2025 +0200, Thomas Andreatta wrote:
> Reorder const qualifier in array declaration.
>
> Signed-off-by: Thomas Andreatta
> Link:
> https://lore.kernel.org/r/20250619084420.146151-3-thomas.andreatta2...@gmail.com
> Reviewed-by: Hans de Goede
> Signed-off-by: Hans de Goede
On Fri Jul 4 21:18:15 2025 +0200, Hans de Goede wrote:
> Drop the unused GC0310_FOCAL_LENGTH_NUM define, the focal-length
> is a property of the sensor-module, not of the raw sensor itself.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Kieran Bingham
> Reviewed-by: Andy Shevchenko
> Link: htt
On Sun Jul 6 11:53:40 2025 +0200, Hans de Goede wrote:
> Add camera orientation and sensor rotation controls using
> the v4l2_fwnode_device_parse() and v4l2_ctrl_new_fwnode_properties()
> helpers.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/2
On Fri Jul 4 11:24:02 2025 +0200, Hans de Goede wrote:
> Replace the duplicate code for calling the special Intel camera sensor GPIO
> type _DSM (79234640-9e10-4fea-a5c1-b5aa8b19756f) and mapping GPIOs to
> the sensor with a call to int3472_discrete_parse_crs() from the int3472
> driver.
>
> Besid
On Sat May 17 13:40:58 2025 +0200, Hans de Goede wrote:
> Switch to using the sub-device state lock and properly call
> v4l2_subdev_init_finalize() / v4l2_subdev_cleanup() on probe() /
> remove().
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/2
On Fri Jul 4 11:20:30 2025 +0200, Hans de Goede wrote:
> Move atomisp_stop_streaming() above atomisp_start_streaming(), this is
> a preparation patch for making atomisp_start_streaming() properly cleanup
> if starting the sensor stream fails.
>
> No functional change, only moving a block of code u
On Thu Jun 19 10:44:24 2025 +0200, Thomas Andreatta wrote:
> Reorder const qualifier in array declaration.
>
> Signed-off-by: Thomas Andreatta
> Link:
> https://lore.kernel.org/r/20250619084420.146151-4-thomas.andreatta2...@gmail.com
> Reviewed-by: Hans de Goede
> Signed-off-by: Hans de Goede
On Sat May 17 13:40:56 2025 +0200, Hans de Goede wrote:
> is_streaming is only set and never read, drop it.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/20250517114106.43494-14-ha...@kernel.org
> Signed-off-by: Mauro Carvalho Chehab
Patch co
On Sun Jul 6 11:53:15 2025 +0200, Hans de Goede wrote:
> Add support for the pixelrate control as expected by libcamera,
> while at it also add the link-frequency control.
>
> Signed-off-by: Hans de Goede
> Link: https://lore.kernel.org/r/20250517114106.43494-8-hdego...@redhat.com
> Signed-off-by
On Fri Jul 4 21:18:27 2025 +0200, Hans de Goede wrote:
> Currently the sensor is running 30.9 fps, increase vblank
> to have it actually run at 30.0 fps.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.org/r/20250517114106.43494-4-hdego...@redhat.com
>
On Sat May 17 13:40:55 2025 +0200, Hans de Goede wrote:
> Reduce the unnecessary long msleep(100) done on stream start to 10 ms and
> move this to gc0310_resume() so that it is also done on the initial
> power-up done by gc0310_detect(), which should fix gc0310_detect()
> sometimes failing.
>
> Wh
On Sat May 17 13:41:00 2025 +0200, Hans de Goede wrote:
> Now that the sd-state's fmt is properly initialized by
> internal_ops.init_state(), the driver can be safely switched
> to v4l2_subdev_get_fmt().
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Andy Shevchenko
> Link: https://lore.kernel.
On Mon May 19 18:46:47 2025 +0300, Andy Shevchenko wrote:
> There are some unused definitions that are using macros from
> math_support.h. In order to have cleaner future changes, remove them first.
>
> Signed-off-by: Andy Shevchenko
> Link:
> https://lore.kernel.org/r/20250519155028.526453-2-an
On Fri Jul 4 11:21:08 2025 +0200, Hans de Goede wrote:
> The atomisp interrupt handling will free the MIPI / CSI-receiver buffers
> when processing a frame-completion event if the stop_requested flag is set,
> but only in the ISP2400 / BYT, not in the ISP2401 / CHT case.
>
> There are 2 problems w
On Fri Jul 4 22:54:19 2025 +0200, Hans de Goede wrote:
> Use V4L2_CID_ANALOGUE_GAIN for gain control, as expected by userspace.
>
> Signed-off-by: Hans de Goede
> Link: https://lore.kernel.org/r/20250517114106.43494-6-hdego...@redhat.com
> Signed-off-by: Mauro Carvalho Chehab
Patch committed.
On Thu Jun 19 10:44:20 2025 +0200, Thomas Andreatta wrote:
> Checkpatch fix: deleted `dev_dbg()` printing the name of the function.
> ftrace can be used instead.
>
> Signed-off-by: Thomas Andreatta
> Link:
> https://lore.kernel.org/r/20250619084420.146151-2-thomas.andreatta2...@g
On Mon May 19 18:46:49 2025 +0300, Andy Shevchenko wrote:
> After recent cleanups the few macros become unused. Remove them.
>
> Signed-off-by: Andy Shevchenko
> Link:
> https://lore.kernel.org/r/20250519155028.526453-4-andriy.shevche...@linux.intel.com
> Reviewed-by: Hans de Goede
> Tested-by:
On Sat Jun 28 08:25:36 2025 +0300, Abdelrahman Fekry wrote:
> The HMM_BO_DEVICE_INITED flag was being set in hmm_bo_device_init()
> before key initialization steps like kmem_cache_create(),
> kmem_cache_alloc(), and __bo_init().
>
> This means that if any of these steps fail, the flag remains set,
On Fri Jul 4 19:10:51 2025 +0300, Abdelrahman Fekry wrote:
> Continue the cleanup of the AtomISP driver, as discussed with Hans and Andy
> in [1].
>
> Tackle TODO item: "Remove custom sysfs files created by atomisp_drvfs.c":
> - Remove the sysfs attributes `dbglvl`, `dbgfun`, and `dbgopt`.
> - Del
On Mon Jun 30 13:08:49 2025 +0200, Hans Verkuil wrote:
> Ensure that the interrupt function names clearly state for which
> gpio they are (cec/hpd/5v). No functional changes.
>
> Signed-off-by: Hans Verkuil
> Signed-off-by: Mauro Carvalho Chehab
Patch committed.
Thanks,
Mauro Carvalho Chehab
On Wed Jun 25 08:35:36 2025 +0200, Hans Verkuil wrote:
> When the EDID is updated, the hotplug detect signal must remain low for
> 100 ms minimum. Currently these three drivers use that exact minimum,
> but some HDMI transmitters need the HPD to be low for a bit longer
> before they detect that the
On Mon May 19 18:46:48 2025 +0300, Andy Shevchenko wrote:
> Replace rarely used macros by generic ones from Linux kernel headers.
>
> Signed-off-by: Andy Shevchenko
> Link:
> https://lore.kernel.org/r/20250519155028.526453-3-andriy.shevche...@linux.intel.com
> Reviewed-by: Hans de Goede
> Teste
On Mon Jun 30 13:08:46 2025 +0200, Hans Verkuil wrote:
> This adds support for inserting 'glitches' after a falling and/or
> rising edge. This tests what happens when there are little voltage
> spikes after falling or rising edges, which can be caused due to
> noise or reflections on the CEC line.
On Sun Jul 6 12:55:40 2025 +0200, Hans Verkuil wrote:
> The pixel_array control size was calculated incorrectly:
> the dimensions were swapped (dims[0] should be the height), and the
> values should be the width or height divided by PIXEL_ARRAY_DIV
> and rounded up. So don't use roundup, but use DI
On Mon Jun 30 13:08:47 2025 +0200, Hans Verkuil wrote:
> If rx-no-low-drive is set, then the CEC pin framework will disable
> the detection of situations where a Low Drive has to be generated.
>
> So if this is set, then we will never generate Low Drives.
>
> This helps testing whether other CEC
On Mon Jun 30 13:08:48 2025 +0200, Hans Verkuil wrote:
> Document rx-no-low-drive and the new support to inject
> glitches.
>
> Signed-off-by: Hans Verkuil
> Signed-off-by: Mauro Carvalho Chehab
Patch committed.
Thanks,
Mauro Carvalho Chehab
.../userspace-api/media/cec/cec-pin-error-inj.rst
On Mon Jun 30 13:08:50 2025 +0200, Hans Verkuil wrote:
> Reading the hpd or 5v gpios is something that can sleep, so rework
> the code to allow this.
>
> Signed-off-by: Hans Verkuil
> Signed-off-by: Mauro Carvalho Chehab
Patch committed.
Thanks,
Mauro Carvalho Chehab
drivers/media/cec/platfo
On Tue Jun 24 08:30:46 2025 +0200, Hans Verkuil wrote:
> Use hverk...@kernel.org as the main address for kernel work.
>
> Signed-off-by: Hans Verkuil
> Signed-off-by: Mauro Carvalho Chehab
Patch committed.
Thanks,
Mauro Carvalho Chehab
.mailmap | 5 +++--
1 file changed, 3 insertions(+), 2 d
On Thu May 29 12:13:17 2025 +0800, Bingbu Cao wrote:
> Intel Image Processing Unit 7th Gen includes input and processing systems
> and the hardware presents itself as a single PCI device in system same
> as IPU6.
>
> The IPU7 PCI device driver basically does PCI configurations, basic
> hardware co
On Thu May 29 12:13:18 2025 +0800, Bingbu Cao wrote:
> The Intel IPU7 has internal microprocessor which runs the firmware
> The microprocessor accesses system DRAM by its internal 32-bit virtual
> address space. Driver should setup the MMU table and expose the DMA
> APIs for memory buffer mapping.
On Thu May 29 12:13:19 2025 +0800, Bingbu Cao wrote:
> IPU7 irmware is generated and released as signed Code Partition
> Directory (CPD) format file which is aligned with the SPI flash code
> partition definition. The driver parses the CPD based on the layout.
>
> Syscom is an inter-process(or) co
On Thu May 29 12:13:20 2025 +0800, Bingbu Cao wrote:
> IPU7 firmware defines the ABIs between firmware and software, this
> patch adds a series of ABI headers.
>
> Signed-off-by: Bingbu Cao
> Signed-off-by: Sakari Ailus
> Signed-off-by: Hans Verkuil
Patch committed.
Thanks,
Hans Verkuil
dri
On Thu May 29 12:13:21 2025 +0800, Bingbu Cao wrote:
> The main input system driver mainly cover the basic hardware setup, v4l2
> devices registration, firmware stream interfaces and interrupt handling.
>
> Input system CSI2 receiver is exposed as a v4l2 sub-device. Each CSI2
> sub-device represen
On Thu May 29 12:13:22 2025 +0800, Bingbu Cao wrote:
> Update MAINTAINERS file for Intel IPU7 input system staging driver.
>
> Signed-off-by: Bingbu Cao
> Signed-off-by: Sakari Ailus
> Signed-off-by: Hans Verkuil
Patch committed.
Thanks,
Hans Verkuil
MAINTAINERS | 9 +
1 file change
On Thu Jul 3 17:53:19 2025 +0300, Sakari Ailus wrote:
> This driver is intended for IPU7 at the moment so drop the IPU8 PCI ID.
>
> Signed-off-by: Sakari Ailus
> Signed-off-by: Hans Verkuil
Patch committed.
Thanks,
Hans Verkuil
drivers/staging/media/ipu7/ipu7.c | 1 -
1 file changed, 1 delet
On Thu May 29 12:13:23 2025 +0800, Bingbu Cao wrote:
> Add Kconfig and Makefile for IPU7 driver and also update
> the Makefile to build the IPU7 driver.
>
> Also add a to-do file to list the TODOs.
>
> Signed-off-by: Bingbu Cao
> Signed-off-by: Sakari Ailus
> Signed-off-by: Hans Verkuil
Patch
On Mon Jun 16 15:29:14 2025 +, Ricardo Ribalda wrote:
> The driver uses "whole" fps in all its calculations (e.g. in
> load_per_instance()). Those calculation expect an fps bigger than 1, and
> not big enough to overflow.
>
> Clamp the value if the user provides a param that will result in an
On Thu Jun 12 07:53:51 2025 +0530, Renjiang Han wrote:
> Some platforms (such as qcs615 and sc7180) use the same core but have
> different frequency tables. Using the opp-table allows us to separate
> the core description from the frequency data and supports the use of
> fallback compatibles.
>
>
On Sat May 31 14:22:00 2025 +0200, Konrad Dybcio wrote:
> Fill in the correct data for the production SKU.
>
> Fixes: 193b3dac29a4 ("media: venus: add msm8998 support")
> Cc: sta...@vger.kernel.org
> Signed-off-by: Konrad Dybcio
> Reviewed-by: Vikash Garodia
> Reviewed-by: Bryan O'Donoghue
> Re
On Fri May 9 14:08:57 2025 +0530, Dikshita Agarwal wrote:
> Correct a typo from "dpeth" to "depth".
>
> Cc: sta...@vger.kernel.org
> Fixes: 3a19d7b9e08b ("media: iris: implement set properties to firmware
> during streamon")
> Acked-by: Vikash Garodia
> Reviewed-by: Bryan O'Donoghue
> Tested-by
On Fri May 9 14:09:00 2025 +0530, Dikshita Agarwal wrote:
> Firmware sends capture buffers with 0 filled length which are not to be
> displayed and should be dropped by client.
> To achieve the same, add V4L2_BUF_FLAG_ERROR to such buffers by making
> sure:
> - These 0 length buffers are not return
On Fri May 9 14:08:47 2025 +0530, Dikshita Agarwal wrote:
> Firmware might hold the DPB buffers for reference in case of sequence
> change, so skip destroying buffers for which QUEUED flag is not removed.
>
> Cc: sta...@vger.kernel.org
> Fixes: 73702f45db81 ("media: iris: allocate, initialize and
On Wed Jun 11 11:13:44 2025 +0530, Akhil P Oommen wrote:
> Pass PD_FLAG_REQUIRED_OPP flag to allow opp framework to scale the rpmpd
> power domains.
>
> Signed-off-by: Akhil P Oommen
> Reviewed-by: Dikshita Agarwal
> Signed-off-by: Bryan O'Donoghue
> Signed-off-by: Hans Verkuil
Patch committe
On Fri May 9 14:09:08 2025 +0530, Dikshita Agarwal wrote:
> Extend the decoder driver's supported formats to include HEVC (H.265)
> and VP9. This change updates the format enumeration (VIDIOC_ENUM_FMT)
> and allows setting these formats via VIDIOC_S_FMT.
>
> Reviewed-by: Bryan O'Donoghue
> Acked-
On Mon Jun 16 16:46:38 2025 +0300, Laurent Pinchart wrote:
> A few functions have documented locking conventions. Documentation is
> nice, but runtime checks are better. Enforce the conventions with
> lockdep assertions.
>
> Signed-off-by: Laurent Pinchart
> Reviewed-by: Jacopo Mondi
> Reviewed-
On Fri May 9 14:09:06 2025 +0530, Dikshita Agarwal wrote:
> Currently, the stream off process checks the count of buffers in
> v4l2_m2m_queues using v4l2_m2m_for_each_src_buf_safe and
> v4l2_m2m_for_each_dst_buf_safe APIs. If the count is non-zero, it
> returns an error. This check is redundant as
On Wed Jun 25 10:20:32 2025 +0100, Daniel Scally wrote:
> Add support to the rzg2l-cru driver to capture 10/12/14 bit bayer
> data and output it into the CRU's 64-bit packed pixel format.
>
> Reviewed-by: Jacopo Mondi
> Reviewed-by: Laurent Pinchart
> Reviewed-by: Lad Prabhakar
> Signed-off-by:
On Tue May 13 17:23:48 2025 +0300, Vladimir Zapolskiy wrote:
> A media device can and at least for sake of simplicity should be registered
> before V4L2 devices including the ones added on async completion.
>
> The change removes the second and out of camss_probe() media device
> registration path
On Fri May 9 14:09:01 2025 +0530, Dikshita Agarwal wrote:
> Add a condition to skip the flush operation during the first sequence
> change event. At this point, the capture queue is not streaming, making
> the flush unnecessary.
>
> Cc: sta...@vger.kernel.org
> Fixes: 84e17adae3e3 ("media: iris: a
On Fri May 9 14:09:02 2025 +0530, Dikshita Agarwal wrote:
> Currently, The flush completion signal is being re-initialized even
> though no response is expected during a sequence change.
>
> Simplify the code by removing re-initialization of flush completion
> signal as it is redundant.
>
> Cc: s
On Fri May 9 14:09:11 2025 +0530, Dikshita Agarwal wrote:
> Add internal buffer count and size calculations for HEVC and VP9
> decoders.
>
> Acked-by: Vikash Garodia
> Tested-by: Neil Armstrong # on SM8550-QRD
> Tested-by: Neil Armstrong # on SM8550-HDK
> Tested-by: Neil Armstrong # on SM8650-
On Fri May 9 14:08:51 2025 +0530, Dikshita Agarwal wrote:
> Currently, port check enforces that session property response must
> arrive only on the BITSTREAM port. However, firmware can send some
> responses on other port as well.
>
> Remove the strict port validation to correctly handle session p
On Fri May 2 23:41:42 2025 +0300, Vladimir Zapolskiy wrote:
> Since clock lanes under CSIPHY are hard-wired and non-selectable,
> it makes sense to remove this port property.
>
> The change follows the same logic as found in commit 336136e197e2
> ("media: dt-bindings: media: camss: Remove clock-la
On Tue Apr 29 10:16:09 2025 +0100, Lad Prabhakar wrote:
> Correct the misnamed FIFO-empty helper for the RZ/G3E CRU. Rename
> `rz3e_fifo_empty` to `rzg3e_fifo_empty` to match the intended
> naming convention.
>
> Reported-by: Biju Das
> Closes:
> https://lore.kernel.org/all/ty3pr01mb11346e57a3df
On Mon Aug 5 16:55:35 2024 +0200, Jacopo Mondi wrote:
> Currently the 'pispbe_schedule()' function does two things:
>
> 1) Tries to assemble a job by inspecting all the video node queues
>to make sure all the required buffers are available
> 2) Submit the job to the hardware
>
> The pispbe_sc
On Fri May 9 14:08:49 2025 +0530, Dikshita Agarwal wrote:
> Update the width, height and buffer size of CAPTURE based on the
> resolution set to OUTPUT via VIDIOC_S_FMT. This is required to set the
> updated capture resolution to firmware when S_FMT is called only for
> OUTPUT.
>
> Cc: sta...@vger
On Wed Jun 18 17:42:47 2025 +0200, Jacopo Mondi wrote:
> As reported by the Kernel Test Robot, the newly merged vspx driver
> exports a few symbols but doesn't include the export.h header.
>
> While at it, include the header file in vsp1_drm.c which exports
> symbols as well.
>
> Reported-by: ker
On Mon Aug 26 12:24:04 2024 +0200, Jacopo Mondi wrote:
> A comment in the pisp_be driver references the
> pispbe_schedule_internal() function which doesn't exist.
>
> Drop it.
>
> Reviewed-by: Laurent Pinchart
> Reviewed-by: Naushir Patuck
> Signed-off-by: Jacopo Mondi
> Signed-off-by: Hans Ve
On Fri May 9 14:09:07 2025 +0530, Dikshita Agarwal wrote:
> Add a comment to explain usage of MBPS and define a macro for 8K
> resolution for better readability
>
> Acked-by: Vikash Garodia
> Reviewed-by: Bryan O'Donoghue
> Tested-by: Neil Armstrong # on SM8550-QRD
> Tested-by: Neil Armstrong
On Tue May 13 17:23:50 2025 +0300, Vladimir Zapolskiy wrote:
> For sake of code simplicity and readability reduce the function code by
> one level of indentation, the change is non-functional.
>
> Signed-off-by: Vladimir Zapolskiy
> Reviewed-by: Bryan O'Donoghue
> [bod: Fixed indentation error]
On Fri May 9 14:09:05 2025 +0530, Dikshita Agarwal wrote:
> Improve the handling of the V4L2_BUF_FLAG_LAST flag in the driver:
> - Ensure that the last flag is not sent multiple times.
> - Attach the last flag to the first capture buffer returned during
> flush, triggered by a sequence change, ad
On Mon May 19 12:42:22 2025 +0530, Vedang Nagar wrote:
> Currently, The event_seq_changed() handler processes a variable number
> of properties sent by the firmware. The number of properties is indicated
> by the firmware and used to iterate over the payload. However, the
> payload size is not bein
On Fri May 2 23:41:40 2025 +0300, Vladimir Zapolskiy wrote:
> There are 4 CSIPHY ports on X1E80100, it'd be preferred to tinker a too
> loose the regexp, which covers all these port names.
>
> Signed-off-by: Vladimir Zapolskiy
> Acked-by: Bryan O'Donoghue
> Reviewed-by: Krzysztof Kozlowski
> Si
On Thu Jun 19 09:48:30 2025 +0200, Jorge Ramirez-Ortiz wrote:
> Ensure the IRQ is disabled - and all pending handlers completed - before
> dismantling the interrupt routing and clearing related pointers.
>
> This prevents any possibility of the interrupt triggering after the
> handler context has
On Mon May 26 19:28:39 2025 -0400, Richard Acayan wrote:
> The libcamera plugin for Pipewire may keep an open file descriptor to
> the video device, even while streaming. This simplifies its operation,
> as it only needs to keep track of a number instead of a file path. When
> the video device is o
On Thu Jun 12 16:58:21 2025 +0200, Jacopo Mondi wrote:
> Use the clamp() function from minmax.h and provide a define for the max
> sizes as they will be used in subsequent patches.
>
> Reviewed-by: Daniel Scally
> Reviewed-by: Stefan Klug
> Signed-off-by: Jacopo Mondi
> Signed-off-by: Hans Verk
On Fri May 9 14:08:50 2025 +0530, Dikshita Agarwal wrote:
> During reconfig, the firmware sends the resolution aligned to 8 bytes.
> If the driver sends the same resolution back to the firmware the resolution
> will be aligned to 16 bytes not 8.
>
> The alignment mismatch would then subsequently c
On Fri May 9 14:08:55 2025 +0530, Dikshita Agarwal wrote:
> The function pointers responsible for setting firmware properties were
> never initialized in the instance capability structure, causing it to
> remain NULL. As a result, the firmware properties were not being set
> correctly.
>
> Fix thi
On Mon Jun 30 23:27:34 2025 +0100, Daniel Scally wrote:
> The Renesas Camera Receiver Unit in the RZ/V2H SoC can output RAW
> data captured from an image sensor without conversion to an RGB/YUV
> format. In that case the data are packed into 64-bit blocks, with a
> variable amount of padding in the
On Mon May 26 09:52:33 2025 +0200, Tommaso Merciai wrote:
> Correct the misnamed .data member for the RZ/G2L CRU. Rename
> `rzgl2_cru_info` to `rzg2l_cru_info` to match the intended
> naming convention.
>
> Signed-off-by: Tommaso Merciai
> Reviewed-by: Geert Uytterhoeven
> Reviewed-by: Laurent P
On Mon Aug 26 12:29:50 2024 +0200, Jacopo Mondi wrote:
> The config parameters buffer is already validated in
> pisp_be_validate_config() at .buf_prepare() time.
>
> However some of the same validations are also performed at
> pispbe_schedule() time. In particular the function checks that:
>
> 1)
On Fri May 9 14:08:52 2025 +0530, Dikshita Agarwal wrote:
> The current check only considers the core error state before allowing
> writes to the HFI queues. However, the core can also transition to the
> deinit state due to a system error triggered by the response thread.
> In such cases, writing
On Fri May 9 14:09:10 2025 +0530, Dikshita Agarwal wrote:
> Subscribe and set mandatory properties to the firmware for HEVC and VP9
> decoders.
>
> Acked-by: Vikash Garodia
> Tested-by: Neil Armstrong # on SM8550-QRD
> Tested-by: Neil Armstrong # on SM8550-HDK
> Tested-by: Neil Armstrong # on
On Wed Jun 25 10:20:30 2025 +0100, Daniel Scally wrote:
> Rather than open-code a calculation of the format's bytesperline
> and sizeimage, use the v4l2_fill_pixfmt() helper. This makes it
> easier to support the CRU packed pixel formats without over
> complicating the driver.
>
> This change make
On Tue May 13 17:23:46 2025 +0300, Vladimir Zapolskiy wrote:
> It's sufficient to have just one previously set csiphy_formats_sdm845 data.
>
> Signed-off-by: Vladimir Zapolskiy
> Reviewed-by: Bryan O'Donoghue
> Signed-off-by: Bryan O'Donoghue
> Signed-off-by: Hans Verkuil
Patch committed.
Th
On Wed Jun 25 10:20:28 2025 +0100, Daniel Scally wrote:
> Add a callback to implement the VIDIOC_ENUM_FRAMESIZES ioctl for the
> CRU driver.
>
> Reviewed-by: Laurent Pinchart
> Signed-off-by: Daniel Scally
> Link:
> https://lore.kernel.org/r/20250625-rzg2l-cru-v6-2-a9099ed26...@ideasonboard.com
On Fri May 9 14:08:56 2025 +0530, Dikshita Agarwal wrote:
> A warning reported by smatch indicated a possible null pointer
> dereference where one of the arguments to API
> "iris_hfi_gen2_handle_system_error" could sometimes be null.
>
> To fix this, add a check to validate that the argument passe
On Tue Apr 29 10:16:08 2025 +0100, Lad Prabhakar wrote:
> Collapse FIFO empty helper into a single return statement by removing the
> redundant `if (amnfifopntr_w == amnfifopntr_r_y) return true;` path. Make
> `rzg2l_fifo_empty()` directly return `amnfifopntr_w == amnfifopntr_r_y`
> to improve read
On Fri Jun 6 17:25:22 2025 +0200, Jorge Ramirez-Ortiz wrote:
> Make sure the interrupt handler is initialized before the interrupt is
> registered.
>
> If the IRQ is registered before hfi_create(), it's possible that an
> interrupt fires before the handler setup is complete, leading to a NULL
> de
On Tue May 13 17:23:45 2025 +0300, Vladimir Zapolskiy wrote:
> A call to media_device_init() requires media_device_cleanup() counterpart
> to complete cleanup and release any allocated resources.
>
> This has been done in the driver .remove() right from the beginning, but
> error paths on .probe()
On Fri May 9 14:08:54 2025 +0530, Dikshita Agarwal wrote:
> HFI_PROPERTY_CONFIG_VDEC_POST_LOOP_DEBLOCKER is deprecated and no longer
> supported on current firmware, remove setting the same to firmware.
>
> Cc: sta...@vger.kernel.org
> Fixes: 79865252acb6 ("media: iris: enable video driver probe o
On Fri May 9 14:09:03 2025 +0530, Dikshita Agarwal wrote:
> Firmware attach DATACORRUPT/DROP buffer flags for the frames which
> needs to be dropped, handle it by setting VB2_BUF_STATE_ERROR for these
> buffers before calling buf_done.
>
> Reviewed-by: Bryan O'Donoghue
> Acked-by: Vikash Garodia
1 - 100 of 749 matches
Mail list logo
