public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org, prabhakar.csengg@gmail.com
Subject: Re: [PATCH 2/3] smiapp: Read link-frequencies property from the endpoint node
Date: Wed, 11 Mar 2015 20:41:28 +0200	[thread overview]
Message-ID: <3221454.r85COdfNJV@avalon> (raw)
In-Reply-To: <1425950282-30548-3-git-send-email-sakari.ailus@iki.fi>

Hi Sakari,

Thank you for the patch.

On Tuesday 10 March 2015 03:18:01 Sakari Ailus wrote:
> The documentation stated that the link-frequencies property belongs to the
> endpoint node, not to the device's of_node. Fix this.
> 
> There are no DT board descriptions using the driver yet, so a fix in the
> driver is sufficient.
> 
> Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi>

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>  drivers/media/i2c/smiapp/smiapp-core.c |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
> b/drivers/media/i2c/smiapp/smiapp-core.c index 565a00c..ecae76b 100644
> --- a/drivers/media/i2c/smiapp/smiapp-core.c
> +++ b/drivers/media/i2c/smiapp/smiapp-core.c
> @@ -3022,8 +3022,7 @@ static struct smiapp_platform_data
> *smiapp_get_pdata(struct device *dev) dev_dbg(dev, "reset %d, nvm %d, clk
> %d, csi %d\n", pdata->xshutdown, pdata->nvm_size, pdata->ext_clk,
> pdata->csi_signalling_mode);
> 
> -	rval = of_get_property(
> -		dev->of_node, "link-frequencies", &asize) ? 0 : -ENOENT;
> +	rval = of_get_property(ep, "link-frequencies", &asize) ? 0 : -ENOENT;
>  	if (rval) {
>  		dev_warn(dev, "can't get link-frequencies array size\n");
>  		goto out_err;
> @@ -3037,7 +3036,7 @@ static struct smiapp_platform_data
> *smiapp_get_pdata(struct device *dev)
> 
>  	asize /= sizeof(*pdata->op_sys_clock);
>  	rval = of_property_read_u64_array(
> -		dev->of_node, "link-frequencies", pdata->op_sys_clock, asize);
> +		ep, "link-frequencies", pdata->op_sys_clock, asize);
>  	if (rval) {
>  		dev_warn(dev, "can't get link-frequencies\n");
>  		goto out_err;

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2015-03-11 18:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10  1:17 [PATCH 0/3] Add link-frequencies to struct v4l2_of_endpoint Sakari Ailus
2015-03-10  1:18 ` [PATCH 1/3] smiapp: Clean up smiapp_get_pdata() Sakari Ailus
2015-03-11 18:40   ` Laurent Pinchart
2015-03-11 22:24   ` Lad, Prabhakar
2015-03-11 22:38     ` Lad, Prabhakar
2015-03-10  1:18 ` [PATCH 2/3] smiapp: Read link-frequencies property from the endpoint node Sakari Ailus
2015-03-11 18:41   ` Laurent Pinchart [this message]
2015-03-11 22:25   ` Lad, Prabhakar
2015-03-11 22:38     ` Lad, Prabhakar
2015-03-10  1:18 ` [PATCH 3/3] v4l: of: Add link-frequencies array to struct v4l2_of_endpoint Sakari Ailus
2015-03-11 22:22   ` Lad, Prabhakar
2015-03-12 20:49     ` [PATCH v1.1 " Sakari Ailus
2015-03-15 17:15       ` Guennadi Liakhovetski
2015-03-15 23:16         ` 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=3221454.r85COdfNJV@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=prabhakar.csengg@gmail.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