Linux PCI subsystem development
 help / color / mirror / Atom feed
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,
	Andy Shevchenko <andriy.shevchenko@intel.com>,
	gregkh@linuxfoundation.org
Subject: Re: [PATCH v4 3/3] mfd: vortex: implement new driver for Vortex southbridges
Date: Mon, 8 Sep 2025 15:24:29 +0100	[thread overview]
Message-ID: <20250908142429.GC9224@google.com> (raw)
In-Reply-To: <75920526-64f4-4eda-8552-58de165f6597@orca.pet>

On Thu, 04 Sep 2025, Marcos Del Sol Vives wrote:

> El 04/09/2025 a las 12:17, Lee Jones escribió:
> >> That GPIO is something required to perform the poweroff sequence, a must
> >> for any machine, while WDT is just a "nice to have".
> >>
> >> Implementing now the WDT just because of a linguistic preference means
> >> delaying something more important in favour of a "nice to have".
> > 
> > You use the word "delaying" here.  What's the rush?
> > 
> > If you only need a GPIO driver, then you don't need the MFD part.
> > 
> 
> I would honestly like that my machines can turn off properly and pretty
> sure others using these platforms would agree on that, as having to yank
> out the power cable is far from ideal.
> 
> Adding WDT would lengthen even further the review process. That ignoring
> I am doing this as a hobby on my spare time and I'd rather spend my
> scarce free time implementing the power off driver than the WDT
> (something I'd do out of completion, I have absolutely no use for a WDT
> in this machine).

Then don't implement it.  Just have the GPIO driver probe on PCI match.

> The reason I am using an MFD is that I was asked to back in v2
> (https://lore.kernel.org/all/aHElavFTptu0q4Kj@smile.fi.intel.com/).
> I'll be CC'ing him.

Andy knows the rules.

> I was told to create a southbridge driver that would match on PCI
> and registered other devices exposed by it as platform drivers.

PCI => Platform is generally decried by Greg and others.

a) With only one device to register, are you sure you need this?
b) If you have more devices, either add them here or use Aux Bus.

> GPIO was the only functionality implemented at the time, and is
> the only functionality implemented right now. So I simply delivered was
> I was asked for.

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2025-09-08 14:24 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
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 [this message]

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=20250908142429.GC9224@google.com \
    --to=lee@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=bhelgaas@google.com \
    --cc=brgl@bgdev.pl \
    --cc=gregkh@linuxfoundation.org \
    --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