From: Lee Jones <lee@kernel.org>
To: "Yakovlev, Georgy" <Georgy.Yakovlev@sony.com>
Cc: Timothy Pearson <tpearson@raptorengineering.com>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Anastasio <sanastasio@raptorengineering.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3 2/4] mfd: sony-cronos-cpld: Add driver for Sony Cronos CPLD
Date: Thu, 20 Nov 2025 15:16:58 +0000 [thread overview]
Message-ID: <20251120151658.GG661940@google.com> (raw)
In-Reply-To: <C519436F-296F-4313-87ED-F665CF8EBDAF@sony.com>
On Wed, 19 Nov 2025, Yakovlev, Georgy wrote:
>
>
> > On Oct 9, 2025, at 3:42 AM, Lee Jones <lee@kernel.org> wrote:
> >
> > This doesn't need to / shouldn't reside in the kernel.
> >
> > Why not use I2C and handle all of this in userspace?
> We would prefer to keep the sysfs interfaces in-kernel due to I2C bus contention between the MFD sub-drivers and userspace applications.
> Keeping everything in-kernel allows the kernel itself to arbitrate between the various MFD sub-drivers; punting to userspace complicates each userspace application as they each individually would need to handle I2C bus contention and associated EBUSY responses vs. a sysfs read.
After speaking with the sysfs maintainer, the long and the short of it
is that this isn't going to be accepted. There are a lot of random
sysfs entries being proposed here that are seemingly being dumped into
MFD, which is "not okay".
MFD is often seen as a dumping ground for devices that do not fit
anywhere else. In reality, it's for child device registration, shared
resource management and occasionally some core functionality for larger
devices. Here you can expect to be able to check if you're operating on
the correct device, create the Regmap and instantiate the drivers. For
that we may be able to reasonably suggest that you use simple-mfd-i2c.
The vast majority of this 'device' seems to pertain to letting userspace
control the device via I2C. The way I see it you have 2 options.
Either use simple-mfd-i2c and get the information you need over I2C from
userspace or find another suitable location to house all of the
non-MFD related handling.
> >> \ No newline at end of file
> >
> > ???
> >
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index 0e897f2ba9eb..a1052663fb27 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -23458,6 +23458,13 @@ S: Maintained
> >> F: drivers/ssb/
> >> F: include/linux/ssb/
> >>
> >> +SONY CRONOS CPLD DRIVER
> >> +M: Georgy Yakovlev <Georgy.Yakovlev@sony.com>
> >
> > This person is going to have to Ack the fact that you're making them the
> > person responsible for maintaining this.
> Yes, I acknowledge.
> Not new to open source in general, but new to kernel submissions.
> Sorry for delayed response, was away.
> >
> >> +S: Maintained
> >> +F: Documentation/devicetree/bindings/mfd/sony,cronos-cpld.yaml
> >> +F: drivers/mfd/sony-cronos-cpld.c
> >> +F: include/linux/mfd/sony/cronos/
> >> +
> >> SONY IMX208 SENSOR DRIVER
> >> M: Sakari Ailus <sakari.ailus@linux.intel.com>
> >> L: linux-media@vger.kernel.org
> >> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> >> index 425c5fba6cb1..cd0c624022f6 100644
> >> --- a/drivers/mfd/Kconfig
> >> +++ b/drivers/mfd/Kconfig
> >> @@ -2341,6 +2341,17 @@ config MFD_QCOM_PM8008
> >> under it in the device tree. Additional drivers must be enabled in
> >> order to use the functionality of the device.
> >>
> >> +config MFD_SONY_CRONOS_CPLD
> >> + tristate "Sony Cronos CPLD Support"
> >
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-11-20 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 18:18 [PATCH v3 2/4] mfd: sony-cronos-cpld: Add driver for Sony Cronos CPLD Timothy Pearson
2025-10-09 10:42 ` Lee Jones
2025-11-19 0:51 ` Yakovlev, Georgy
2025-11-20 15:16 ` 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=20251120151658.GG661940@google.com \
--to=lee@kernel.org \
--cc=Georgy.Yakovlev@sony.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sanastasio@raptorengineering.com \
--cc=tpearson@raptorengineering.com \
/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).