From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Marek Vasut <marex@denx.de>
Cc: linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] clk: rs9: Check for vendor/device ID
Date: Wed, 04 Jan 2023 11:27:26 +0100 [thread overview]
Message-ID: <3826066.fW5hKsROvD@steina-w> (raw)
In-Reply-To: <2ba4e002-9f27-2e36-2bd2-8753c455b21f@denx.de>
Am Dienstag, 3. Januar 2023, 15:28:16 CET schrieb Marek Vasut:
> On 1/3/23 13:31, Alexander Stein wrote:
> > This is in preparation to support additional devices which have different
> > IDs as well as a slightly different register layout.
> >
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> >
> > drivers/clk/clk-renesas-pcie.c | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
> >
> > diff --git a/drivers/clk/clk-renesas-pcie.c
> > b/drivers/clk/clk-renesas-pcie.c index e6247141d0c0..0076ed8f11b0 100644
> > --- a/drivers/clk/clk-renesas-pcie.c
> > +++ b/drivers/clk/clk-renesas-pcie.c
> > @@ -45,6 +45,13 @@
> >
> > #define RS9_REG_DID 0x6
> > #define RS9_REG_BCP 0x7
> >
> > +#define RS9_REG_VID_IDT 0x01
> > +
> > +#define RS9_REG_DID_TYPE_FGV (0x0 <<
RS9_REG_DID_TYPE_SHIFT)
> > +#define RS9_REG_DID_TYPE_DBV (0x1 <<
RS9_REG_DID_TYPE_SHIFT)
> > +#define RS9_REG_DID_TYPE_DMV (0x2 <<
RS9_REG_DID_TYPE_SHIFT)
>
> I'm not entirely sure whether this shouldn't be using the BIT() macro,
> what do you think ?
As Geert already pointed out these are not just one-bit values.
> > +#define RS9_REG_DID_TYPE_SHIFT 0x6
> > +
> >
> > /* Supported Renesas 9-series models. */
> > enum rs9_model {
> >
> > RENESAS_9FGV0241,
> >
> > @@ -54,6 +61,7 @@ enum rs9_model {
> >
> > struct rs9_chip_info {
> >
> > const enum rs9_model model;
> > unsigned int num_clks;
> >
> > + u8 did;
>
> Should this be const (and also the num_clks) ?
Does this make a difference? chip_info in rs9_driver_data is already const, so
you can't write into it anyway.
> > };
> >
> > struct rs9_driver_data {
> >
> > @@ -270,6 +278,7 @@ static int rs9_probe(struct i2c_client *client)
> >
> > {
> >
> > unsigned char name[5] = "DIF0";
> > struct rs9_driver_data *rs9;
> >
> > + unsigned int vid, did;
> >
> > struct clk_hw *hw;
> > int i, ret;
> >
> > @@ -306,6 +315,20 @@ static int rs9_probe(struct i2c_client *client)
> >
> > if (ret < 0)
> >
> > return ret;
> >
> > + ret = regmap_read(rs9->regmap, RS9_REG_VID, &vid);
> > + if (ret < 0)
> > + return ret;
>
> Newline here.
Okay, will do.
> > + ret = regmap_read(rs9->regmap, RS9_REG_DID, &did);
> > + if (ret < 0)
> > + return ret;
> > +
> > + if ((vid != RS9_REG_VID_IDT) || (did != rs9->chip_info->did)) {
>
> Drop the unnecessary inner () parenthesis .
Okay, will remove them.
> > + dev_err(&client->dev,
>
> return dev_err_probe() might work better here ?
How? This error branch always returns -ENODEV, so no deferred probing will
occur at all.
Best regards,
Alexander
> > + "Incorrect VID/DID: %#02x, %#02x. Expected
%#02x, %#02x\n",
> > + vid, did, RS9_REG_VID_IDT, rs9->chip_info->did);
> > + return -ENODEV;
> > + }
>
> [...]
next prev parent reply other threads:[~2023-01-04 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:31 [PATCH 1/4] clk: rs9: Check for vendor/device ID Alexander Stein
2023-01-03 12:31 ` [PATCH 2/4] dt-bindings: clk: rs9: Add bindings for 9FGV0441 Alexander Stein
2023-01-03 13:25 ` Krzysztof Kozlowski
2023-01-03 13:49 ` Alexander Stein
2023-01-03 12:31 ` [PATCH 3/4] clk: rs9: Support device specific dif bit calculation Alexander Stein
2023-01-03 14:31 ` Marek Vasut
2023-01-04 10:32 ` Alexander Stein
2023-01-04 14:34 ` Marek Vasut
2023-01-03 12:31 ` [PATCH 4/4] clk: rs9: Add support for 9FGV0441 Alexander Stein
2023-01-03 14:28 ` [PATCH 1/4] clk: rs9: Check for vendor/device ID Marek Vasut
2023-01-03 16:08 ` Geert Uytterhoeven
2023-01-04 10:26 ` Alexander Stein
2023-01-04 10:27 ` Alexander Stein [this message]
2023-01-04 14:36 ` Marek Vasut
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=3826066.fW5hKsROvD@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marex@denx.de \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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