From: Rich Felker <dalias@libc.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>,
David Lechner <david@lechnology.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Frank Rowand <frowand.list@gmail.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Arend van Spriel <aspriel@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Michal Suchanek <msuchanek@suse.de>,
Jan Kiszka <jan.kiszka@siemens.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Peter Rosin <peda@axentia.se>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH RFC PoC 0/2] platform: different approach to early platform drivers
Date: Thu, 26 Apr 2018 13:31:51 -0400 [thread overview]
Message-ID: <20180426173151.GJ3094@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180426152920.21569-1-brgl@bgdev.pl>
On Thu, Apr 26, 2018 at 05:29:18PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> This is a follow to my series[1] the aim of which was to introduce device tree
> support for early platform devices.
>
> It was received rather negatively. Aside from using device tree to pass
> implementation specific details to the system, two important concerns were
> raised: no probe deferral support and the fact that currently the early devices
> never get converted to actual platform drivers. This series is a
> proof-of-concept that's trying to address those issues.
>
> The only user of the current version of early platform drivers is the SuperH
> architecture. If this series eventually gets merged, we could simply replace
> the other solution.
Looking at a quick output of:
grep -r -A10 early_devices[[] arch/sh/kernel/
it looks like all of the existing early platform devices are serial
ports, clocks, and clocksources. The switch to device tree should pick
them all up from CLK_OF_DECLARE, TIMER_OF_DECLARE, and
EARLYCON_DECLARE. Until that's complete, the existing code works
as-is. I don't see what problem you're trying to solve.
FYI I'm (sometimes-somewhat-absent) arch/sh co-maintainer.
Rich
next prev parent reply other threads:[~2018-04-26 17:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 15:29 Bartosz Golaszewski
2018-04-26 15:29 ` [PATCH RFC PoC 1/2] earlydev: implement a new way to probe platform devices early Bartosz Golaszewski
2018-04-27 15:13 ` Arnd Bergmann
2018-04-26 15:29 ` [PATCH RFC PoC 2/2] misc: implement a dummy early platform driver Bartosz Golaszewski
2018-04-26 17:31 ` Rich Felker [this message]
2018-04-27 2:28 ` [PATCH RFC PoC 0/2] platform: different approach to early platform drivers David Lechner
2018-04-27 2:54 ` Rich Felker
2018-04-27 7:52 ` Arnd Bergmann
2018-04-27 8:29 ` Sekhar Nori
2018-04-27 8:55 ` Arnd Bergmann
2018-04-27 8:59 ` Bartosz Golaszewski
2018-04-27 8:57 ` Bartosz Golaszewski
2018-04-27 10:18 ` Arnd Bergmann
2018-04-27 11:53 ` Bartosz Golaszewski
2018-04-27 12:40 ` Arnd Bergmann
2018-04-27 14:05 ` Bartosz Golaszewski
2018-04-27 14:48 ` Arnd Bergmann
2018-04-27 16:05 ` Bartosz Golaszewski
2018-04-27 19:08 ` Arnd Bergmann
2018-04-27 15:22 ` Rich Felker
2018-05-02 21:11 ` Geert Uytterhoeven
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=20180426173151.GJ3094@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=aspriel@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=msuchanek@suse.de \
--cc=mturquette@baylibre.com \
--cc=nsekhar@ti.com \
--cc=peda@axentia.se \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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®