From: Casey Connolly <casey.connolly@linaro.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
sboyd@kernel.org
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org,
srini@kernel.org, vkoul@kernel.org, kishon@kernel.org,
sre@kernel.org, krzysztof.kozlowski@linaro.org,
u.kleine-koenig@baylibre.com, linux-arm-msm@vger.kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org, linux-pm@vger.kernel.org,
kernel@collabora.com, wenst@chromium.org
Subject: Re: [PATCH v1 2/7] nvmem: qcom-spmi-sdam: Migrate to devm_spmi_subdevice_alloc_and_add()
Date: Mon, 21 Jul 2025 12:44:26 +0200 [thread overview]
Message-ID: <e724e6a2-21a8-436a-8809-ce73c0afa433@linaro.org> (raw)
In-Reply-To: <20250721075525.29636-3-angelogioacchino.delregno@collabora.com>
Hi Angelo,
On 21/07/2025 09:55, AngeloGioacchino Del Regno wrote:
> Some Qualcomm PMICs integrate a SDAM device, internally located in
> a specific address range reachable through SPMI communication.
>
> Instead of using the parent SPMI device (the main PMIC) as a kind
> of syscon in this driver, register a new SPMI sub-device for SDAM
> and initialize its own regmap with this sub-device's specific base
> address, retrieved from the devicetree.
>
> This allows to stop manually adding the register base address to
> every R/W call in this driver, as this can be, and is now, handled
> by the regmap API instead.
This is honestly a really nice improvement :D>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> drivers/nvmem/qcom-spmi-sdam.c | 41 +++++++++++++++++++++++++---------
> 1 file changed, 30 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/nvmem/qcom-spmi-sdam.c b/drivers/nvmem/qcom-spmi-sdam.c
> index 4f1cca6eab71..1b80e8563a33 100644
> --- a/drivers/nvmem/qcom-spmi-sdam.c
> +++ b/drivers/nvmem/qcom-spmi-sdam.c
> @@ -9,6 +9,7 @@
> #include <linux/nvmem-provider.h>
> #include <linux/platform_device.h>
> #include <linux/regmap.h>
> +#include <linux/spmi.h>
>
> #define SDAM_MEM_START 0x40
> #define REGISTER_MAP_ID 0x40
> @@ -20,7 +21,6 @@
> struct sdam_chip {
> struct regmap *regmap;
> struct nvmem_config sdam_config;
> - unsigned int base;
> unsigned int size;
> };
>
> @@ -73,7 +73,7 @@ static int sdam_read(void *priv, unsigned int offset, void *val,
> return -EINVAL;
> }
>
> - rc = regmap_bulk_read(sdam->regmap, sdam->base + offset, val, bytes);
> + rc = regmap_bulk_read(sdam->regmap, offset, val, bytes);
> if (rc < 0)
> dev_err(dev, "Failed to read SDAM offset %#x len=%zd, rc=%d\n",
> offset, bytes, rc);
> @@ -100,7 +100,7 @@ static int sdam_write(void *priv, unsigned int offset, void *val,
> return -EINVAL;
> }
>
> - rc = regmap_bulk_write(sdam->regmap, sdam->base + offset, val, bytes);
> + rc = regmap_bulk_write(sdam->regmap, offset, val, bytes);
> if (rc < 0)
> dev_err(dev, "Failed to write SDAM offset %#x len=%zd, rc=%d\n",
> offset, bytes, rc);
> @@ -110,28 +110,47 @@ static int sdam_write(void *priv, unsigned int offset, void *val,
>
> static int sdam_probe(struct platform_device *pdev)
> {
> + struct regmap_config sdam_regmap_config = {
> + .reg_bits = 16,
> + .val_bits = 16,
I believe registers are 8 bits wide, at least on Qualcomm platforms.
Kind regards,
--
// Casey (she/her)
next prev parent reply other threads:[~2025-07-21 10:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 7:55 [PATCH v1 0/7] SPMI: Implement sub-devices and migrate drivers AngeloGioacchino Del Regno
2025-07-21 7:55 ` [PATCH v1 1/7] spmi: Implement spmi_subdevice_alloc_and_add() and devm variant AngeloGioacchino Del Regno
2025-07-21 11:34 ` Andy Shevchenko
2025-07-21 13:00 ` AngeloGioacchino Del Regno
2025-07-21 7:55 ` [PATCH v1 2/7] nvmem: qcom-spmi-sdam: Migrate to devm_spmi_subdevice_alloc_and_add() AngeloGioacchino Del Regno
2025-07-21 10:44 ` Casey Connolly [this message]
2025-07-21 12:45 ` AngeloGioacchino Del Regno
2025-07-21 13:56 ` Casey Connolly
2025-07-22 8:21 ` AngeloGioacchino Del Regno
2025-07-21 7:55 ` [PATCH v1 3/7] power: reset: qcom-pon: " AngeloGioacchino Del Regno
2025-07-21 11:36 ` Andy Shevchenko
2025-07-21 13:05 ` AngeloGioacchino Del Regno
2025-07-21 17:14 ` Andy Shevchenko
2025-07-22 8:23 ` AngeloGioacchino Del Regno
2025-07-21 7:55 ` [PATCH v1 4/7] phy: qualcomm: eusb2-repeater: " AngeloGioacchino Del Regno
2025-07-21 13:10 ` kernel test robot
2025-07-21 18:27 ` kernel test robot
2025-07-21 7:55 ` [PATCH v1 5/7] misc: qcom-coincell: " AngeloGioacchino Del Regno
2025-07-21 8:58 ` Greg KH
2025-07-21 11:30 ` kernel test robot
2025-07-21 7:55 ` [PATCH v1 6/7] iio: adc: qcom-spmi-iadc: " AngeloGioacchino Del Regno
2025-07-21 7:55 ` [PATCH v1 7/7] iio: adc: qcom-spmi-iadc: Remove regmap R/W wrapper functions AngeloGioacchino Del Regno
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=e724e6a2-21a8-436a-8809-ce73c0afa433@linaro.org \
--to=casey.connolly@linaro.org \
--cc=andy@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sboyd@kernel.org \
--cc=sre@kernel.org \
--cc=srini@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
--cc=vkoul@kernel.org \
--cc=wenst@chromium.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®