From: Johan Hovold <johan@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 1/2] mfd: lm3533: Hide legacy platform data in the driver
Date: Wed, 5 Jun 2024 14:40:30 +0200 [thread overview]
Message-ID: <ZmBcvtLCzllQDWVX@hovoldconsulting.com> (raw)
In-Reply-To: <20240531165834.GA1204315@google.com>
On Fri, May 31, 2024 at 05:58:34PM +0100, Lee Jones wrote:
> On Fri, 31 May 2024, Andy Shevchenko wrote:
>
> > On Fri, May 31, 2024 at 04:54:45PM +0100, Lee Jones wrote:
> > > On Fri, 31 May 2024, Andy Shevchenko wrote:
> > > > On Fri, May 31, 2024 at 04:00:48PM +0100, Lee Jones wrote:
> > > > > On Wed, 08 May 2024, Andy Shevchenko wrote:
> > > > >
> > > > > > First of all, there is no user for the platform data in the kernel.
> > > > > > Second, it needs a lot of updates to follow the modern standards
> > > > > > of the kernel, including proper Device Tree bindings and device
> > > > > > property handling.
> > > > > >
> > > > > > For now, just hide the legacy platform data in the driver's code.
> > > > >
> > > > > Why not just rip it out entirely?
> > > >
> > > > You mean the driver?
> > >
> > > The unused platform data.
> >
> > Good question. In any case these drivers are non-functional anyway without OOT
> > board code. If we rip out the main platform data completely, the logical following
> > question arises: why do we need the per-device platform data? If we rip that out,
> > we basically make non-functional driver a 100% dead code. Hence what you propose
> > mostly equals to ripping out the drivers completely.
> >
> > TL;DR: with the main platform data being ripped out the driver code will be in
> > inconsistent state.
>
> What do you think Johan? Do you see any reason to keep it around?
Yeah, I'd prefer to keep it around. This device is used in a bunch of
Sony phones and Bjorn A posted a series adding devicetree bindings a few
years ago which I believe was more or less acked and ready go.
I'll try to find some time to look at that myself as I think I may
favour a less verbose binding (e.g. similar to pm8008 that I'm working
on).
For now I suggest keeping the platform data where it is and just convert
the single gpio lookup to look for a "hwen" gpio that can be provided by
lookup tables and soon devicetree.
Johan
next prev parent reply other threads:[~2024-06-05 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 10:46 [PATCH v1 0/2] mfd: lm3533: Get rid of legacy GPIO APIs Andy Shevchenko
2024-05-08 10:46 ` [PATCH v1 1/2] mfd: lm3533: Hide legacy platform data in the driver Andy Shevchenko
2024-05-27 13:03 ` Linus Walleij
2024-05-31 15:00 ` Lee Jones
2024-05-31 15:08 ` Andy Shevchenko
2024-05-31 15:54 ` Lee Jones
2024-05-31 16:40 ` Andy Shevchenko
2024-05-31 16:58 ` Lee Jones
2024-05-31 17:09 ` Andy Shevchenko
2024-06-05 12:40 ` Johan Hovold [this message]
2024-05-08 10:46 ` [PATCH v1 2/2] mfd: lm3533: Move to new GPIO descriptor-based APIs Andy Shevchenko
2024-05-27 13:05 ` Linus Walleij
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=ZmBcvtLCzllQDWVX@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.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®