[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6422bc88-6d0a-7b51-aaa7-640c6961b177@metux.net>
Date: Tue, 17 Dec 2019 14:44:39 +0100
From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To: Greg KH <greg@...ah.com>,
"Enrico Weigelt, metux IT consult" <info@...ux.net>
Cc: linux-kernel@...r.kernel.org, linus.walleij@...aro.org,
bgolaszewski@...libre.com, dmitry.torokhov@...il.com,
jacek.anaszewski@...il.com, pavel@....cz, dmurphy@...com,
arnd@...db.de, masahiroy@...nel.org, michal.lkml@...kovi.net,
kafai@...com, songliubraving@...com, yhs@...com, andriin@...com,
linux-gpio@...r.kernel.org, linux-input@...r.kernel.org,
linux-leds@...r.kernel.org, linux-arch@...r.kernel.org,
linux-kbuild@...r.kernel.org, netdev@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH] RFC: platform driver registering via initcall tables
On 17.12.19 11:31, Greg KH wrote:
Hi,
> No, what is so "special" about platform drivers that they require this?
Nothing, of course ;-)
It's the the starting point for this PoC. The idea actually is doing
this for all other driver types, too (eg. spi, pci, usb, ...). But
they'll need their own tables, as different *_register() functions have
to be called - just haven't implemented that yet.
> If anything, we should be moving _AWAY_ from platform drivers and use
> real bus drivers instead.
That would be nice, but, unfortunately, we have lots of devices which
aren't attached to any (probing-capable) bus. That's why we have things
like oftree, etc.
> Please no, I don't see why this is even needed.
The idea is getting rid of all the init code, which all just does the
same, just calls some *_register() function.
--mtx
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists