From: Ming Yu <a0282524688@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl, andi.shyti@kernel.org,
mkl@pengutronix.de, mailhol.vincent@wanadoo.fr,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, wim@linux-watchdog.org,
linux@roeck-us.net, jdelvare@suse.com,
alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-rtc@vger.kernel.org, linux-usb@vger.kernel.org,
Ming Yu <tmyu0@nuvoton.com>
Subject: Re: [PATCH v12 1/7] mfd: Add core driver for Nuvoton NCT6694
Date: Thu, 12 Jun 2025 22:40:55 +0800 [thread overview]
Message-ID: <CAOoeyxVvZiD18qbGd5oUnqLNETKw50fJBjJO3vR50kon_a5_kA@mail.gmail.com> (raw)
In-Reply-To: <20250612140041.GF381401@google.com>
Dear Lee,
Thank you for reviewing,
Lee Jones <lee@kernel.org> 於 2025年6月12日 週四 下午10:00寫道:
>
...
> > +static const struct mfd_cell nct6694_devs[] = {
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 0),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 1),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 2),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 3),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 4),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 5),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 6),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 7),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 8),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 9),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 10),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 11),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 12),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 13),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 14),
> > + MFD_CELL_BASIC("nct6694-gpio", NULL, NULL, 0, 15),
> > +
> > + MFD_CELL_BASIC("nct6694-i2c", NULL, NULL, 0, 0),
> > + MFD_CELL_BASIC("nct6694-i2c", NULL, NULL, 0, 1),
> > + MFD_CELL_BASIC("nct6694-i2c", NULL, NULL, 0, 2),
> > + MFD_CELL_BASIC("nct6694-i2c", NULL, NULL, 0, 3),
> > + MFD_CELL_BASIC("nct6694-i2c", NULL, NULL, 0, 4),
> > + MFD_CELL_BASIC("nct6694-i2c", NULL, NULL, 0, 5),
>
> Why have we gone back to this silly numbering scheme?
>
> What happened to using IDA in the child driver?
>
In a previous version, I tried to maintain a static IDA in each
sub-driver. However, I didn’t consider the case where multiple NCT6694
devices are bound to the same driver — in that case, the IDs are not
fixed and become unusable for my purpose.
I’ve since realized that using pdev->id avoids the need for cell->id,
so I reverted to the earlier approach.
That said, do you think it would be a better solution to manage all
the IDAs centrally within the driver? For example:
in nct6694.c
struct nct6694 {
struct device *dev;
struct ida gpio_ida;
struct ida i2c_ida;
struct ida can_ida;
struct ida wdt_ida;
};
static int nct6694_probe(struct platform_device *pdev)
{
ida_init(&nct6694->gpio_ida);
...
}
in gpio-nct6694.c
static int nct6694_gpio_probe(struct platform_device *pdev)
{
id = ida_alloc(&nct6694->gpio_ida, GFP_KERNEL);
}
Best regards,
Ming
next prev parent reply other threads:[~2025-06-12 14:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 4:14 [PATCH v12 0/7] Add Nuvoton NCT6694 MFD drivers a0282524688
2025-06-04 4:14 ` [PATCH v12 1/7] mfd: Add core driver for Nuvoton NCT6694 a0282524688
2025-06-04 10:11 ` Oliver Neukum
2025-06-04 12:40 ` Guenter Roeck
2025-06-05 7:49 ` Ming Yu
2025-06-05 7:48 ` Ming Yu
2025-06-12 14:00 ` Lee Jones
2025-06-12 14:40 ` Ming Yu [this message]
2025-06-12 15:23 ` Lee Jones
2025-06-13 1:54 ` Ming Yu
2025-06-13 13:11 ` Lee Jones
2025-06-13 15:09 ` Ming Yu
2025-06-19 11:53 ` Lee Jones
2025-06-19 12:24 ` Ming Yu
2025-06-19 15:28 ` Lee Jones
2025-06-19 16:03 ` Ming Yu
2025-06-19 16:20 ` Greg KH
2025-06-19 16:58 ` Guenter Roeck
2025-06-19 17:18 ` Greg KH
2025-06-20 2:54 ` Ming Yu
2025-06-20 5:02 ` Greg KH
2025-06-25 9:01 ` Lee Jones
2025-06-25 10:54 ` Ming Yu
2025-06-25 13:46 ` Lee Jones
2025-06-25 14:24 ` Ming Yu
2025-06-25 14:53 ` Lee Jones
2025-06-04 4:14 ` [PATCH v12 2/7] gpio: Add Nuvoton NCT6694 GPIO support a0282524688
2025-06-04 4:14 ` [PATCH v12 3/7] i2c: Add Nuvoton NCT6694 I2C support a0282524688
2025-06-04 4:14 ` [PATCH v12 4/7] can: Add Nuvoton NCT6694 CANFD support a0282524688
2025-06-04 10:19 ` Vincent Mailhol
2025-06-04 4:14 ` [PATCH v12 5/7] watchdog: Add Nuvoton NCT6694 WDT support a0282524688
2025-06-04 4:14 ` [PATCH v12 6/7] hwmon: Add Nuvoton NCT6694 HWMON support a0282524688
2025-06-04 4:14 ` [PATCH v12 7/7] rtc: Add Nuvoton NCT6694 RTC support a0282524688
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=CAOoeyxVvZiD18qbGd5oUnqLNETKw50fJBjJO3vR50kon_a5_kA@mail.gmail.com \
--to=a0282524688@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tmyu0@nuvoton.com \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).