From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] net: davinci_mdio: enable and disable clock
Date: Thu, 02 Aug 2012 22:17:56 +0200 [thread overview]
Message-ID: <501AE074.8090906@gmail.com> (raw)
In-Reply-To: <20120802195308.GZ6802@n2100.arm.linux.org.uk>
On 02.08.2012 21:53, Russell King - ARM Linux wrote:
> On Thu, Aug 02, 2012 at 09:43:35PM +0200, Daniel Mack wrote:
>> Make the driver control the device clocks. Appearantly, the Davinci
>> platform probes this driver with the clock all powered up, but on OMAP,
>> this isn't the case.
>
> Hmm, this looks like it could do with improvement, especially as we're
> moving everything over to a common clk API.
>
> 1. This driver could do with clk_prepare()/clk_unprepare() calls.
Ok, done.
> 2. This driver should not be making the assumption that NULL means
> it can avoid clk_* calls. It should instead be using
> if (!IS_ERR(clk))
Well spotted. Amended patch below.
Thanks,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-net-davinci_mdio-prepare-and-unprepare-clocks.patch
Type: text/x-patch
Size: 2045 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120802/2fa5d4e5/attachment.bin>
next prev parent reply other threads:[~2012-08-02 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 19:43 [PATCH 1/2] net: davinci_mdio: enable and disable clock Daniel Mack
2012-08-02 19:43 ` [PATCH 2/2] net: davinci_mdio: add DT bindings Daniel Mack
2012-08-02 19:53 ` [PATCH 1/2] net: davinci_mdio: enable and disable clock Russell King - ARM Linux
2012-08-02 20:17 ` Daniel Mack [this message]
2012-08-02 20:20 ` Paul Walmsley
2012-08-02 20:28 ` Daniel Mack
2012-08-03 5:16 ` Vaibhav Hiremath
2012-08-03 5:22 ` Daniel Mack
2012-08-03 5:53 ` Hiremath, Vaibhav
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=501AE074.8090906@gmail.com \
--to=zonque@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).