linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: Query: clk: Defining new struct clk_foo types
Date: Thu, 5 Apr 2012 11:58:35 +0200	[thread overview]
Message-ID: <20120405095835.GB20478@pengutronix.de> (raw)
In-Reply-To: <4F7D443E.3010800@st.com>

On Thu, Apr 05, 2012 at 12:35:34PM +0530, Viresh Kumar wrote:
> Hi Mike,
> 
> I am doing SPEAr SoCs clock port with common clock framework.
> 
> Currently there are following type of clk_foo implementations present:
> - clk_gate
> - clk_divider
> - clk_fixed_rate
> - clk_mux
> 
> I have few more in my SoC:
> clk with:
> - gate + divider
> - gate + fixed_rate
> - gate + mux
> ...
> 
> How should i go ahead in my implementation for these?
> Should i create SPEAr specific structures or enhance drivers/clk for this?

If you have a gate and a divider then register a gate and a divider.
We don't need clk providers for combination of these, the clock
framework will handle it just fine.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2012-04-05  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  7:05 Query: clk: Defining new struct clk_foo types Viresh Kumar
2012-04-05  9:58 ` Sascha Hauer [this message]
2012-04-05 10:13   ` Viresh Kumar
2012-04-05 10:30     ` Sascha Hauer
2012-04-05 10:40       ` Viresh Kumar
2012-04-05 13:12         ` Sascha Hauer

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=20120405095835.GB20478@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).