mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Ezequiel Garcia <ezequiel@collabora.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] media: i2c: ov5645: Switch to assigned-clock-rates
Date: Fri, 13 Mar 2020 01:02:53 +0200	[thread overview]
Message-ID: <20200312230253.GB30932@pendragon.ideasonboard.com> (raw)
In-Reply-To: <OSBPR01MB3590906C6121D1DFFF4ABF0DAAFD0@OSBPR01MB3590.jpnprd01.prod.outlook.com>

Hi Prabhakar,

On Thu, Mar 12, 2020 at 09:52:38PM +0000, Prabhakar Mahadev Lad wrote:
> On 12 March 2020 21:42, Geert Uytterhoeven wrote:
> > On Thu, Mar 12, 2020 at 10:13 PM Lad Prabhakar wrote:
> > > This patch switches to assigned-clock-rates for specifying the clock rate.
> > > The clk-conf.c internally handles setting the clock rate when
> > > assigned-clock-rates is passed.
> > >
> > > The driver now sets the clock frequency only if the deprecated
> > > property clock-frequency is defined instead assigned-clock-rates, this
> > > is to avoid breakage with existing DT binaries.
> > >
> > > Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> >
> > Thanks for your patch!
> >
> > > --- a/drivers/media/i2c/ov5645.c
> > > +++ b/drivers/media/i2c/ov5645.c
> > > @@ -1055,6 +1055,7 @@ static int ov5645_probe(struct i2c_client *client)
> > >         struct device_node *endpoint;
> > >         struct ov5645 *ov5645;
> > >         u8 chip_id_high, chip_id_low;
> > > +       bool set_clk = false;
> > >         unsigned int i;
> > >         u32 xclk_freq;
> > >         int ret;
> > > @@ -1094,10 +1095,17 @@ static int ov5645_probe(struct i2c_client
> > *client)
> > >                 return PTR_ERR(ov5645->xclk);
> > >         }
> > >
> > > -       ret = of_property_read_u32(dev->of_node, "clock-frequency",
> > &xclk_freq);
> > > +       ret = of_property_read_u32(dev->of_node, "assigned-clock-rates",
> > > +                                  &xclk_freq);
> > >         if (ret) {
> >
> > I think you can just leave out the above check...
> >
> > > -               dev_err(dev, "could not get xclk frequency\n");
> > > -               return ret;
> > > +               /* check if deprecated property clock-frequency is defined */
> > > +               ret = of_property_read_u32(dev->of_node, "clock-frequency",
> > > +                                          &xclk_freq);
> > > +               if (ret) {
> >
> > ... and ignore the absence of the deprecated property.
> >
> > > +                       dev_err(dev, "could not get xclk frequency\n");
> > > +                       return ret;
> > > +               }
> > > +               set_clk = true;
> >
> > I.e. just
> >
> >         /* check if deprecated property clock-frequency is defined */
> >         xclk_freq = 0;
> >         of_property_read_u32(dev->of_node, "clock-frequency", &xclk_freq);
> >         if (xclk_freq) {
> >                 ret = clk_set_rate(ov5645->xclk, xclk_freq);
> >                 if (ret) {
> >                         dev_err(dev, "could not set xclk frequency\n");
> >                         return ret;
> >                 }
> >         } else {
> >                 xclk_freq = clk_get_rate(ov5645->xclk, xclk_freq);
> >         }
> >
> I did think about it initially, but realized the clk_get_rate may vary platform to platform
> for example in G2E clk_get_rate() returns a frequency of 24242424 with
> assigned-clock-rates set to  24000000 and probe would fail due to a check for
> external clock must be 24MHz, with 1% tolerance.

Then you need to handle the tolerance in this driver :-)

> > >         }
> > >
> > >         /* external clock must be 24MHz, allow 1% tolerance */ @@
> > > -1107,10 +1115,12 @@ static int ov5645_probe(struct i2c_client *client)
> > >                 return -EINVAL;
> > >         }
> > >
> > > -       ret = clk_set_rate(ov5645->xclk, xclk_freq);
> > > -       if (ret) {
> > > -               dev_err(dev, "could not set xclk frequency\n");
> > > -               return ret;
> > > +       if (set_clk) {
> > > +               ret = clk_set_rate(ov5645->xclk, xclk_freq);
> > > +               if (ret) {
> > > +                       dev_err(dev, "could not set xclk frequency\n");
> > > +                       return ret;
> > > +               }
> > >
> > >         }
> > >
> > >         for (i = 0; i < OV5645_NUM_SUPPLIES; i++)

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2020-03-12 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 21:12 [PATCH v2 0/3] " Lad Prabhakar
2020-03-12 21:12 ` [PATCH v2 1/3] media: dt-bindings: media: i2c: " Lad Prabhakar
2020-03-12 21:12 ` [PATCH v2 2/3] media: i2c: ov5645: " Lad Prabhakar
2020-03-12 21:41   ` Geert Uytterhoeven
2020-03-12 21:52     ` Prabhakar Mahadev Lad
2020-03-12 23:02       ` Laurent Pinchart [this message]
2020-03-13  8:02         ` Prabhakar Mahadev Lad
2020-03-12 23:00   ` Laurent Pinchart
2020-03-12 21:12 ` [PATCH v2 3/3] ARM: dts: imx6qdl-wandboard: Switch to assigned-clock-rates for ov5645 node Lad Prabhakar

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=20200312230253.GB30932@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@collabora.com \
    --cc=festevam@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnguo@kernel.org \
    /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

all inboxes | Powered by JetHome®