mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Rizzo <elpa.rizzo@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
	ben-linux@fluff.org, linux-api@vger.kernel.org
Subject: Re: [PATCH 1/2] User access to internal clocks
Date: Mon, 9 Feb 2009 19:54:57 +0100	[thread overview]
Message-ID: <8447d6730902091054x7c4c842m7339382e19260bd8@mail.gmail.com> (raw)
In-Reply-To: <8447d6730902091017m21cb30d0w6be6fbbbf33db4f3@mail.gmail.com>

> What about adding a dedicated function to clk api that registers a struct clk
>  in a linked list and associates it with a name, with the only specific purpose
>  to enumerate and list (and possibly change rate and parents) all
> clocks in sysfs ?
> Obviously only specifically registered clocks will be visible in sysfs...
>

Or better, only proposed functions:
int clk_for_each(int(*fn)(struct clk *, void *), void *data)
and
const char *clk_sysname(struct clk *)
need to be added to clk api, the function to register the struct clk
in the linked list could be implementation specific.
Maybe a function like this:
struct clk *clk_get_by_sysname(const char *sysname);
could be useful to be added to api interface, too ?

  reply	other threads:[~2009-02-09 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 17:04 Davide Rizzo
2009-02-09 17:10 ` Russell King - ARM Linux
2009-02-09 17:44   ` Davide Rizzo
2009-02-09 17:55     ` Russell King - ARM Linux
2009-02-09 18:17       ` Davide Rizzo
2009-02-09 18:54         ` Davide Rizzo [this message]
2009-02-09 19:01           ` Russell King - ARM Linux
2009-02-09 21:06             ` Davide Rizzo
2009-02-09 17:12 ` Hans J. Koch
2009-02-09 18:12 ` Russell King - ARM Linux

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=8447d6730902091054x7c4c842m7339382e19260bd8@mail.gmail.com \
    --to=elpa.rizzo@gmail.com \
    --cc=ben-linux@fluff.org \
    --cc=gregkh@suse.de \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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®