From: Lee Jones <lee@kernel.org>
To: Marcos Del Sol Vives <marcos@orca.pet>
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Michael Walle <mwalle@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-gpio@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 3/3] mfd: vortex: implement new driver for Vortex southbridges
Date: Wed, 3 Sep 2025 15:01:15 +0100 [thread overview]
Message-ID: <20250903140115.GC2764654@google.com> (raw)
In-Reply-To: <1d4352b6-c27e-4946-be36-87765f3fb7c3@orca.pet>
On Wed, 03 Sep 2025, Marcos Del Sol Vives wrote:
> El 03/09/2025 a las 9:21, Lee Jones escribió:
> >>>> +static const struct mfd_cell vortex_dx_sb_cells[] = {
> >>>> + {
> >>>> + .name = "vortex-gpio",
> >>>> + .resources = vortex_dx_gpio_resources,
> >>>> + .num_resources = ARRAY_SIZE(vortex_dx_gpio_resources),
> >>>> + },
> >>>> +};
> >>>
> >>> It's not an MFD until you have more than one device.
> >>
> >> Same as above.
> >
> > It will not be accepted with only a single device (SFD?).
> >
>
> I've been working on making all the changes, except this one.
>
> If you prefer, I can either implement the watchdog now, add it on this
Yes, please implement the WDT now.
> patch series and thus make it a proper MFD (at the cost of delaying
> even further the GPIO inclusion), or keep the struct mfd_cell array
> as a single-element array and implement the watchdog later on another
> merge request, using that very same array.
>
> I am however not okay with wasting my time rewriting that to bypass
> the MFD API for this, so I can waste even more time later
> implementing again the MFD API, just because linguistically
> one (right now) is technically not "multi".
I don't get this. If you implement the WDT now, you will be "multi", so
what are you protesting against?
> That seems very unreasonable, specially when it wouldn't be a first
> since at least these other devices are also using MFD with a single
> device:
>
> - 88pm80
% grep name drivers/mfd/88pm800.c
.name = "88pm80x-rtc",
.name = "88pm80x-onkey",
.name = "88pm80x-regulator",
.name = "88pm800",
> - 88pm805
% grep name drivers/mfd/88pm805.c
.name = "88pm80x-codec",
.name = "88pm805",
> - at91-usart
% grep NAME drivers/mfd/at91-usart.c
MFD_CELL_NAME("at91_usart_spi");
MFD_CELL_NAME("atmel_usart_serial");
> - stw481x
* Copyright (C) 2013 ST-Ericsson SA
> - vx855
* Copyright (C) 2009 VIA Technologies, Inc.
> - wm8400
* Copyright 2008 Wolfson Microelectronics PLC.
> - zynqmp (last changed in 2024, so certainly not legacy!)
This should _not_ be using the MFD API at all!
> And probably others since I did not look too deep into it.
>
> Greetings,
> Marcos
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-09-03 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 13:58 [PATCH v4 0/3] Introduce support for Vortex GPIO pins Marcos Del Sol Vives
2025-08-22 13:58 ` [PATCH v4 1/3] gpio: gpio-regmap: add flag to set direction before value Marcos Del Sol Vives
2025-08-22 13:58 ` [PATCH v4 2/3] gpio: vortex: add new GPIO device driver Marcos Del Sol Vives
2025-08-24 7:42 ` William Breathitt Gray
2025-08-22 13:58 ` [PATCH v4 3/3] mfd: vortex: implement new driver for Vortex southbridges Marcos Del Sol Vives
2025-09-02 15:18 ` Lee Jones
2025-09-02 18:06 ` Marcos Del Sol Vives
2025-09-03 7:21 ` Lee Jones
2025-09-03 7:43 ` Marcos Del Sol Vives
2025-09-03 9:14 ` Lee Jones
2025-09-03 13:01 ` Marcos Del Sol Vives
2025-09-03 14:01 ` Lee Jones [this message]
2025-09-03 14:48 ` Marcos Del Sol Vives
2025-09-04 10:17 ` Lee Jones
2025-09-04 12:21 ` Marcos Del Sol Vives
2025-09-08 14:24 ` Lee Jones
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=20250903140115.GC2764654@google.com \
--to=lee@kernel.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marcos@orca.pet \
--cc=mwalle@kernel.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®