From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-media@vger.kernel.org,
"Mauro Carvalho Chehab" <m.chehab@samsung.com>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Frank Schäfer" <fschaefer.oss@googlemail.com>,
"Hans Verkuil" <hans.verkuil@cisco.com>
Subject: Re: [PATCH 2/3] V4L2: add a v4l2-clk helper macro to produce an I2C device ID
Date: Wed, 28 Aug 2013 15:35:48 +0200 [thread overview]
Message-ID: <14364379.DScLfzIeAP@avalon> (raw)
In-Reply-To: <1377696508-3190-3-git-send-email-g.liakhovetski@gmx.de>
Hi Guennadi,
Thank you for the patch.
On Wednesday 28 August 2013 15:28:27 Guennadi Liakhovetski wrote:
> To obtain a clock reference consumers supply their device object to the
> V4L2 clock framework. The latter then uses the consumer device name to
> find a matching clock. For that to work V4L2 clock providers have to
> provide the same device name, when registering clocks. This patch adds
> a helper macro to generate a suitable device name for I2C devices.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> V4L2 clocks use device ID matching, which in case of I2C devices involves
> comparing a specially constructed from an I2C adapter number and a device
> address
Is this text placed below the SoB on purpose ?
> ---
> include/media/v4l2-clk.h | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/include/media/v4l2-clk.h b/include/media/v4l2-clk.h
> index a354a9d..0b36cc1 100644
> --- a/include/media/v4l2-clk.h
> +++ b/include/media/v4l2-clk.h
> @@ -65,4 +65,7 @@ static inline struct v4l2_clk
> *v4l2_clk_register_fixed(const char *dev_id, return
> __v4l2_clk_register_fixed(dev_id, id, rate, THIS_MODULE); }
>
> +#define v4l2_clk_name_i2c(name, size, adap, client) snprintf(name, size, \
> + "%d-%04x", adap, client)
> +
I would have made this a static inline but I have to confess I don't know why
:-)
> #endif
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-08-28 13:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 13:28 [PATCH 0/3] V4L2: fix em28xx ov2640 support Guennadi Liakhovetski
2013-08-28 13:28 ` [PATCH 1/3] V4L2: add v4l2-clock helpers to register and unregister a fixed-rate clock Guennadi Liakhovetski
2013-08-28 13:33 ` Laurent Pinchart
2013-08-28 14:49 ` Guennadi Liakhovetski
2013-08-28 13:28 ` [PATCH 2/3] V4L2: add a v4l2-clk helper macro to produce an I2C device ID Guennadi Liakhovetski
2013-08-28 13:35 ` Laurent Pinchart [this message]
2013-08-28 13:42 ` Guennadi Liakhovetski
2013-08-28 13:28 ` [PATCH 3/3] V4L2: em28xx: register a V4L2 clock source Guennadi Liakhovetski
2013-08-28 21:54 ` Sylwester Nawrocki
2013-09-02 18:40 ` [PATCH 0/3] V4L2: fix em28xx ov2640 support Frank Schäfer
2013-09-03 6:34 ` Guennadi Liakhovetski
2013-09-05 13:32 ` Guennadi Liakhovetski
2013-09-05 15:22 ` Frank Schäfer
2013-09-05 15:41 ` Mauro Carvalho Chehab
2013-09-05 15:57 ` Guennadi Liakhovetski
2013-09-09 17:27 ` Frank Schäfer
2013-09-09 17:30 ` Frank Schäfer
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=14364379.DScLfzIeAP@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=fschaefer.oss@googlemail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=s.nawrocki@samsung.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.