From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: <devicetree@vger.kernel.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Rob Herring <rob.herring@calxeda.com>,
<linux-crypto@vger.kernel.org>,
Tobias Rauter <tobiasrauter@gmail.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] ARM: dts: mxs: set dcp to "disabled" by default
Date: Mon, 12 Aug 2013 14:05:51 +0200 [thread overview]
Message-ID: <21000.53151.841177.378797@ipc1.ka-ro> (raw)
In-Reply-To: <20130812110523.GD25292@S2101-09.ap.freescale.net>
Hi,
Shawn Guo writes:
> On Thu, Aug 08, 2013 at 03:30:27PM +0200, Lothar Waßmann wrote:
> > Reintroduce 'status = "disabled"' for the dcp node that was dropped by
> > commit 519d8b1a "Added support for Freescale's DCP co-processor".
>
> For IP blocks that do not have pins to be routed on boards, it should be
> fine to have it enabled in <soc>.dtsi.
>
That means that when a new driver is added, it will start wasting
resources on all board using that SoC unless the board maintainers
explicitly disable that driver in DTB.
I would prefer things to be the other way:
New drivers (no matter whether for chip-internal or external hardware)
should require to be explicitly enabled for those platforms on which
they are being used.
Lothar Waßmann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Geschäftsführer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info@karo-electronics.de
___________________________________________________________
next prev parent reply other threads:[~2013-08-12 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:30 [PATCH 0/3] ARM: dts: mxs: dcp cleanup patches Lothar Waßmann
2013-08-08 13:30 ` [PATCH 1/3] ARM: dts: mxs: set dcp to "disabled" by default Lothar Waßmann
2013-08-12 11:05 ` Shawn Guo
2013-08-12 12:05 ` Lothar Waßmann [this message]
2013-08-12 14:17 ` Kumar Gala
2013-08-08 13:30 ` [PATCH 2/3] crypto: dcp - cleanup: commas at end of struct initializers where appropriate Lothar Waßmann
2013-08-08 13:30 ` [PATCH 3/3] crypto: dcp: rename 'compatible' property to 'fsl,dcp' Lothar Waßmann
2013-08-08 19:39 ` Sergei Shtylyov
2013-08-08 21:14 ` [PATCH 0/3] ARM: dts: mxs: dcp cleanup patches Kumar Gala
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=21000.53151.841177.378797@ipc1.ka-ro \
--to=lw@karo-electronics.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=tobiasrauter@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