All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Francesco VIRLINZI <francesco.virlinzi@st.com>,
	Jeremy Kerr <jeremy.kerr@canonical.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC,PATCH 1/7 v2] Add a common struct clk
Date: Tue, 12 Jan 2010 14:24:04 +0000	[thread overview]
Message-ID: <20100112142404.GD18532@trinity.fluff.org> (raw)
In-Reply-To: <20100112090149.GB26435@n2100.arm.linux.org.uk>

On Tue, Jan 12, 2010 at 09:01:49AM +0000, Russell King - ARM Linux wrote:
> On Tue, Jan 12, 2010 at 09:48:44AM +0100, Francesco VIRLINZI wrote:
> > Hi Jeremy
> > In November I already sent a proposal on
> >  a generic linux clk framework.
> > On that I would suggest:
> >
> >>
> >> +struct clk {
> >> +	const struct clk_operations *ops;
> >>    
> >            spinlock_t lock;
> >            const char *name;
> >            int id;
> 
> Name and ID are totally pointless, unless you insist on using the clk
> API in the wrong way (like S3C does.)

I do intend to change the clock lookup on the Samsung series, but we're
currently in the process of trying to do a whole pile of work on not
only adding new SoCs but also cleaning up the existing support and making
a whole pile of code common to all the Samsung SoC family.

I never got the time to go throughly through Francesco's clock framework
but it seemed rathe rcomplicated for our current requirements and also
had a whole pile of style problems that made it really difficult to read.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC,PATCH 1/7 v2] Add a common struct clk
Date: Tue, 12 Jan 2010 14:24:04 +0000	[thread overview]
Message-ID: <20100112142404.GD18532@trinity.fluff.org> (raw)
In-Reply-To: <20100112090149.GB26435@n2100.arm.linux.org.uk>

On Tue, Jan 12, 2010 at 09:01:49AM +0000, Russell King - ARM Linux wrote:
> On Tue, Jan 12, 2010 at 09:48:44AM +0100, Francesco VIRLINZI wrote:
> > Hi Jeremy
> > In November I already sent a proposal on
> >  a generic linux clk framework.
> > On that I would suggest:
> >
> >>
> >> +struct clk {
> >> +	const struct clk_operations *ops;
> >>    
> >            spinlock_t lock;
> >            const char *name;
> >            int id;
> 
> Name and ID are totally pointless, unless you insist on using the clk
> API in the wrong way (like S3C does.)

I do intend to change the clock lookup on the Samsung series, but we're
currently in the process of trying to do a whole pile of work on not
only adding new SoCs but also cleaning up the existing support and making
a whole pile of code common to all the Samsung SoC family.

I never got the time to go throughly through Francesco's clock framework
but it seemed rathe rcomplicated for our current requirements and also
had a whole pile of style problems that made it really difficult to read.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2010-01-12 14:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12  6:58 [RFC,PATCH 0/7 v2] Common struct clk implementation Jeremy Kerr
2010-01-12  6:58 ` Jeremy Kerr
2010-01-12  6:58 ` [RFC,PATCH 3/7 v2] arm/versatile: use generic struct clk Jeremy Kerr
2010-01-12  6:58   ` Jeremy Kerr
2010-01-12 16:25   ` Russell King - ARM Linux
2010-01-12 16:25     ` Russell King - ARM Linux
2010-01-12 16:25     ` Russell King - ARM Linux
2010-01-25  0:35     ` Jeremy Kerr
2010-01-25  0:35       ` Jeremy Kerr
2010-01-25  0:35       ` Jeremy Kerr
2010-01-12  6:58 ` [RFC,PATCH 2/7 v2] Generic support for fixed-rate clocks Jeremy Kerr
2010-01-12  6:58   ` Jeremy Kerr
2010-01-12  6:58 ` [RFC, PATCH 6/7 v2] arm/icst307: use common struct clk, unify realview and versatile clocks Jeremy Kerr
2010-01-12  6:58   ` Jeremy Kerr
2010-01-12  6:58 ` [RFC,PATCH 4/7 v2] arm/versatile: remove oscoff from clk_versatile Jeremy Kerr
2010-01-12  6:58   ` Jeremy Kerr
2010-01-12  6:58 ` [RFC,PATCH 7/7 v2] arm/icst307: remove icst307_ps_to_vco Jeremy Kerr
2010-01-12  6:58   ` Jeremy Kerr
2010-01-12  6:58 ` [RFC,PATCH 5/7 v2] arm/realview: use generic struct clk Jeremy Kerr
2010-01-12  6:58   ` Jeremy Kerr
2010-01-12  6:58 ` [RFC,PATCH 1/7 v2] Add a common " Jeremy Kerr
2010-01-12  6:58   ` Jeremy Kerr
2010-01-12  8:48   ` Francesco VIRLINZI
2010-01-12  8:48     ` Francesco VIRLINZI
2010-01-12  8:48     ` Francesco VIRLINZI
2010-01-12  9:01     ` Russell King - ARM Linux
2010-01-12  9:01       ` Russell King - ARM Linux
2010-01-12 14:24       ` Ben Dooks [this message]
2010-01-12 14:24         ` Ben Dooks
2010-01-12 14:27       ` Ben Dooks
2010-01-12 14:27         ` Ben Dooks
2010-01-12 14:30   ` Ben Dooks
2010-01-12 14:30     ` Ben Dooks
2010-01-12 14:30     ` Ben Dooks
2010-01-12  9:13 ` [RFC,PATCH 0/7 v2] Common struct clk implementation Russell King - ARM Linux
2010-01-12  9:13   ` Russell King - ARM Linux
2010-01-12  9:13   ` Russell King - ARM Linux
2010-01-13  1:17   ` Jeremy Kerr
2010-01-13  1:17     ` Jeremy Kerr
2010-01-13  1:17     ` Jeremy Kerr

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=20100112142404.GD18532@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=francesco.virlinzi@st.com \
    --cc=jeremy.kerr@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.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 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.