From: Eric Anholt <eric@anholt.net>
To: kernel@martin.sperl.org, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Russell King <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Martin Sperl <kernel@martin.sperl.org>
Subject: Re: [PATCH 0/4] add minimal bcm2835-sdram driver
Date: Thu, 12 May 2016 11:15:27 -0700 [thread overview]
Message-ID: <87twi39m80.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1463056732-5607-1-git-send-email-kernel@martin.sperl.org>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
kernel@martin.sperl.org writes:
> From: Martin Sperl <kernel@martin.sperl.org>
>
> As the sdram clock is a critical clock to the system
> the minimal bcm2835-sdram driver claims (and enables)
> this clock and also exposes the corresponding sdram
> registers via debugfs.
I don't think this is a good solution to the problem you are trying to
work around. You're relying on the fact that this driver gets
successfully probed before a driver that would -EPROBE_DEFER on a
sibling clock, which is not a guarantee.
Let's please continue the debugging of clock management on linux-clk.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-05-12 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 12:38 kernel
2016-05-12 12:38 ` [PATCH 1/4] dt: bindings: add bcm2835-memory-controller documentation kernel
2016-05-16 16:04 ` Rob Herring
2016-05-12 12:38 ` [PATCH 2/4] memory: bcm2835: add bcm2835-memory controller kernel
2016-05-12 12:38 ` [PATCH 3/4] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt kernel
2016-05-12 14:56 ` Stefan Wahren
2016-05-12 16:00 ` Martin Sperl
2016-05-12 12:38 ` [PATCH 4/4] ARM: bcm2835_defconfig: add bcm2835-sdram controller kernel
2016-05-12 14:50 ` [PATCH 0/4] add minimal bcm2835-sdram driver Stefan Wahren
2016-05-12 15:28 ` Martin Sperl
2016-05-12 15:55 ` Stefan Wahren
2016-05-12 16:03 ` Martin Sperl
2016-05-12 18:15 ` Eric Anholt [this message]
2016-05-12 19:46 ` Martin Sperl
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=87twi39m80.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=devicetree@vger.kernel.org \
--cc=kernel@martin.sperl.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®