From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/7] nvmem: imx-ocotp: Pass parameters via a struct
Date: Wed, 11 Oct 2017 17:28:13 +0200 [thread overview]
Message-ID: <1507735693.22082.8.camel@pengutronix.de> (raw)
In-Reply-To: <1507558312-20580-3-git-send-email-pure.logic@nexus-software.ie>
Hi Bryan,
On Mon, 2017-10-09 at 15:11 +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..7798571 100644
> --- a/drivers/nvmem/imx-ocotp.c
> +++ b/drivers/nvmem/imx-ocotp.c
> @@ -53,11 +53,15 @@
>
> static DEFINE_MUTEX(ocotp_mutex);
>
> +struct ocotp_params {
> + unsigned int nregs;
> +};
> +
> struct ocotp_priv {
> struct device *dev;
> struct clk *clk;
> void __iomem *base;
> - unsigned int nregs;
> + const struct ocotp_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 ocotp_params params[] = {
> + { .nregs = 128 },
> + { .nregs = 64 },
> + { .nregs = 128 },
> + { .nregs = 128 },
> + { .nregs = 64 },
> +};
Could you either add an enum for the indices into this array or split
the array into separate named structs?
I find it already hard to see which parameter belongs to which
compatible, and this will grow worse with increasing number of entries
in the parameter set.
For example,
static const struct ocotp_params imx6q_params = {
.nregs = 128,
};
static const struct ocotp_params imx6sl_params = {
.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", .data = ¶ms[0] },
> + { .compatible = "fsl,imx6sl-ocotp", .data = ¶ms[1] },
> + { .compatible = "fsl,imx6sx-ocotp", .data = ¶ms[2] },
> + { .compatible = "fsl,imx6ul-ocotp", .data = ¶ms[3] },
> + { .compatible = "fsl,imx7d-ocotp", .data = ¶ms[4] },
{ .compatible = "fsl,imx6q-ocotp", .data = &imx6q_params },
{ .compatible = "fsl,imx6sl-ocotp", .data = &imx6sl_params },
...
Apart from that,
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
> { },
> };
> 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 = of_device_get_match_data(&pdev->dev);
> + imx_ocotp_nvmem_config.size = 4 * priv->params->nregs;
> 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-11 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 14:11 [PATCH v3 0/7] Fix i.MX7D OCOTP write support Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 1/7] nvmem: imx-ocotp: Restrict OTP write to IMX6 processors Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 2/7] nvmem: imx-ocotp: Pass parameters via a struct Bryan O'Donoghue
2017-10-11 15:28 ` Philipp Zabel [this message]
2017-10-09 14:11 ` [PATCH v3 3/7] nvmem: imx-ocotp: Add support for banked OTP addressing Bryan O'Donoghue
2017-10-11 15:32 ` Philipp Zabel
2017-10-11 15:54 ` Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 4/7] nvmem: imx-ocotp: Move i.MX6 write clock setup to dedicated function Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 5/7] nvmem: imx-ocotp: Add i.MX7D timing write clock setup support Bryan O'Donoghue
2017-10-11 16:03 ` Philipp Zabel
2017-10-11 16:22 ` Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 6/7] nvmem: imx-ocotp: Enable i.MX7D OTP write support Bryan O'Donoghue
2017-10-09 14:11 ` [PATCH v3 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=1507735693.22082.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).