From: Tero Kristo <t-kristo@ti.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, tony@atomide.com,
nm@ti.com, rnayak@ti.com, bcousson@baylibre.com,
mturquette@linaro.org, linux-arm-kernel@lists.infradead.org,
Anatolij Gustschin <agust@denx.de>
Subject: Re: [PATCHv12 06/49] clk: add support for low level register ops
Date: Tue, 7 Jan 2014 09:44:56 +0200 [thread overview]
Message-ID: <52CBB078.7000607@ti.com> (raw)
In-Reply-To: <52C7141F.2020901@codeaurora.org>
On 01/03/2014 09:48 PM, Stephen Boyd wrote:
> On 01/03/14 01:13, Tero Kristo wrote:
>> On 12/22/2013 07:39 PM, Gerhard Sittig wrote:
>>>
>>>
>>> Further I'd suggest to split this register access aspect out of
>>> the TI clock series, and to prepare it already for regmap style
>>> access to the hardware registers. See the next comment below.
>>
>> This sounds like a good idea to me, seeing it is blocking lots of
>> other things.
>
> This ll_ops struct looks like a simplified regmap. Have you seen my
> series that adds regmap support to the common clock framework[1]? Is
> there any reason why you can't use those patches and layer some patches
> on top to add support for regmap to the basic clock types?
>
> [1] https://lkml.org/lkml/2013/12/23/461
Yea I've seen that. I also used regmap myself on some earlier rev, but
it is rather an overkill solution to my purposes, and it also adds
additional latencies to the register access.
-Tero
WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv12 06/49] clk: add support for low level register ops
Date: Tue, 7 Jan 2014 09:44:56 +0200 [thread overview]
Message-ID: <52CBB078.7000607@ti.com> (raw)
In-Reply-To: <52C7141F.2020901@codeaurora.org>
On 01/03/2014 09:48 PM, Stephen Boyd wrote:
> On 01/03/14 01:13, Tero Kristo wrote:
>> On 12/22/2013 07:39 PM, Gerhard Sittig wrote:
>>>
>>>
>>> Further I'd suggest to split this register access aspect out of
>>> the TI clock series, and to prepare it already for regmap style
>>> access to the hardware registers. See the next comment below.
>>
>> This sounds like a good idea to me, seeing it is blocking lots of
>> other things.
>
> This ll_ops struct looks like a simplified regmap. Have you seen my
> series that adds regmap support to the common clock framework[1]? Is
> there any reason why you can't use those patches and layer some patches
> on top to add support for regmap to the basic clock types?
>
> [1] https://lkml.org/lkml/2013/12/23/461
Yea I've seen that. I also used regmap myself on some earlier rev, but
it is rather an overkill solution to my purposes, and it also adds
additional latencies to the register access.
-Tero
next prev parent reply other threads:[~2014-01-07 7:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 16:34 [PATCHv12 00/49] ARM: TI SoC clock DT conversion Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 01/49] clk: add support for registering clocks from description Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 03/49] clk: divider: add support for registering divider clock from descriptor Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 04/49] clk: mux: add support for registering mux " Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 05/49] clk: gate: add support for registering gate " Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 06/49] clk: add support for low level register ops Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-22 17:39 ` Gerhard Sittig
2013-12-22 17:39 ` Gerhard Sittig
2014-01-03 9:13 ` Tero Kristo
2014-01-03 9:13 ` Tero Kristo
2014-01-03 19:48 ` Stephen Boyd
2014-01-03 19:48 ` Stephen Boyd
2014-01-07 7:44 ` Tero Kristo [this message]
2014-01-07 7:44 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 07/49] clk: divider: add support for low level ops Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-22 17:52 ` Gerhard Sittig
2013-12-22 17:52 ` Gerhard Sittig
2014-01-03 9:17 ` Tero Kristo
2014-01-03 9:17 ` Tero Kristo
2014-01-04 16:48 ` Gerhard Sittig
2014-01-04 16:48 ` Gerhard Sittig
2013-12-20 16:34 ` [PATCHv12 08/49] clk: gate: " Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 09/49] clk: mux: " Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 12/49] CLK: TI: Add DPLL clock support Tero Kristo
2013-12-20 16:34 ` Tero Kristo
[not found] ` <1387557274-22583-1-git-send-email-t-kristo-l0cyMroinI0@public.gmane.org>
2013-12-20 16:34 ` [PATCHv12 11/49] CLK: ti: add init support for clock IP blocks Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 14/49] clk: ti: add composite clock support Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 18/49] CLK: TI: add support for clockdomain binding Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 17/49] CLK: TI: add support for gate clock Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 23/49] CLK: TI: DRA7: Add APLL support Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 16:34 ` [PATCHv12 43/49] ARM: OMAP2+: PRM: add support for initializing PRCM clock modules from DT Tero Kristo
2013-12-20 16:34 ` Tero Kristo
2013-12-20 18:37 ` [PATCHv12 00/49] ARM: TI SoC clock DT conversion Tony Lindgren
2013-12-20 18:37 ` Tony Lindgren
2013-12-20 20:06 ` Felipe Balbi
2013-12-20 20:06 ` Felipe Balbi
2013-12-20 20:10 ` Sebastian Reichel
2013-12-20 20:10 ` Sebastian Reichel
2014-01-07 3:21 ` Nishanth Menon
2014-01-07 3:21 ` Nishanth Menon
2014-01-07 16:36 ` Nishanth Menon
2014-01-07 16:36 ` Nishanth Menon
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=52CBB078.7000607@ti.com \
--to=t-kristo@ti.com \
--cc=agust@denx.de \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=sboyd@codeaurora.org \
--cc=tony@atomide.com \
/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.