From: Srinivas Kandagatla <srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Martin Blumenstingl
<martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org,
khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 3/4] nvmem: add a driver for the Amlogic Meson6/Meson8/Meson8b SoCs
Date: Mon, 2 Oct 2017 16:28:38 +0100 [thread overview]
Message-ID: <8f1f5a45-951c-7434-44d5-4ef2a61ec038@linaro.org> (raw)
In-Reply-To: <20171001125700.1520-4-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Minor comments!!
On 01/10/17 13:56, Martin Blumenstingl wrote:
> This adds a driver to access the efuse on Amlogic Meson6, Meson8 and
> Meson8b SoCs.
> These SoCs are accessing the efuse IP block directly through the
> registers in the "secbus" region. This makes it different from the Meson
> GX efuse driver which uses the "secure monitor" firmware to access the
> efuse.
>
> The efuse on Meson6 can only read one byte at a time, while the efuse on
> Meson8 and Meson8b always reads 4 bytes at a time. The new driver
> supports both, but due to lack of hardware Meson6 support was not tested.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
> ---
> drivers/nvmem/Kconfig | 10 ++
> drivers/nvmem/Makefile | 2 +
> drivers/nvmem/meson-mx-efuse.c | 272 +++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 284 insertions(+)
> create mode 100644 drivers/nvmem/meson-mx-efuse.c
>
> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> +
> +
> +static void meson_mx_efuse_mask_bits(struct meson_mx_efuse *efuse, u32 reg,
> + u32 mask, u32 set)
> +{
> + u32 data;
> +
> + data = readl(efuse->base + reg);
> + data &= ~mask;
> + data |= (set & mask);
> +
> + writel(data, efuse->base + reg);
> +}
> +
> +static int meson_mx_efuse_hw_enable(struct meson_mx_efuse *efuse)
> +{
> + int err;
> +
> + err = clk_prepare_enable(efuse->core_clk);
> + if (err)
> + return err;
> +
> + /* power up the efuse */
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_PD_ENABLE, 0);
> +
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL4,
> + MESON_MX_EFUSE_CNTL4_ENCRYPT_ENABLE, 0);
> +
> + return 0;
> +}
> +
> +static void meson_mx_efuse_hw_disable(struct meson_mx_efuse *efuse)
> +{
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_PD_ENABLE,
> + MESON_MX_EFUSE_CNTL1_PD_ENABLE);
> +
> + clk_disable_unprepare(efuse->core_clk);
> +}
> +
> +static int meson_mx_efuse_read_addr(struct meson_mx_efuse *efuse,
> + unsigned int addr, u32 *value)
> +{
> + int err;
> + u32 regval;
> +
> + /* write the address to read */
> + regval = FIELD_PREP(MESON_MX_EFUSE_CNTL1_BYTE_ADDR_MASK, addr);
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_BYTE_ADDR_MASK, regval);
> +
> + /* inform the hardware that we changed the address */
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_BYTE_ADDR_SET,
> + MESON_MX_EFUSE_CNTL1_BYTE_ADDR_SET);
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_BYTE_ADDR_SET, 0);
> +
> + /* start the read process */
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_AUTO_RD_START,
> + MESON_MX_EFUSE_CNTL1_AUTO_RD_START);
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_AUTO_RD_START, 0);
> +
> + /*
> + * perform a dummy read to ensure that the HW has the RD_BUSY bit set
> + * when polling for the status below.
> + */
> + readl(efuse->base + MESON_MX_EFUSE_CNTL1);
> +
> + err = readl_poll_timeout_atomic(efuse->base + MESON_MX_EFUSE_CNTL1,
> + regval,
> + (!(regval & MESON_MX_EFUSE_CNTL1_AUTO_RD_BUSY)),
> + 1, 1000);
> + if (err) {
> + dev_err(efuse->config.dev,
> + "Timeout while reading efuse address %u\n", addr);
> + return err;
> + }
> +
> + *value = readl(efuse->base + MESON_MX_EFUSE_CNTL2);
> +
> + return 0;
> +}
> +
> +static int meson_mx_efuse_read(void *context, unsigned int offset,
> + void *buf, size_t bytes)
> +{
> + struct meson_mx_efuse *efuse = context;
> + u32 tmp;
> + int err, i, addr;
> +
> + err = meson_mx_efuse_hw_enable(efuse);
> + if (err)
> + return err;
> +
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_AUTO_RD_ENABLE,
> + MESON_MX_EFUSE_CNTL1_AUTO_RD_ENABLE);
> +
> + for (i = offset; i < offset + bytes; i += efuse->config.word_size) {
> + addr = i / efuse->config.word_size;
> +
> + err = meson_mx_efuse_read_addr(efuse, addr, &tmp);
> + if (err)
> + break;
> +
> + memcpy(buf + i, &tmp, efuse->config.word_size);
> + }
> +
> + meson_mx_efuse_mask_bits(efuse, MESON_MX_EFUSE_CNTL1,
> + MESON_MX_EFUSE_CNTL1_AUTO_RD_ENABLE, 0);
> +
> + meson_mx_efuse_hw_disable(efuse);
> +
> + return err;
> +}
...
> +
> +static int meson_mx_efuse_probe(struct platform_device *pdev)
> +{
> + const struct meson_mx_efuse_platform_data *drvdata;
> + struct meson_mx_efuse *efuse;
> + struct resource *res;
> +
...
> +
> + efuse->core_clk = devm_clk_get(&pdev->dev, "core");
> + if (IS_ERR(efuse->core_clk)) {
> + dev_err(&pdev->dev, "Failed to get core clock\n");
> + return PTR_ERR(efuse->core_clk);
> + }
> +
> + efuse->nvmem = nvmem_register(&efuse->config);
> + if (IS_ERR(efuse->nvmem)) {
> + clk_unprepare(efuse->core_clk);
Do you need this???
> + return PTR_ERR(efuse->nvmem);
> + }
> +
> + platform_set_drvdata(pdev, efuse);
> +
> + return 0;
> +}
> +
> +static int meson_mx_efuse_remove(struct platform_device *pdev)
> +{
> + struct meson_mx_efuse *efuse = platform_get_drvdata(pdev);
> + int err;
> +
> + err = nvmem_unregister(efuse->nvmem);
> +
> + clk_unprepare(efuse->core_clk);
Do you need this disable here? AFAIU, this driver would never leave the
clk prepared unless we are in the middle of read.
> +
> + return err;
> +}
> +
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-02 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 12:56 [PATCH 0/4] Amlogic Meson6/Meson8/Meson8b efuse support Martin Blumenstingl
[not found] ` <20171001125700.1520-1-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-10-01 12:56 ` [PATCH 1/4] dt-bindings: nvmem: Describe the Amlogic Meson6/Meson8/Meson8b efuse Martin Blumenstingl
2017-10-01 12:56 ` [PATCH 2/4] nvmem: meson-efuse: indicate that this driver is only for Meson GX SoCs Martin Blumenstingl
2017-10-01 12:56 ` [PATCH 3/4] nvmem: add a driver for the Amlogic Meson6/Meson8/Meson8b SoCs Martin Blumenstingl
[not found] ` <20171001125700.1520-4-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-10-02 15:28 ` Srinivas Kandagatla [this message]
[not found] ` <8f1f5a45-951c-7434-44d5-4ef2a61ec038-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-10-02 18:38 ` Martin Blumenstingl
2017-10-03 4:48 ` Chris Moore
[not found] ` <cd1e7f9c-5aff-8f4c-82b0-c58c2de4c253-GANU6spQydw@public.gmane.org>
2017-10-03 11:14 ` Martin Blumenstingl
2017-10-09 10:36 ` Srinivas Kandagatla
2017-10-01 12:57 ` [PATCH 4/4] ARM: dts: meson: add the efuse node Martin Blumenstingl
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=8f1f5a45-951c-7434-44d5-4ef2a61ec038@linaro.org \
--to=srinivas.kandagatla-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
--cc=linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).