public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] nvmem: qfprom: increase id to support multiple devices
Date: Tue, 30 Jun 2020 19:18:20 +0800	[thread overview]
Message-ID: <20200630111819.GE8343@dragon> (raw)
In-Reply-To: <04022e2b-e028-b942-811d-a9c8ac836fcc@linaro.org>

Hi Srini,

On Tue, Jun 30, 2020 at 10:41:24AM +0100, Srinivas Kandagatla wrote:
> TBH, this functionality need to go into core driver which already has IDR to
> allocated ID's for nvmem providers.
> 
> Can you try this patch:

The patch doesn't apply to v5.8-rc, so I manually applied it for
testing. It works like a charm.

Tested-by: Shawn Guo <shawn.guo@linaro.org>

Please copy me when you post it, so that I can pick it up for my
project.  Thanks!

Shawn

> 
> ---------------------------->cut<---------------------------------diff --git
> a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index 927eb5f6003f..aa87bd6415ab 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -629,12 +629,18 @@ struct nvmem_device *nvmem_register(const struct
> nvmem_config *config)
>         if (!config->no_of_node)
>                 nvmem->dev.of_node = config->dev->of_node;
> 
> -       if (config->id == -1 && config->name) {
> +       switch (config->id) {
> +       case NVMEM_DEVID_NONE:
>                 dev_set_name(&nvmem->dev, "%s", config->name);
> -       } else {
> +               break;
> +       case NVMEM_DEVID_AUTO:
> +               dev_set_name(&nvmem->dev, "%s%d", config->name, nvmem->id);
> +               break;
> +       default:
>                 dev_set_name(&nvmem->dev, "%s%d",
>                              config->name ? : "nvmem",
>                              config->name ? config->id : nvmem->id);
> +               break;
>         }
> 
>         nvmem->read_only = device_property_present(config->dev, "read-only")
> ||
> diff --git a/drivers/nvmem/qfprom.c b/drivers/nvmem/qfprom.c
> index 8a91717600be..8b425f8d847d 100644
> --- a/drivers/nvmem/qfprom.c
> +++ b/drivers/nvmem/qfprom.c
> @@ -31,6 +31,7 @@ static struct nvmem_config econfig = {
>         .name = "qfprom",
>         .stride = 1,
>         .word_size = 1,
> +       .id = NVMEM_DEVID_AUTO,
>         .reg_read = qfprom_reg_read,
>  };
> 
> diff --git a/include/linux/nvmem-provider.h b/include/linux/nvmem-provider.h
> index 6d6f8e5d24c9..06409a6c40bc 100644
> --- a/include/linux/nvmem-provider.h
> +++ b/include/linux/nvmem-provider.h
> @@ -27,6 +27,9 @@ enum nvmem_type {
>         NVMEM_TYPE_BATTERY_BACKED,
>  };
> 
> +#define NVMEM_DEVID_NONE       (-1)
> +#define NVMEM_DEVID_AUTO       (-2)
> +
>  /**
>   * struct nvmem_config - NVMEM device configuration
>   *
> ---------------------------->cut<---------------------------------

      reply	other threads:[~2020-06-30 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 13:32 [PATCH] nvmem: qfprom: increase id to support multiple devices Shawn Guo
2020-06-30  9:41 ` Srinivas Kandagatla
2020-06-30 11:18   ` Shawn Guo [this message]

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=20200630111819.GE8343@dragon \
    --to=shawn.guo@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.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