linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacopo Mondi <jacopo@jmondi.org>
To: Eugen.Hristev@microchip.com
Cc: linux-media@vger.kernel.org, hverkuil-cisco@xs4all.nl,
	Nicolas.Ferre@microchip.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Claudiu.Beznea@microchip.com
Subject: Re: [PATCH v5 04/13] media: atmel: atmel-isc: implement media controller
Date: Wed, 23 Feb 2022 17:34:31 +0100	[thread overview]
Message-ID: <20220223163431.wask6vh2tfhllzf4@uno.localdomain> (raw)
In-Reply-To: <e4109e0f-af1f-7594-a154-92e65fd7ac59@microchip.com>

Hi Eugen,

On Thu, Feb 17, 2022 at 02:59:19PM +0000, Eugen.Hristev@microchip.com wrote:
> On 2/17/22 3:56 PM, Eugen Hristev wrote:
> > Implement the support for media-controller.
> > This means that the capabilities of the driver have changed and now
> > it also advertises the IO_MC .
> > The driver will register it's media device, and add the video entity to this
> > media device. The subdevices are registered to the same media device.
> > The ISC will have a base entity which is auto-detected as atmel_isc_base.
> > It will also register a subdevice that allows cropping of the incoming frame
> > to the maximum frame size supported by the ISC.
> > The ISC will create a link between the subdevice that is asynchronously
> > registered and the atmel_isc_scaler entity.
> > Then, the atmel_isc_scaler and atmel_isc_base are connected through another
> > link.
> >
> > Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
> > ---
>
>
> Hello Jacopo,
>
> I will add to this patch a little update about how the scaler is seen
> now by the media-ctl :
>
> for imx219 sensor, which generates 3280x2464:
>
>
> - entity 1: atmel_isc_scaler (2 pads, 2 links)
>              type V4L2 subdev subtype Unknown flags 0
>              device node name /dev/v4l-subdev0
>          pad0: Sink
>                  [fmt:SRGGB10_1X10/3280x2464 field:none colorspace:srgb
>                   crop.bounds:(0,0)/3280x2464
>                   crop:(0,0)/3264x2464]
>                  <- "csi2dc":1 [ENABLED,IMMUTABLE]
>          pad1: Source
>                  [fmt:SRGGB10_1X10/3264x2464 field:none colorspace:srgb]
>                  -> "atmel_isc_common":0 [ENABLED,IMMUTABLE]
>
>
> The source pad of the scaler looks good now.
>
> For the imx274 which I am using (and it generates 3840x2160 ):
>
> - entity 1: atmel_isc_scaler (2 pads, 2 links)
>              type V4L2 subdev subtype Unknown flags 0
>              device node name /dev/v4l-subdev0
>          pad0: Sink
>                  [fmt:SRGGB10_1X10/3840x2160 field:none colorspace:srgb
>                   crop.bounds:(0,0)/3840x2160
>                   crop:(0,0)/3264x2160]
>                  <- "csi2dc":1 [ENABLED,IMMUTABLE]
>          pad1: Source
>                  [fmt:SRGGB10_1X10/3264x2160 field:none colorspace:srgb]
>                  -> "atmel_isc_common":0 [ENABLED,IMMUTABLE]
>
> So in both cases, each line is cropped down to 3264 as the maximum width.
>
> If we select a lower frame size, the scaler will automatically update
> the source pad to reflect this, e.g.:
>
>
> - entity 1: atmel_isc_scaler (2 pads, 2 links)
>              type V4L2 subdev subtype Unknown flags 0
>              device node name /dev/v4l-subdev0
>          pad0: Sink
>                  [fmt:SRGGB10_1X10/1920x1080 field:none colorspace:srgb
>                   crop.bounds:(0,0)/1920x1080
>                   crop:(0,0)/1920x1080]
>                  <- "csi2dc":1 [ENABLED,IMMUTABLE]
>          pad1: Source
>                  [fmt:SRGGB10_1X10/1920x1080 field:none colorspace:srgb]
>                  -> "atmel_isc_common":0 [ENABLED,IMMUTABLE]
>
>
> does it look good now ?

great! I think it now works as intended, thanks!

I only have one question. BOUND target is the larger rectangle that
contains all crop rectangles. As your max crop is limited to 3264x2160
I wonder if BOUND should be limited by the same size. Does
v4l2-compliance check for this.

Otherwise it looks good!

Thanks
  j

>
> Thanks for checking this out !
> Eugen

  reply	other threads:[~2022-02-23 16:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 13:56 [PATCH v5 00/13] media: atmel: atmel-isc: implement media controller Eugen Hristev
2022-02-17 13:56 ` [PATCH v5 01/13] media: atmel: atmel-isc-base: use streaming status when queueing buffers Eugen Hristev
2022-02-23 17:05   ` Jacopo Mondi
2022-02-17 13:56 ` [PATCH v5 02/13] media: atmel: atmel-isc-base: replace is_streaming call in s_fmt_vid_cap Eugen Hristev
2022-02-23 17:05   ` Jacopo Mondi
2022-02-17 13:56 ` [PATCH v5 03/13] media: atmel: atmel-isc: remove redundant comments Eugen Hristev
2022-02-23 17:06   ` Jacopo Mondi
2022-02-17 13:56 ` [PATCH v5 04/13] media: atmel: atmel-isc: implement media controller Eugen Hristev
2022-02-17 14:59   ` Eugen.Hristev
2022-02-23 16:34     ` Jacopo Mondi [this message]
2022-02-23 16:32   ` Jacopo Mondi
2022-03-01  8:56     ` Eugen.Hristev
2022-02-17 13:56 ` [PATCH v5 05/13] media: atmel: atmel-sama5d2-isc: fix wrong mask in YUYV format check Eugen Hristev
2022-02-23 17:06   ` Jacopo Mondi
2022-02-17 13:56 ` [PATCH v5 06/13] media: atmel: atmel-isc-base: use mutex to lock awb workqueue from streaming Eugen Hristev
2022-02-23 17:07   ` Jacopo Mondi
2022-02-17 13:56 ` [PATCH v5 07/13] media: atmel: atmel-isc: compact the controller formats list Eugen Hristev
2022-02-17 13:56 ` [PATCH v5 08/13] media: atmel: atmel-isc: change format propagation to subdev into only verification Eugen Hristev
2022-02-23 17:03   ` Jacopo Mondi
2022-03-03 15:21     ` Eugen.Hristev
2022-02-17 13:56 ` [PATCH v5 09/13] media: atmel: atmel-sama7g5-isc: remove stray line Eugen Hristev
2022-02-23 17:07   ` Jacopo Mondi
2022-02-17 13:56 ` [PATCH v5 10/13] dt-bindings: media: microchip,xisc: add bus-width of 14 Eugen Hristev
2022-02-17 13:56 ` [PATCH v5 11/13] ARM: dts: at91: sama7g5: add nodes for video capture Eugen Hristev
2022-02-17 13:56 ` [PATCH v5 12/13] ARM: configs: at91: sama7: add xisc and csi2dc Eugen Hristev
2022-02-17 13:56 ` [PATCH v5 13/13] ARM: multi_v7_defconfig: add atmel video pipeline modules Eugen Hristev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220223163431.wask6vh2tfhllzf4@uno.localdomain \
    --to=jacopo@jmondi.org \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Eugen.Hristev@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).