All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Jensen <jonas.jensen@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"arm@kernel.org" <arm@kernel.org>,
	"mturquette@linaro.org" <mturquette@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] clk: add MOXA ART SoCs clock driver
Date: Thu, 18 Jul 2013 12:36:40 +0200	[thread overview]
Message-ID: <CACmBeS2SnpiUtiQD6j9qyaXZ5-chHSHVeo4c5=UhitVonvkKtw@mail.gmail.com> (raw)
In-Reply-To: <20130718095035.GA29153@e106331-lin.cambridge.arm.com>

Hi Mark, thanks for taking a look at this.

On 18 July 2013 11:50, Mark Rutland <mark.rutland@arm.com> wrote:
> This confuses me. moxart_of_clk_init gets called because there was a
> "moxa,moxart-core-clock", node in the dt, but the driver only seems to
> use the information to figure out the configuration of another clock
> ("moxa,moxart-apb-clock"), and never registers a clock specifically for
> the core-clock.
>
> I couldn't find "moxa,moxart-apb-clock" described in mainline. COuld you
> describe the relationship between core-clock and apb-clock?

It's true core-clock exist only so the register can be mapped.

apb-clock is part of a patch set that will add new device tree files for the
MOXA ART SoC, but it's not in mainline:

http://lists.infradead.org/pipermail/linux-arm-kernel/2013-July/181757.html

apb-clock could be a fixed rate 48MHz DT only clock, but because we can't
be sure it's 48MHz on all platforms, reading it from a register with core-clock
is more portable.


Best regards,
Jonas

WARNING: multiple messages have this Message-ID (diff)
From: jonas.jensen@gmail.com (Jonas Jensen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] clk: add MOXA ART SoCs clock driver
Date: Thu, 18 Jul 2013 12:36:40 +0200	[thread overview]
Message-ID: <CACmBeS2SnpiUtiQD6j9qyaXZ5-chHSHVeo4c5=UhitVonvkKtw@mail.gmail.com> (raw)
In-Reply-To: <20130718095035.GA29153@e106331-lin.cambridge.arm.com>

Hi Mark, thanks for taking a look at this.

On 18 July 2013 11:50, Mark Rutland <mark.rutland@arm.com> wrote:
> This confuses me. moxart_of_clk_init gets called because there was a
> "moxa,moxart-core-clock", node in the dt, but the driver only seems to
> use the information to figure out the configuration of another clock
> ("moxa,moxart-apb-clock"), and never registers a clock specifically for
> the core-clock.
>
> I couldn't find "moxa,moxart-apb-clock" described in mainline. COuld you
> describe the relationship between core-clock and apb-clock?

It's true core-clock exist only so the register can be mapped.

apb-clock is part of a patch set that will add new device tree files for the
MOXA ART SoC, but it's not in mainline:

http://lists.infradead.org/pipermail/linux-arm-kernel/2013-July/181757.html

apb-clock could be a fixed rate 48MHz DT only clock, but because we can't
be sure it's 48MHz on all platforms, reading it from a register with core-clock
is more portable.


Best regards,
Jonas

  reply	other threads:[~2013-07-18 10:40 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 14:03 [PATCH] clk: add MOXA ART SoCs clock driver Jonas Jensen
2013-06-27 14:03 ` Jonas Jensen
2013-07-04 13:08 ` [PATCH v2] " Jonas Jensen
2013-07-04 13:08   ` Jonas Jensen
2013-07-17 13:23   ` [PATCH v3] " Jonas Jensen
2013-07-17 13:23     ` Jonas Jensen
2013-07-18  9:50     ` Mark Rutland
2013-07-18  9:50       ` Mark Rutland
2013-07-18 10:36       ` Jonas Jensen [this message]
2013-07-18 10:36         ` Jonas Jensen
2013-07-18 11:02         ` Mark Rutland
2013-07-18 11:02           ` Mark Rutland
2013-07-18 11:55           ` Jonas Jensen
2013-07-18 11:55             ` Jonas Jensen
2013-07-18 13:56             ` Mark Rutland
2013-07-18 13:56               ` Mark Rutland
2013-07-18 14:25               ` Jonas Jensen
2013-07-18 14:25                 ` Jonas Jensen
2013-07-19  8:07     ` [PATCH v4] " Jonas Jensen
2013-07-19  8:07       ` Jonas Jensen
2013-07-19  8:17       ` [PATCH v5] " Jonas Jensen
2013-07-19  8:17         ` Jonas Jensen
2013-07-22  9:21         ` Mark Rutland
2013-07-22  9:21           ` Mark Rutland
2013-07-23  8:09           ` Tomasz Figa
2013-07-23  8:09             ` Tomasz Figa
2013-07-26 22:32             ` Mike Turquette
2013-07-26 22:32               ` Mike Turquette
2013-07-29  9:44         ` [PATCH v6] " Jonas Jensen
2013-07-29  9:44           ` Jonas Jensen
2013-10-07  4:47           ` Mike Turquette
2013-10-07  4:47             ` Mike Turquette
2013-10-09 14:54           ` [PATCH v7] " Jonas Jensen
2013-10-09 14:54             ` Jonas Jensen
2013-11-01 18:13             ` Sylwester Nawrocki
2013-11-01 18:13               ` Sylwester Nawrocki
2013-12-09 15:16             ` [PATCH v8] " Jonas Jensen
2013-12-09 15:16               ` Jonas Jensen
2014-01-17 15:03               ` [PATCH v9] " Jonas Jensen
2014-01-17 15:03                 ` Jonas Jensen
2014-01-17 15:17                 ` Sudeep Holla
2014-01-17 15:17                   ` Sudeep Holla
2014-01-17 15:17                   ` Sudeep Holla
2014-01-21 12:44                 ` [PATCH v10] " Jonas Jensen
2014-01-21 12:44                   ` Jonas Jensen
2014-01-21 12:44                   ` Jonas Jensen
2014-01-27 10:20                   ` Mark Rutland
2014-01-27 10:20                     ` Mark Rutland
2014-01-27 10:20                     ` Mark Rutland
2014-01-28 11:09                   ` [PATCH v11] " Jonas Jensen
2014-01-28 11:09                     ` Jonas Jensen
2014-01-28 11:09                     ` Jonas Jensen
2014-03-13 20:27                     ` Mike Turquette
2014-03-13 20:27                       ` Mike Turquette

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='CACmBeS2SnpiUtiQD6j9qyaXZ5-chHSHVeo4c5=UhitVonvkKtw@mail.gmail.com' \
    --to=jonas.jensen@gmail.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@linaro.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.