From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Petr Mladek <pmladek@suse.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Joe Perches <joe@perches.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs
Date: Sat, 4 Apr 2020 03:21:47 +0300 [thread overview]
Message-ID: <20200404002147.GG9690@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200404001425.GC4394@kekkonen.localdomain>
Hi Sakari,
On Sat, Apr 04, 2020 at 03:14:25AM +0300, Sakari Ailus wrote:
> On Fri, Apr 03, 2020 at 09:32:42PM +0300, Andy Shevchenko wrote:
> > On Fri, Apr 3, 2020 at 8:54 PM Joe Perches <joe@perches.com> wrote:
> > > On Fri, 2020-04-03 at 19:32 +0200, Mauro Carvalho Chehab wrote:
> > > > Em Fri, 03 Apr 2020 09:56:42 -0700
> > > > Joe Perches <joe@perches.com> escreveu:
> >
> > > It _might_ be useful to use a CONFIG_MEDIA_SUPPORT guard
> > > in lib/vsprintf for this.
> >
> > No need. FourCC, if Sakari makes it more generic, can be used for
> > other purposes, e.g. printing component names from the chips (not
> > related to media at all).
>
> Could you elaborate?
>
> This could be already used on DRM, presumably, and that does not depend on
> CONFIG_MEDIA_SUPPORT. I don't know how much there would be a need for that,
> though, but this remains a possibility.
/**
* drm_get_format_name - fill a string with a drm fourcc format's name
* @format: format to compute name of
* @buf: caller-supplied buffer
*/
const char *drm_get_format_name(uint32_t format, struct drm_format_name_buf *buf)
{
snprintf(buf->str, sizeof(buf->str),
"%c%c%c%c %s-endian (0x%08x)",
printable_char(format & 0xff),
printable_char((format >> 8) & 0xff),
printable_char((format >> 16) & 0xff),
printable_char((format >> 24) & 0x7f),
format & DRM_FORMAT_BIG_ENDIAN ? "big" : "little",
format);
return buf->str;
}
EXPORT_SYMBOL(drm_get_format_name);
I'm not advocating for one approach or the other in this case, but we
should standardize 4CC printing between the two subsystems.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Joe Perches <joe@perches.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Petr Mladek <pmladek@suse.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs
Date: Sat, 4 Apr 2020 03:21:47 +0300 [thread overview]
Message-ID: <20200404002147.GG9690@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200404001425.GC4394@kekkonen.localdomain>
Hi Sakari,
On Sat, Apr 04, 2020 at 03:14:25AM +0300, Sakari Ailus wrote:
> On Fri, Apr 03, 2020 at 09:32:42PM +0300, Andy Shevchenko wrote:
> > On Fri, Apr 3, 2020 at 8:54 PM Joe Perches <joe@perches.com> wrote:
> > > On Fri, 2020-04-03 at 19:32 +0200, Mauro Carvalho Chehab wrote:
> > > > Em Fri, 03 Apr 2020 09:56:42 -0700
> > > > Joe Perches <joe@perches.com> escreveu:
> >
> > > It _might_ be useful to use a CONFIG_MEDIA_SUPPORT guard
> > > in lib/vsprintf for this.
> >
> > No need. FourCC, if Sakari makes it more generic, can be used for
> > other purposes, e.g. printing component names from the chips (not
> > related to media at all).
>
> Could you elaborate?
>
> This could be already used on DRM, presumably, and that does not depend on
> CONFIG_MEDIA_SUPPORT. I don't know how much there would be a need for that,
> though, but this remains a possibility.
/**
* drm_get_format_name - fill a string with a drm fourcc format's name
* @format: format to compute name of
* @buf: caller-supplied buffer
*/
const char *drm_get_format_name(uint32_t format, struct drm_format_name_buf *buf)
{
snprintf(buf->str, sizeof(buf->str),
"%c%c%c%c %s-endian (0x%08x)",
printable_char(format & 0xff),
printable_char((format >> 8) & 0xff),
printable_char((format >> 16) & 0xff),
printable_char((format >> 24) & 0x7f),
format & DRM_FORMAT_BIG_ENDIAN ? "big" : "little",
format);
return buf->str;
}
EXPORT_SYMBOL(drm_get_format_name);
I'm not advocating for one approach or the other in this case, but we
should standardize 4CC printing between the two subsystems.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2020-04-04 0:22 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 9:11 [PATCH v2 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs Sakari Ailus
2020-04-03 9:11 ` Sakari Ailus
2020-04-03 9:31 ` Andy Shevchenko
2020-04-03 9:31 ` Andy Shevchenko
2020-04-03 9:39 ` Sakari Ailus
2020-04-03 9:39 ` Sakari Ailus
2020-04-03 9:54 ` Andy Shevchenko
2020-04-03 9:54 ` Andy Shevchenko
2020-04-03 10:10 ` Sakari Ailus
2020-04-03 10:10 ` Sakari Ailus
2020-04-03 10:24 ` Laurent Pinchart
2020-04-03 10:24 ` Laurent Pinchart
2020-04-03 10:47 ` Sakari Ailus
2020-04-03 10:47 ` Sakari Ailus
2020-04-03 11:19 ` Mauro Carvalho Chehab
2020-04-03 11:19 ` Mauro Carvalho Chehab
2020-04-03 11:54 ` Andy Shevchenko
2020-04-03 11:54 ` Andy Shevchenko
2020-04-03 18:38 ` Joe Perches
2020-04-03 18:38 ` Joe Perches
2020-04-03 23:36 ` Sakari Ailus
2020-04-03 23:36 ` Sakari Ailus
2020-04-03 23:55 ` Joe Perches
2020-04-03 23:55 ` Joe Perches
2020-04-03 12:10 ` Rasmus Villemoes
2020-04-03 12:10 ` Rasmus Villemoes
2020-04-03 14:22 ` Mauro Carvalho Chehab
2020-04-03 14:22 ` Mauro Carvalho Chehab
2020-04-03 16:56 ` Joe Perches
2020-04-03 16:56 ` Joe Perches
2020-04-03 17:32 ` Mauro Carvalho Chehab
2020-04-03 17:32 ` Mauro Carvalho Chehab
2020-04-03 17:48 ` Joe Perches
2020-04-03 17:48 ` Joe Perches
2020-04-03 18:32 ` Andy Shevchenko
2020-04-03 18:32 ` Andy Shevchenko
2020-04-04 0:14 ` Sakari Ailus
2020-04-04 0:14 ` Sakari Ailus
2020-04-04 0:21 ` Laurent Pinchart [this message]
2020-04-04 0:21 ` Laurent Pinchart
2020-04-06 7:17 ` Sakari Ailus
2020-04-06 7:17 ` Sakari Ailus
2020-04-06 7:46 ` Mauro Carvalho Chehab
2020-04-06 7:46 ` Mauro Carvalho Chehab
2020-04-06 10:44 ` Andy Shevchenko
2020-04-06 10:44 ` Andy Shevchenko
2020-04-06 13:01 ` Joe Perches
2020-04-06 13:01 ` Joe Perches
2020-04-06 7:28 ` Sakari Ailus
2020-04-06 7:28 ` Sakari Ailus
2020-04-06 7:37 ` Jani Nikula
2020-04-06 7:37 ` Jani Nikula
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=20200404002147.GG9690@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mchehab+huawei@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sergey.senozhatsky@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.