From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mfd: dbx500-prcmu: Correctly reorder PRCMU clock identifiers
Date: Fri, 7 Jun 2013 15:20:20 +0100 [thread overview]
Message-ID: <20130607142020.GB24958@gmail.com> (raw)
In-Reply-To: <CACRpkdYLB-_JjEd69vVub_Z3L+avQRrFBt1fGuyR0D_owcLWvA@mail.gmail.com>
On Fri, 07 Jun 2013, Linus Walleij wrote:
> On Thu, Jun 6, 2013 at 1:21 PM, Lee Jones <lee.jones@linaro.org> wrote:
>
> > ... as stipulated by the Hardware Specification document.
> >
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
>
> I think you need Ulf (as ux500 clock author) and Loic (as PRCMU
> developer) to have a look at this.
>
> > -enum prcmu_clock {
> > - PRCMU_SGACLK,
> (...)
> > +#define ARMCLK 0
> > +#define PRCMU_ACLK 1
> (...)
>
> It seems the enum and the defines want to do two different things?
>
> The first is a kernel-internal representation of the clocks, whereas
> the latter is a HW-centric representation for a certain PRCMU
> variant (I guess?)
>
> Does one actually exclude the other?
>From what I can tell, they're non-ordered values which are used as
read-ins to the clk_mgt array. So long as they are unique I'm not sure
the order matters. The current order seems 'made up', unless I'm
mistaken.
I agree that Ulf should take a look and confirm/deny my findings.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-06-07 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 11:21 [PATCH 0/4] Unrelated fixes found while DT:ing clocks Lee Jones
2013-06-06 11:21 ` [PATCH 1/4] mfd: dbx500-prcmu: Use correct names for clock management registers Lee Jones
2013-06-07 13:09 ` Linus Walleij
2013-06-06 11:21 ` [PATCH 2/4] mfd: dbx500-prcmu: Correctly reorder PRCMU clock identifiers Lee Jones
2013-06-07 13:13 ` Linus Walleij
2013-06-07 14:20 ` Lee Jones [this message]
2013-06-10 10:54 ` Linus Walleij
2013-06-06 11:21 ` [PATCH 3/4] ARM: ux500: Fix trivial whitespace/tabbing issue Lee Jones
2013-06-07 13:15 ` Linus Walleij
2013-06-06 11:21 ` [PATCH 4/4] ARM: ux500: Remove call to u8500_of_init_devices() - again Lee Jones
2013-06-06 15:58 ` Arnd Bergmann
2013-06-06 16:50 ` Lee Jones
2013-06-06 19:35 ` Arnd Bergmann
2013-06-07 7:47 ` Linus Walleij
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=20130607142020.GB24958@gmail.com \
--to=lee.jones@linaro.org \
--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).