[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231125092137.2948-2-amit.kumar-mahapatra@amd.com>
Date: Sat, 25 Nov 2023 14:51:28 +0530
From: Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
To: <broonie@...nel.org>, <tudor.ambarus@...aro.org>,
<pratyush@...nel.org>, <miquel.raynal@...tlin.com>,
<richard@....at>, <vigneshr@...com>,
<sbinding@...nsource.cirrus.com>, <lee@...nel.org>,
<james.schulman@...rus.com>, <david.rhodes@...rus.com>,
<rf@...nsource.cirrus.com>, <perex@...ex.cz>, <tiwai@...e.com>
CC: <linux-spi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<michael@...le.cc>, <linux-mtd@...ts.infradead.org>,
<nicolas.ferre@...rochip.com>, <alexandre.belloni@...tlin.com>,
<claudiu.beznea@...on.dev>, <michal.simek@....com>,
<linux-arm-kernel@...ts.infradead.org>,
<alsa-devel@...a-project.org>, <patches@...nsource.cirrus.com>,
<linux-sound@...r.kernel.org>, <git@....com>,
<amitrkcian2002@...il.com>,
Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
Subject: [PATCH v11 01/10] mfd: tps6594: Use set/get APIs to access spi->chip_select
In preparation for adding multiple CS support for a device, set/get
functions were introduces accessing spi->chip_select in
'commit 303feb3cc06a ("spi: Add APIs in spi core to set/get
spi->chip_select and spi->cs_gpiod")'.
Replace spi->chip_select with spi_get_chipselect() API.
Signed-off-by: Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
---
drivers/mfd/tps6594-spi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/tps6594-spi.c b/drivers/mfd/tps6594-spi.c
index f4b4f37f957f..24b72847e3f5 100644
--- a/drivers/mfd/tps6594-spi.c
+++ b/drivers/mfd/tps6594-spi.c
@@ -98,7 +98,7 @@ static int tps6594_spi_probe(struct spi_device *spi)
spi_set_drvdata(spi, tps);
tps->dev = dev;
- tps->reg = spi->chip_select;
+ tps->reg = spi_get_chipselect(spi, 0);
tps->irq = spi->irq;
tps->regmap = devm_regmap_init(dev, NULL, spi, &tps6594_spi_regmap_config);
--
2.17.1
Powered by blists - more mailing lists