From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Grant Likely <grant.likely@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [RFC PATCH 0/2] DT match helpers for initcalls and platform devices
Date: Wed, 30 Oct 2013 09:26:22 +0100 [thread overview]
Message-ID: <20131030082621.GA22787@ulmo.nvidia.com> (raw)
In-Reply-To: <1383113571-13029-1-git-send-email-robherring2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Wed, Oct 30, 2013 at 01:12:49AM -0500, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> This series adds a couple of boilerplate helpers to match with DT for
> initcalls and platform device creation and probe. The goal here is to
> remove more platform code out of arch/arm and eventually the machine
> descriptors.
I fear that this is a step backwards because it makes it easier for
people to do the wrong thing. We've been doing the same with interrupt
controllers and clocks. With those there's at least the argument that
they need to be available really early and therefore cannot use the
regular driver model. But for everything else, shouldn't we enforce
proper drivers to be written?
Perhaps if you can point me to some examples I could get more context
why and where this would be useful.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-30 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 6:12 [RFC PATCH 0/2] DT match helpers for initcalls and platform devices Rob Herring
[not found] ` < 1383113571-13029-3-git-send-email-robherring2@gmail.com>
[not found] ` <20131121125007. 17A8FC40A2C@trevor.secretlab.ca>
[not found] ` < 20131030082621.GA22787@ulmo.nvidia.com>
[not found] ` < 1383113571-13029-2-git-send-email-robherring2@gmail.com>
[not found] ` <20131121124736. 6EBEBC40A2C@trevor.secretlab.ca>
2013-10-30 6:12 ` [RFC PATCH 1/2] driver core: introduce module_platform_driver_match_and_probe Rob Herring
2013-11-21 12:47 ` Grant Likely
2013-11-21 22:33 ` Rob Herring
2013-11-21 23:11 ` Grant Likely
2013-10-30 6:12 ` [RFC PATCH 2/2] of: add initcall with match boilerplate helpers Rob Herring
2013-11-21 12:50 ` Grant Likely
2013-11-21 23:23 ` Rob Herring
2013-11-27 15:22 ` Grant Likely
2013-12-05 17:57 ` Rob Herring
2013-10-30 8:26 ` Thierry Reding [this message]
2013-10-30 20:02 ` [RFC PATCH 0/2] DT match helpers for initcalls and platform devices Rob Herring
2013-10-30 21:40 ` Rob Herring
2013-11-21 12:53 ` Grant Likely
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=20131030082621.GA22787@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.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