From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] [media] Add RGB444_1X12 and RGB565_1X16 media bus formats
Date: Sun, 16 Nov 2014 09:19:18 +0100 [thread overview]
Message-ID: <20141116091918.56b859e8@bbrezillon> (raw)
In-Reply-To: <546767FD.2080706@iki.fi>
On Sat, 15 Nov 2014 16:49:33 +0200
Sakari Ailus <sakari.ailus@iki.fi> wrote:
> Hi Boris,
>
> Boris Brezillon wrote:
> > Hi Sakari,
> >
> > On Fri, 14 Nov 2014 15:58:31 +0200
> > Sakari Ailus <sakari.ailus@iki.fi> wrote:
> >
> >> Hi Boris,
> >>
> >> On Fri, Nov 14, 2014 at 11:36:00AM +0100, Boris Brezillon wrote:
> ...
> >>> diff --git a/include/uapi/linux/media-bus-format.h b/include/uapi/linux/media-bus-format.h
> >>> index 23b4090..cc7b79e 100644
> >>> --- a/include/uapi/linux/media-bus-format.h
> >>> +++ b/include/uapi/linux/media-bus-format.h
> >>> @@ -33,7 +33,7 @@
> >>>
> >>> #define MEDIA_BUS_FMT_FIXED 0x0001
> >>>
> >>> -/* RGB - next is 0x100e */
> >>> +/* RGB - next is 0x1010 */
> >>> #define MEDIA_BUS_FMT_RGB444_2X8_PADHI_BE 0x1001
> >>> #define MEDIA_BUS_FMT_RGB444_2X8_PADHI_LE 0x1002
> >>> #define MEDIA_BUS_FMT_RGB555_2X8_PADHI_BE 0x1003
> >>> @@ -47,6 +47,8 @@
> >>> #define MEDIA_BUS_FMT_RGB888_2X12_BE 0x100b
> >>> #define MEDIA_BUS_FMT_RGB888_2X12_LE 0x100c
> >>> #define MEDIA_BUS_FMT_ARGB8888_1X32 0x100d
> >>> +#define MEDIA_BUS_FMT_RGB444_1X12 0x100e
> >>> +#define MEDIA_BUS_FMT_RGB565_1X16 0x100f
> >>
> >> I'd arrange these according to BPP and bits per sample, both in the header
> >> and documentation.
> >
> > I cannot keep both macro values and BPP/bits per sample in incrementing
> > order. Are you sure you prefer to order macros in BPP/bits per sample
> > order ?
>
> If you take a look elsewhere in the header, you'll notice that the
> ordering has preferred the BPP value (and other values with semantic
> significance) over the numeric value of the definition. I'd just prefer
> to keep it that way. This is also why the "next is" comments are there.
>
My bad, I only had a look at RGB formats.
I'll fix that.
Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2014-11-16 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 10:36 [PATCH] [media] Add RGB444_1X12 and RGB565_1X16 media bus formats Boris Brezillon
[not found] ` <1415961360-14898-1-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-11-14 13:58 ` Sakari Ailus
2014-11-14 15:04 ` Boris Brezillon
2014-11-15 14:49 ` Sakari Ailus
2014-11-16 8:19 ` Boris Brezillon [this message]
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=20141116091918.56b859e8@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=sakari.ailus@iki.fi \
/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).