From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND][PATCH 2/7] nvmem: imx-ocotp: Pass parameters via a struct
Date: Thu, 05 Oct 2017 12:31:52 +0200 [thread overview]
Message-ID: <1507199512.8473.8.camel@pengutronix.de> (raw)
In-Reply-To: <1507155921-824-3-git-send-email-pure.logic@nexus-software.ie>
Hi Bryan,
a few small nitpicks below.
On Wed, 2017-10-04 at 23:25 +0100, Bryan O'Donoghue wrote:
> It will be useful in later patches to know the register access mode
> and bit-shift to apply to a given input offset.
>
> Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support")
>
> Signed-off-by: Bryan O'Donoghue <pure.logic@nexus-software.ie>
> ---
> ?drivers/nvmem/imx-ocotp.c | 32 ++++++++++++++++++++++----------
> ?1 file changed, 22 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/nvmem/imx-ocotp.c b/drivers/nvmem/imx-ocotp.c
> index 17d160f..fed76a4 100644
> --- a/drivers/nvmem/imx-ocotp.c
> +++ b/drivers/nvmem/imx-ocotp.c
> @@ -53,11 +53,15 @@
> ?
> ?static DEFINE_MUTEX(ocotp_mutex);
> ?
> +struct octp_params {
Should this struct be called "ocotp_params"?
> + unsigned int nregs;
> +};
> +
> ?struct ocotp_priv {
> ? struct device *dev;
> ? struct clk *clk;
> ? void __iomem *base;
> - unsigned int nregs;
> + struct octp_params *params;
> ? struct nvmem_config *config;
> ?};
> ?
> @@ -121,8 +125,8 @@ static int imx_ocotp_read(void *context, unsigned
> int offset,
> ? index = offset >> 2;
> ? count = bytes >> 2;
> ?
> - if (count > (priv->nregs - index))
> - count = priv->nregs - index;
> + if (count > (priv->params->nregs - index))
> + count = priv->params->nregs - index;
> ?
> ? mutex_lock(&ocotp_mutex);
> ?
> @@ -308,12 +312,20 @@ static struct nvmem_config
> imx_ocotp_nvmem_config = {
> ? .reg_write = imx_ocotp_write,
> ?};
> ?
> +static const struct octp_params params[] = {
> + { .nregs = 128},
Missing whitespace.
> + { .nregs = 64},
> + { .nregs = 128},
> + { .nregs = 128},
> + { .nregs = 64},
> +};
> +
> ?static const struct of_device_id imx_ocotp_dt_ids[] = {
> - { .compatible = "fsl,imx6q-ocotp",??(void *)128 },
> - { .compatible = "fsl,imx6sl-ocotp", (void *)64 },
> - { .compatible = "fsl,imx6sx-ocotp", (void *)128 },
> - { .compatible = "fsl,imx6ul-ocotp", (void *)128 },
> - { .compatible = "fsl,imx7d-ocotp", (void *)64 },
> + { .compatible = "fsl,imx6q-ocotp",??(void *)¶ms[0] },
The (void *) cast is superfluous with this change, I'd also add the
missing ".data =":
{ .compatible = "fsl,imx6q-ocotp",??.data = ¶ms[0] },
> + { .compatible = "fsl,imx6sl-ocotp", (void *)¶ms[1] },
> + { .compatible = "fsl,imx6sx-ocotp", (void *)¶ms[2] },
> + { .compatible = "fsl,imx6ul-ocotp", (void *)¶ms[3] },
> + { .compatible = "fsl,imx7d-ocotp", (void *)¶ms[4] },
> ? { },
> ?};
> ?MODULE_DEVICE_TABLE(of, imx_ocotp_dt_ids);
> @@ -342,8 +354,8 @@ static int imx_ocotp_probe(struct platform_device
> *pdev)
> ? return PTR_ERR(priv->clk);
> ?
> ? of_id = of_match_device(imx_ocotp_dt_ids, dev);
> - priv->nregs = (unsigned long)of_id->data;
> - imx_ocotp_nvmem_config.size = 4 * priv->nregs;
> + priv->params = (struct octp_params *)of_id->data;
> + imx_ocotp_nvmem_config.size = 4 * priv->params->nregs;
This would be a good opportunity to switch to of_device_get_match_data.
> ? imx_ocotp_nvmem_config.dev = dev;
> ? imx_ocotp_nvmem_config.priv = priv;
> ? priv->config = &imx_ocotp_nvmem_config;
regards
Philipp
next prev parent reply other threads:[~2017-10-05 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 22:25 [RESEND][PATCH 0/7] Fix i.MX7D OCOTP write support Bryan O'Donoghue
2017-10-04 22:25 ` [RESEND][PATCH 1/7] nvmem: imx-ocotp: Restrict OTP write to IMX6 processors Bryan O'Donoghue
2017-10-05 10:31 ` Philipp Zabel
2017-10-04 22:25 ` [RESEND][PATCH 2/7] nvmem: imx-ocotp: Pass parameters via a struct Bryan O'Donoghue
2017-10-05 10:31 ` Philipp Zabel [this message]
2017-10-04 22:25 ` [RESEND][PATCH 3/7] nvmem: imx-ocotp: Add support for banked OTP addressing Bryan O'Donoghue
2017-10-05 10:32 ` Philipp Zabel
2017-10-04 22:25 ` [RESEND][PATCH 4/7] nvmem: imx-ocotp: Move i.MX6 write clock setup to dedicated function Bryan O'Donoghue
2017-10-05 10:34 ` Philipp Zabel
2017-10-04 22:25 ` [RESEND][PATCH 5/7] nvmem: imx-ocotp: Add i.MX7D timing write clock setup support Bryan O'Donoghue
2017-10-05 10:52 ` Philipp Zabel
2017-10-05 13:00 ` Bryan O'Donoghue
2017-10-04 22:25 ` [RESEND][PATCH 6/7] nvmem: imx-ocotp: Enable i.MX7D OTP write support Bryan O'Donoghue
2017-10-04 22:25 ` [RESEND][PATCH 7/7] nvmem: imx-ocotp: Update module description Bryan O'Donoghue
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=1507199512.8473.8.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).