[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zln9lRvKJYwlSM3l@smile.fi.intel.com>
Date: Fri, 31 May 2024 19:40:53 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Lee Jones <lee@...nel.org>
Cc: linux-kernel@...r.kernel.org, Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v1 1/2] mfd: lm3533: Hide legacy platform data in the
driver
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.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists