[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87twi39m80.fsf@eliezer.anholt.net>
Date: Thu, 12 May 2016 11:15:27 -0700
From: Eric Anholt <eric@...olt.net>
To: kernel@...tin.sperl.org, Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Stephen Warren <swarren@...dotorg.org>,
Lee Jones <lee@...nel.org>,
Russell King <linux@....linux.org.uk>,
devicetree@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: Martin Sperl <kernel@...tin.sperl.org>
Subject: Re: [PATCH 0/4] add minimal bcm2835-sdram driver
kernel@...tin.sperl.org writes:
> From: Martin Sperl <kernel@...tin.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.
Download attachment "signature.asc" of type "application/pgp-signature" (819 bytes)
Powered by blists - more mailing lists