linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mickael GUENE <mickael.guene@st.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"Hugues FRUCHET" <hugues.fruchet@st.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Matt Ranostay <matt.ranostay@konsulko.com>,
	Petr Cvek <petrcvekcz@gmail.com>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Ben Kao" <ben.kao@intel.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	"Todor Tomov" <todor.tomov@linaro.org>,
	Rui Miguel Silva <rui.silva@linaro.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Ricardo Ribalda Delgado <ricardo@ribalda.com>,
	"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
	Tianshu Qiu <tian.shu.qiu@intel.com>,
	Bingbu Cao <bingbu.cao@intel.com>
Subject: Re: [PATCH v3 2/2] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver
Date: Mon, 8 Apr 2019 06:17:18 +0000	[thread overview]
Message-ID: <1c7e0b8a-7441-57eb-38c0-e951917637c6@st.com> (raw)
In-Reply-To: <20190406110135.7l2m6hkmvwr33d7s@kekkonen.localdomain>

Hi Sakari,

On 4/6/19 13:01, Sakari Ailus wrote:
> On Tue, Mar 26, 2019 at 02:36:41PM +0000, Mickael GUENE wrote:
>> Sakari,
>>
>>>> +static int bpp_from_code(__u32 code)
>>>> +{
>>>> +	switch (code) {
>>>> +	case MEDIA_BUS_FMT_SBGGR8_1X8:
>>>> +	case MEDIA_BUS_FMT_SGBRG8_1X8:
>>>> +	case MEDIA_BUS_FMT_SGRBG8_1X8:
>>>> +	case MEDIA_BUS_FMT_SRGGB8_1X8:
>>>> +		return 8;
>>>> +	case MEDIA_BUS_FMT_SBGGR10_1X10:
>>>> +	case MEDIA_BUS_FMT_SGBRG10_1X10:
>>>> +	case MEDIA_BUS_FMT_SGRBG10_1X10:
>>>> +	case MEDIA_BUS_FMT_SRGGB10_1X10:
>>>> +		return 10;
>>>> +	case MEDIA_BUS_FMT_SBGGR12_1X12:
>>>> +	case MEDIA_BUS_FMT_SGBRG12_1X12:
>>>> +	case MEDIA_BUS_FMT_SGRBG12_1X12:
>>>> +	case MEDIA_BUS_FMT_SRGGB12_1X12:
>>>> +		return 12;
>>>> +	case MEDIA_BUS_FMT_UYVY8_2X8:
>>>
>>> This is good for the parallel bus, but on CSI-2 side you should have
>>> MEDIA_BUS_FMT_UYVY8_1X16 instead. This isn't technically correct for a
>>> serial bus, but the custom is to use the one sample / pixel formats on the
>>> serial busses.
>>>
>>  Should MEDIA_BUS_FMT_BGR888_1X24 be something like
>> MEDIA_BUS_FMT_BGR888_3X8 for parallel output bus ?
> 
> Good point. Yes.
> 
> Could you add that format to
> Documentation/media/uapi/v4l/subdev-formats.rst, please, in a separate
> patch?
> 
 I also need to add it to include/uapi/linux/media-bus-format.h I
suppose ?
 I was also wondering if I should add MEDIA_BUS_FMT_BGR888_3X8_BE and
MEDIA_BUS_FMT_BGR888_3X8_LE instead ?

 So if you are ok with the above I will add MEDIA_BUS_FMT_BGR888_3X8 to
subdev-formats.rs and media-bus-format.h as a first parch of my serie.

Mickael

  reply	other threads:[~2019-04-08  6:18 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12  6:44 [PATCH v1 0/3] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-12  6:44 ` [PATCH v1 1/3] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-16 21:46   ` Sakari Ailus
2019-03-18  8:28     ` Mickael GUENE
2019-03-18  8:48       ` Sakari Ailus
2019-03-18  9:08         ` Mickael GUENE
2019-03-12  6:44 ` [PATCH v1 2/3] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
2019-03-16 22:14   ` Sakari Ailus
2019-03-18  9:57     ` Mickael GUENE
2019-03-25 11:17       ` Sakari Ailus
2019-03-25 12:14         ` Mickael GUENE
2019-03-26 11:37           ` Sakari Ailus
2019-03-26 12:07             ` Mickael GUENE
2019-03-12  6:44 ` [PATCH v1 3/3] media: MAINTAINERS: add entry for STMicroelectronics MIPID02 media driver Mickael Guene
2019-03-16 21:47   ` Sakari Ailus
2019-03-18 10:01     ` Mickael GUENE
2019-03-25  7:55 ` [PATCH v2 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-25  7:55   ` [PATCH v2 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-25  7:55   ` [PATCH v2 2/2] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
2019-03-25 11:44     ` Sakari Ailus
2019-03-25 12:22       ` Mickael GUENE
2019-03-26 11:34         ` Sakari Ailus
2019-03-26 12:32           ` Mickael GUENE
2019-03-26 10:03 ` [PATCH v3 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-26 10:03   ` [PATCH v3 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-26 12:17     ` Sakari Ailus
2019-03-26 13:40       ` Mickael GUENE
2019-03-26 13:44         ` Sakari Ailus
2019-03-26 10:03   ` [PATCH v3 2/2] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
2019-03-26 11:33     ` Sakari Ailus
2019-03-26 12:57       ` Mickael GUENE
2019-03-26 13:54         ` Sakari Ailus
2019-03-26 14:12           ` Mickael GUENE
2019-03-26 14:14             ` Sakari Ailus
2019-03-26 14:36       ` Mickael GUENE
2019-04-06 11:01         ` Sakari Ailus
2019-04-08  6:17           ` Mickael GUENE [this message]
2019-04-08  9:21             ` Sakari Ailus
2019-03-27  9:55 ` [PATCH v4 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-27  9:55   ` [PATCH v4 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-28 17:43     ` Rob Herring
2019-04-06 10:35     ` Sakari Ailus
2019-04-06 10:38       ` Sakari Ailus
2019-04-08  6:20         ` Mickael GUENE
2019-03-27  9:55   ` [PATCH v4 2/2] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
     [not found]     ` <20190406105606.rciacao5d4hljbbu@kekkonen.localdomain>
2019-04-08  8:20       ` Mickael GUENE
2019-04-08  9:17         ` Sakari Ailus

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=1c7e0b8a-7441-57eb-38c0-e951917637c6@st.com \
    --to=mickael.guene@st.com \
    --cc=akinobu.mita@gmail.com \
    --cc=ben.kao@intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hugues.fruchet@st.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo+renesas@jmondi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=matt.ranostay@konsulko.com \
    --cc=mchehab@kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=petrcvekcz@gmail.com \
    --cc=ricardo@ribalda.com \
    --cc=rui.silva@linaro.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tian.shu.qiu@intel.com \
    --cc=todor.tomov@linaro.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).