From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Guru Das Srinagesh <gurus@codeaurora.org>, linux-arm-msm@vger.kernel.org
Cc: Subbaraman Narayanamurthy <subbaram@codeaurora.org>,
David Collins <collinsd@codeaurora.org>,
Anirudh Ghayal <aghayal@codeaurora.org>,
Shyam Kumar Thella <sthella@codeaurora.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] nvmem: qcom-spmi-sdam: Enable multiple devices
Date: Wed, 22 Jul 2020 10:32:49 +0100 [thread overview]
Message-ID: <a81a3563-1a87-d302-054e-bc20db8de1e7@linaro.org> (raw)
In-Reply-To: <1595360761-640-1-git-send-email-gurus@codeaurora.org>
On 21/07/2020 20:46, Guru Das Srinagesh wrote:
> Using pdev->id as the nvmem's config ID (which, by default, is
> NVMEM_DEVID_NONE) prevents multiple instances of this driver from
> probing because of the following error:
>
> sysfs: cannot create duplicate filename '/bus/nvmem/devices/spmi_sdam'
>
> Use NVMEM_DEVID_AUTO as the NVMEM config ID to fix the issue.
>
> Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
> ---
> drivers/nvmem/qcom-spmi-sdam.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied thanks,
--srini
>
> diff --git a/drivers/nvmem/qcom-spmi-sdam.c b/drivers/nvmem/qcom-spmi-sdam.c
> index 8682cda..a72704c 100644
> --- a/drivers/nvmem/qcom-spmi-sdam.c
> +++ b/drivers/nvmem/qcom-spmi-sdam.c
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0-only
> /*
> - * Copyright (c) 2017 The Linux Foundation. All rights reserved.
> + * Copyright (c) 2017, 2020 The Linux Foundation. All rights reserved.
> */
>
> #include <linux/device.h>
> @@ -141,7 +141,7 @@ static int sdam_probe(struct platform_device *pdev)
>
> sdam->sdam_config.dev = &pdev->dev;
> sdam->sdam_config.name = "spmi_sdam";
> - sdam->sdam_config.id = pdev->id;
> + sdam->sdam_config.id = NVMEM_DEVID_AUTO;
> sdam->sdam_config.owner = THIS_MODULE,
> sdam->sdam_config.stride = 1;
> sdam->sdam_config.word_size = 1;
>
prev parent reply other threads:[~2020-07-22 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 19:46 Guru Das Srinagesh
2020-07-22 9:32 ` Srinivas Kandagatla [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=a81a3563-1a87-d302-054e-bc20db8de1e7@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=aghayal@codeaurora.org \
--cc=collinsd@codeaurora.org \
--cc=gurus@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sthella@codeaurora.org \
--cc=subbaram@codeaurora.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
all inboxes | Powered by JetHome®