All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] dm: clk: Add a way to find a clock by its driver
Date: Mon, 18 Jul 2016 10:23:37 -0600	[thread overview]
Message-ID: <578D0289.3030802@wwwdotorg.org> (raw)
In-Reply-To: <1468790598-21133-1-git-send-email-sjg@chromium.org>

On 07/17/2016 03:23 PM, Simon Glass wrote:
> Some SoCs have a single clock device. Provide a way to find it given its
> driver name. This is handled by the linker so will fail if the name is not
> found, avoiding strange errors when names change and do not match. It is
> also faster than a string comparison.

The code looks plausible, but the commit subject and description imply 
this has something to do with clocks, whereas it doesn't; it seems to be 
a generic/core DM function.

  parent reply	other threads:[~2016-07-18 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17 21:23 [U-Boot] [PATCH 1/4] dm: clk: Add a way to find a clock by its driver Simon Glass
2016-07-17 21:23 ` [U-Boot] [PATCH 2/4] rockchip: Add a way to obtain the main clock device Simon Glass
2016-07-18 12:16   ` Simon Glass
2016-07-17 21:23 ` [U-Boot] [PATCH 3/4] rockchip: Use rockchip_get_clk() to obtain the SoC clock Simon Glass
2016-07-17 22:17   ` Anatolij Gustschin
2016-07-18 12:16     ` Simon Glass
2016-07-17 21:23 ` [U-Boot] [PATCH 4/4] rockchip: rk3288: Move rockchip_get_cru() out of the driver Simon Glass
2016-07-18 12:16 ` [U-Boot] [PATCH 1/4] dm: clk: Add a way to find a clock by its driver Simon Glass
2016-07-18 16:23 ` Stephen Warren [this message]
2016-08-01  1:01   ` Simon Glass

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=578D0289.3030802@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.