From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Petr Mladek" <pmladek@suse.com>,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
hverkuil@xs4all.nl,
"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
laurent.pinchart@ideasonboard.com,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
linux-media@vger.kernel.org,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs
Date: Thu, 2 Apr 2020 15:53:23 +0200 [thread overview]
Message-ID: <20200402155323.6866b5c9@coco.lan> (raw)
In-Reply-To: <87eet6mgk7.fsf@intel.com>
Em Thu, 02 Apr 2020 11:34:48 +0300
Jani Nikula <jani.nikula@linux.intel.com> escreveu:
> On Wed, 01 Apr 2020, Sakari Ailus <sakari.ailus@linux.intel.com> wrote:
> > Add a printk modifier %ppf (for pixel format) for printing V4L2 and DRM
> > pixel formats denoted by 4ccs. The 4cc encoding is the same for both so
> > the same implementation can be used.
>
> I'm not going to take a strong stand in one way or the other regarding
> the patch at hand, but I do think at some point we have to draw a line
> what should be included in printk formats. Arguably they should be
> reserved to things that are generally useful across large parts of the
> kernel, right?
>
> I think the more specialized you get, the more you should think about
> just using the plain old %s, and your own helpers.
As I suggested it, from my side, I'd like to have it inside printk :-)
There is a subset of formats that are subsystem-specific anyway at
printk, like the network ones. We use extensively fourcc along the
media subsystem (and you probably also use fourcc at DRM). Even some input
devices nowadays may be using V4L2 core (some multi-sensor touching
devices), with depends on it.
So, those fourcc codes are pretty common. Having it at the printk
infra makes a lot easier for people to use them.
> Because frankly, the
> kernel printk specifiers also start getting more than a little obscure.
I liked one of the suggestions of using "%p4cc" (or maybe something
similar, if having a number there is a problem, like "%pAcc" or "%pfcc")
for this printk. This would be very easy for people to identify and
remember about its meaning.
> Or could we conceive of a way to make this locally extensible yet safe,
> letting callers use something like %{foo}, as well as providing a
> locally relevant function to do the conversion?
That's something that it makes sense to be implemented in the future,
for things that would be self-contained inside an specific subsystem.
Thanks,
Mauro
next prev parent reply other threads:[~2020-04-02 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 14:05 [PATCH 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs Sakari Ailus
2020-04-01 14:13 ` Hans Verkuil
2020-04-01 15:13 ` Andy Shevchenko
2020-04-02 7:32 ` Sakari Ailus
2020-04-06 7:37 ` Pekka Paalanen
2020-04-02 7:18 ` Sakari Ailus
2020-04-02 8:34 ` Jani Nikula
2020-04-02 8:52 ` Sakari Ailus
2020-04-02 13:53 ` Mauro Carvalho Chehab [this message]
2020-04-02 23:28 ` Joe Perches
2020-04-02 23:26 ` Joe Perches
2020-04-03 6:37 ` Jani Nikula
2020-04-03 13:11 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2020-04-27 14:50 Sakari Ailus
2020-04-27 14:54 ` 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=20200402155323.6866b5c9@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=jani.nikula@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox