From: Matt Porter <matt.porter@linaro.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Tim Kryger <tim.kryger@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Christian Daudt <bcm@fixthebug.org>,
Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"patches@linaro.org" <patches@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Thomas Gleixner <tglx@linutronix.de>, Chris Ball <cjb@laptop.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH v2 6/6] mmc: sdhci-bcm-kona: Add basic use of clocks
Date: Fri, 18 Oct 2013 09:22:57 -0400 [thread overview]
Message-ID: <20131018132257.GG2721@beef> (raw)
In-Reply-To: <20131017141309.GG24056@e106331-lin.cambridge.arm.com>
On Thu, Oct 17, 2013 at 03:13:09PM +0100, Mark Rutland wrote:
> On Wed, Oct 16, 2013 at 10:47:10PM +0100, Tim Kryger wrote:
> > + /* Get and enable the external clock */
> > + kona_dev->external_clk = devm_clk_get(dev, NULL);
> > + if (IS_ERR(kona_dev->external_clk)) {
> > + dev_err(dev, "Failed to get external clock\n");
> > + ret = PTR_ERR(kona_dev->external_clk);
> > + goto err_pltfm_free;
>
> This seems like a pretty clear breakage of existing DTBs.
>
> Why?
Normal kernel incremental development. The notion of breaking DTBs is
pretty much incompatible with the long-standing tradition of developing
kernel support in an incremental fashion.
In this case, the bootloader available on these boards has had clocks
and regulators enabled for all the drivers currently upstream. This
allowed development of the sdhci driver (and others) independent of having
the common clk driver and PMU/regulator drivers ready. That's been especially
important given the flux that the common clk framework is in with regards
to bindings.
Are you suggesting that the required clock needs to be made logically
optional in the code to retain backward compatbility?
-Matt
next prev parent reply other threads:[~2013-10-18 13:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 21:47 [RESEND PATCH v2 0/6] Update Kona drivers to use clocks Tim Kryger
2013-10-16 21:47 ` [RESEND PATCH v2 1/6] ARM: dts: Declare clocks as fixed on bcm11351 Tim Kryger
2013-11-08 10:53 ` Daniel Lezcano
2013-11-08 19:42 ` Tim Kryger
2013-11-08 21:35 ` Christian Daudt
2013-10-16 21:47 ` [RESEND PATCH v2 2/6] ARM: dts: Specify clocks for UARTs " Tim Kryger
2013-10-17 5:41 ` Christian Daudt
[not found] ` <CAEPRUYrzAow1yr58jOp5ead7BkQx-K7yaLLzSHPwqYVu=aZFEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-17 6:14 ` Sebastian Hesselbarth
2013-10-17 13:56 ` Mark Rutland
2013-10-21 18:56 ` Tim Kryger
2013-10-16 21:47 ` [RESEND PATCH v2 3/6] ARM: dts: Specify clocks for SDHCIs " Tim Kryger
2013-10-16 21:47 ` [RESEND PATCH v2 4/6] clocksource: kona: Add basic use of external clock Tim Kryger
2013-10-17 14:05 ` Mark Rutland
[not found] ` <20131017140542.GE24056-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-10-21 21:07 ` Tim Kryger
[not found] ` <1381960030-1640-1-git-send-email-tim.kryger-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-10-16 21:47 ` [RESEND PATCH v2 5/6] ARM: dts: Specify clocks for timer on bcm11351 Tim Kryger
2013-10-17 14:06 ` Mark Rutland
2013-10-18 20:25 ` Tim Kryger
2013-10-17 13:47 ` [RESEND PATCH v2 0/6] Update Kona drivers to use clocks Mark Rutland
2013-10-16 21:47 ` [RESEND PATCH v2 6/6] mmc: sdhci-bcm-kona: Add basic use of clocks Tim Kryger
2013-10-17 14:13 ` Mark Rutland
2013-10-18 13:22 ` Matt Porter [this message]
2013-10-21 23:13 ` Tim Kryger
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=20131018132257.GG2721@beef \
--to=matt.porter@linaro.org \
--cc=Pawel.Moll@arm.com \
--cc=bcm@fixthebug.org \
--cc=cjb@laptop.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=tglx@linutronix.de \
--cc=tim.kryger@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).