From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 06/11] net: dsa: ksz9477: create regmap cdev for switch registers
Date: Wed, 11 Jan 2023 10:33:06 +0100 [thread overview]
Message-ID: <79b1495c-6399-ddc0-71ea-d1827d490f0b@pengutronix.de> (raw)
In-Reply-To: <20230111085613.GJ24755@pengutronix.de>
Hi,
On 11.01.23 09:56, Sascha Hauer wrote:
> On Wed, Jan 11, 2023 at 09:01:14AM +0100, Ahmad Fatoum wrote:
>> Now that we use regmap for the KSZ9477 driver, we can make the register
>> map available for introspection as a device file. As the KSZ driver has
>> a separate regmap for each of the three access sizes, we add a new
>> regmap_multi_register_cdev abstraction that multiplexes device file
>> access to the regmap with the best matching alignment.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>> drivers/base/regmap/Makefile | 1 +
>> drivers/base/regmap/regmap-multi.c | 81 ++++++++++++++++++++++++++++++
>> drivers/net/ksz9477.c | 6 ++-
>> include/regmap.h | 2 +
>> 4 files changed, 89 insertions(+), 1 deletion(-)
>> create mode 100644 drivers/base/regmap/regmap-multi.c
>>
>> diff --git a/drivers/base/regmap/Makefile b/drivers/base/regmap/Makefile
>> index d99db4277149..fe5beaaaa382 100644
>> --- a/drivers/base/regmap/Makefile
>> +++ b/drivers/base/regmap/Makefile
>> @@ -1,5 +1,6 @@
>> # SPDX-License-Identifier: GPL-2.0-only
>> obj-y += regmap.o
>> +obj-y += regmap-multi.o
>> obj-y += regmap-mmio.o
>> obj-$(CONFIG_REGMAP_FORMATTED) += regmap-fmt.o
>> obj-$(CONFIG_I2C) += regmap-i2c.o
>> diff --git a/drivers/base/regmap/regmap-multi.c b/drivers/base/regmap/regmap-multi.c
>> new file mode 100644
>> index 000000000000..79dd1ba9bd95
>> --- /dev/null
>> +++ b/drivers/base/regmap/regmap-multi.c
>> @@ -0,0 +1,81 @@
>> +// SPDX-License-Identifier: GPL-2.0-only
>> +/*
>> + * Copyright 2022 Ahmad Fatoum <a.fatoum@pengutronix.de>
>> + */
>> +
>> +#include <common.h>
>> +#include <regmap.h>
>> +#include <linux/export.h>
>> +
>> +#include "internal.h"
>> +
>> +enum { MULTI_MAP_8, MULTI_MAP_16, MULTI_MAP_32, MULTI_MAP_COUNT };
>> +struct regmap_multi {
>> + struct cdev cdev;
>> + struct regmap *map[MULTI_MAP_COUNT];
>> +};
>> +
>> +static struct regmap *regmap_multi_cdev_get_map(struct cdev *cdev, size_t count)
>> +{
>> + struct regmap_multi *multi = container_of(cdev, struct regmap_multi, cdev);
>> + struct regmap *map = NULL;
>> +
>> + if (count % 4 == 0)
>> + map = multi->map[MULTI_MAP_32];
>> + if (!map && count % 2 == 0)
>> + map = multi->map[MULTI_MAP_16];
>> + return map ?: multi->map[MULTI_MAP_8];
>> +}
>
> You pick the regmap only based on 'count'. Shouldn't you take the offset
> into account as well?
I don't think so. This is a bit similar to mem_copy(), which underlies
the mw command. There we only use count as well and if offset is unaligned,
so be it.
>
>> +
>> +static ssize_t regmap_multi_cdev_read(struct cdev *cdev, void *buf, size_t count,
>> + loff_t offset, unsigned long flags)
>> +{
>> + struct regmap *map = regmap_multi_cdev_get_map(cdev, count);
>> +
>> + return regmap_bulk_read(map, offset, buf, count) ?: count;
>> +}
>> +
>> +static ssize_t regmap_multi_cdev_write(struct cdev *cdev, const void *buf, size_t count,
>> + loff_t offset, unsigned long flags)
>> +{
>> + struct regmap *map = regmap_multi_cdev_get_map(cdev, count);
>> +
>> + return regmap_bulk_write(map, offset, buf, count) ?: count;
>> +}
>> +
>> +static struct cdev_operations regmap_multi_fops = {
>> + .read = regmap_multi_cdev_read,
>> + .write = regmap_multi_cdev_write,
>> +};
>> +
>> +int regmap_multi_register_cdev(struct regmap *maps[3])
>
> MULTI_MAP_COUNT instead of 3?
I didn't want to define the symbol in the header, so kept this for
symmetry.
Cheers,
Ahmad
>
> Sascha
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-01-11 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 8:01 [PATCH 00/11] net: dsa: ksz9477: use regmap to add I2C support next to SPI Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 01/11] regmap: consolidate reg/val format into regmap_format Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 02/11] regmap: support formatted read and write Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 03/11] regmap: port regmap_init_spi Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 04/11] regmap: factor out regmap cdev size calculation Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 05/11] net: dsa: ksz9477: switch to regmap_init_spi Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 06/11] net: dsa: ksz9477: create regmap cdev for switch registers Ahmad Fatoum
2023-01-11 8:56 ` Sascha Hauer
2023-01-11 9:33 ` Ahmad Fatoum [this message]
2023-01-11 8:01 ` [PATCH 07/11] drivers: base: regmap: introduce REGMAP_I2C Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 08/11] dev: add dev_bus_is_spi/i2c helpers Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 09/11] net: dsa: ksz9477: refactor to prepare i2c support Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 10/11] regmap: i2c: use formatted I/O Ahmad Fatoum
2023-01-11 8:01 ` [PATCH 11/11] net: ksz9477: add I2C support Ahmad Fatoum
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=79b1495c-6399-ddc0-71ea-d1827d490f0b@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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