From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: linux-clk@vger.kernel.org, Marek Vasut <marex@denx.de>
Cc: Marek Vasut <marex@denx.de>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v4] clk: rs9: Fix I2C accessors
Date: Fri, 30 Sep 2022 08:25:23 +0200 [thread overview]
Message-ID: <12086721.O9o76ZdvQC@steina-w> (raw)
In-Reply-To: <20220929195521.284497-1-marex@denx.de>
Hi Marek,
Am Donnerstag, 29. September 2022, 21:55:21 CEST schrieb Marek Vasut:
> Add custom I2C accessors to this driver, since the regular I2C regmap ones
> do not generate the exact I2C transfers required by the chip. On I2C write,
> it is mandatory to send transfer length first, on read the chip returns the
> transfer length in first byte. Instead of always reading back 8 bytes, which
> is the default and also the size of the entire register file, set BCP
> register to 1 to read out 1 byte which is less wasteful.
>
> Fixes: 892e0ddea1aa ("clk: rs9: Add Renesas 9-series PCIe clock generator
> driver") Reported-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> V2: Fix endianness handling in rs9_regmap_i2c_read() i2c_transfer
> V3: - Disable regcache, the driver does a couple of I2C writes on boot
> and that is all, so it only adds complexity
> - Set regmap max_register to RS9_REG_BCP which is the correct one
> V4: - Do not use I2C_M_RECV_LEN due to overhead, it requires buffer 4
> times the size of this devices' register file, just read two bytes
> via I2C
> ---
> Cc: Alexander Stein <alexander.stein@ew.tq-group.com>
> Cc: Michael Turquette <mturquette@baylibre.com>
> Cc: Stephen Boyd <sboyd@kernel.org>
> ---
> drivers/clk/clk-renesas-pcie.c | 65 ++++++++++++++++++++++++++++++++--
> 1 file changed, 62 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/clk/clk-renesas-pcie.c b/drivers/clk/clk-renesas-pcie.c
> index 4f5df1fc74b46..e6247141d0c05 100644
> --- a/drivers/clk/clk-renesas-pcie.c
> +++ b/drivers/clk/clk-renesas-pcie.c
> @@ -90,13 +90,66 @@ static const struct regmap_access_table
> rs9_writeable_table = { .n_yes_ranges = ARRAY_SIZE(rs9_writeable_ranges),
> };
>
> +static int rs9_regmap_i2c_write(void *context,
> + unsigned int reg, unsigned int
val)
> +{
> + struct i2c_client *i2c = context;
> + const u8 data[3] = { reg, 1, val };
> + const int count = ARRAY_SIZE(data);
> + int ret;
> +
> + ret = i2c_master_send(i2c, data, count);
> + if (ret == count)
> + return 0;
> + else if (ret < 0)
> + return ret;
> + else
> + return -EIO;
> +}
> +
> +static int rs9_regmap_i2c_read(void *context,
> + unsigned int reg, unsigned int *val)
> +{
> + struct i2c_client *i2c = context;
> + struct i2c_msg xfer[2];
> + u8 txdata = reg;
> + u8 rxdata[2];
> + int ret;
> +
> + xfer[0].addr = i2c->addr;
> + xfer[0].flags = 0;
> + xfer[0].len = 1;
> + xfer[0].buf = (void *)&txdata;
> +
> + xfer[1].addr = i2c->addr;
> + xfer[1].flags = I2C_M_RD;
> + xfer[1].len = 2;
> + xfer[1].buf = (void *)rxdata;
> +
> + ret = i2c_transfer(i2c->adapter, xfer, 2);
> + if (ret < 0)
> + return ret;
> + if (ret != 2)
> + return -EIO;
> +
> + /*
> + * Byte 0 is transfer length, which is always 1 due
> + * to BCP register programming to 1 in rs9_probe(),
> + * ignore it and use data from Byte 1.
> + */
This comments only holds true until cache is enabled again. Cache is
initialized by from reading registers using this function before BCP is set :)
Anyway, that's good for now:
Reviewed-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> + *val = rxdata[1];
> + return 0;
> +}
> +
> static const struct regmap_config rs9_regmap_config = {
> .reg_bits = 8,
> .val_bits = 8,
> - .cache_type = REGCACHE_FLAT,
> - .max_register = 0x8,
> + .cache_type = REGCACHE_NONE,
> + .max_register = RS9_REG_BCP,
> .rd_table = &rs9_readable_table,
> .wr_table = &rs9_writeable_table,
> + .reg_write = rs9_regmap_i2c_write,
> + .reg_read = rs9_regmap_i2c_read,
> };
>
> static int rs9_get_output_config(struct rs9_driver_data *rs9, int idx)
> @@ -242,11 +295,17 @@ static int rs9_probe(struct i2c_client *client)
> return ret;
> }
>
> - rs9->regmap = devm_regmap_init_i2c(client, &rs9_regmap_config);
> + rs9->regmap = devm_regmap_init(&client->dev, NULL,
> + client,
&rs9_regmap_config);
> if (IS_ERR(rs9->regmap))
> return dev_err_probe(&client->dev, PTR_ERR(rs9->regmap),
> "Failed to allocate register
map\n");
>
> + /* Always read back 1 Byte via I2C */
> + ret = regmap_write(rs9->regmap, RS9_REG_BCP, 1);
> + if (ret < 0)
> + return ret;
> +
> /* Register clock */
> for (i = 0; i < rs9->chip_info->num_clks; i++) {
> snprintf(name, 5, "DIF%d", i);
next prev parent reply other threads:[~2022-09-30 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 19:55 [PATCH v4] clk: rs9: Fix I2C accessors Marek Vasut
2022-09-30 6:25 ` Alexander Stein [this message]
2022-10-17 21:06 ` Stephen Boyd
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=12086721.O9o76ZdvQC@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=linux-clk@vger.kernel.org \
--cc=marex@denx.de \
--cc=mturquette@baylibre.com \
--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