From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] v4l: of: check for unique lanes in data-lanes and clock-lanes
Date: Sat, 28 Jan 2017 18:26:24 +0200 [thread overview]
Message-ID: <1773458.Cvt8mFyy2S@avalon> (raw)
In-Reply-To: <20170126131259.5621-1-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
Thank you for the patch.
On Thursday 26 Jan 2017 14:12:59 Niklas Söderlund wrote:
> All lines in data-lanes and clock-lanes properties must be unique.
> Instead of drivers checking for this add it to the generic parser.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> drivers/media/v4l2-core/v4l2-of.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/v4l2-core/v4l2-of.c
> b/drivers/media/v4l2-core/v4l2-of.c index 93b33681776c..1042db6bb996 100644
> --- a/drivers/media/v4l2-core/v4l2-of.c
> +++ b/drivers/media/v4l2-core/v4l2-of.c
> @@ -32,12 +32,19 @@ static int v4l2_of_parse_csi_bus(const struct
> device_node *node, prop = of_find_property(node, "data-lanes", NULL);
> if (prop) {
> const __be32 *lane = NULL;
> - unsigned int i;
> + unsigned int i, n;
>
> for (i = 0; i < ARRAY_SIZE(bus->data_lanes); i++) {
> lane = of_prop_next_u32(prop, lane, &v);
> if (!lane)
> break;
> + for (n = 0; n < i; n++) {
> + if (bus->data_lanes[n] == v) {
> + pr_warn("%s: duplicated lane %u in
data-lanes\n",
> + node->full_name, v);
> + return -EINVAL;
> + }
If you used a bitmask to store the already used lanes you could avoid the
nested loops.
Apart from that,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> + }
> bus->data_lanes[i] = v;
> }
> bus->num_data_lanes = i;
> @@ -63,6 +70,15 @@ static int v4l2_of_parse_csi_bus(const struct device_node
> *node, }
>
> if (!of_property_read_u32(node, "clock-lanes", &v)) {
> + unsigned int n;
> +
> + for (n = 0; n < bus->num_data_lanes; n++) {
> + if (bus->data_lanes[n] == v) {
> + pr_warn("%s: duplicated lane %u in clock-
lanes\n",
> + node->full_name, v);
> + return -EINVAL;
> + }
> + }
> bus->clock_lane = v;
> have_clk_lane = true;
> }
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2017-01-28 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 13:12 [PATCH] v4l: of: check for unique lanes in data-lanes and clock-lanes Niklas Söderlund
2017-01-26 13:31 ` Geert Uytterhoeven
2017-01-27 9:31 ` Sakari Ailus
2017-01-28 16:26 ` Laurent Pinchart [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=1773458.Cvt8mFyy2S@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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