From: Tero Kristo <t-kristo@ti.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-omap@vger.kernel.org, mturquette@linaro.org,
paul@pwsan.com, tony@atomide.com, nm@ti.com, rnayak@ti.com,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv2 10/11] ARM: dts: omap4 clock data
Date: Mon, 24 Jun 2013 10:39:49 +0300 [thread overview]
Message-ID: <51C7F7C5.70201@ti.com> (raw)
In-Reply-To: <51C3AB46.4040609@codeaurora.org>
On 06/21/2013 04:24 AM, Stephen Boyd wrote:
> On 06/19/13 06:19, Tero Kristo wrote:
>> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
>> index 2a56428..70608db 100644
>> --- a/arch/arm/boot/dts/omap4.dtsi
>> +++ b/arch/arm/boot/dts/omap4.dtsi
>> @@ -106,6 +106,8 @@
>> ti,hwmods = "counter_32k";
>> };
>>
>> + /include/ "omap4-clocks.dtsi"
>> +
>
> Doesn't this cause one platform device to be allocated for each clock
> node defined in omap4-clocks.dtsi? Are you concerned about wasting
> memory on things that aren't really devices and that will never be probed?
Hi Stephen,
Sounds like a valid point to me, so should this include just go under
the root in omap4.dtsi? I am not quite familiar with DT specifics myself
as of yet.
-Tero
>
>> omap4_pmx_core: pinmux@4a100040 {
>> compatible = "ti,omap4-padconf", "pinctrl-single";
>> reg = <0x4a100040 0x0196>;
>
WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 10/11] ARM: dts: omap4 clock data
Date: Mon, 24 Jun 2013 10:39:49 +0300 [thread overview]
Message-ID: <51C7F7C5.70201@ti.com> (raw)
In-Reply-To: <51C3AB46.4040609@codeaurora.org>
On 06/21/2013 04:24 AM, Stephen Boyd wrote:
> On 06/19/13 06:19, Tero Kristo wrote:
>> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
>> index 2a56428..70608db 100644
>> --- a/arch/arm/boot/dts/omap4.dtsi
>> +++ b/arch/arm/boot/dts/omap4.dtsi
>> @@ -106,6 +106,8 @@
>> ti,hwmods = "counter_32k";
>> };
>>
>> + /include/ "omap4-clocks.dtsi"
>> +
>
> Doesn't this cause one platform device to be allocated for each clock
> node defined in omap4-clocks.dtsi? Are you concerned about wasting
> memory on things that aren't really devices and that will never be probed?
Hi Stephen,
Sounds like a valid point to me, so should this include just go under
the root in omap4.dtsi? I am not quite familiar with DT specifics myself
as of yet.
-Tero
>
>> omap4_pmx_core: pinmux at 4a100040 {
>> compatible = "ti,omap4-padconf", "pinctrl-single";
>> reg = <0x4a100040 0x0196>;
>
next prev parent reply other threads:[~2013-06-24 7:40 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 13:18 [PATCHv2 00/11] ARM: OMAP4 clock data conversion to DT Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 01/11] CLK: clkdev: add support for looking up clocks from DT Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 02/11] CLK: use of_property_read_u32 instead of read_u8 Tero Kristo
2013-06-19 13:18 ` Tero Kristo
[not found] ` <1371647942-4811-3-git-send-email-t-kristo-l0cyMroinI0@public.gmane.org>
2013-06-21 0:57 ` Mike Turquette
2013-06-21 0:57 ` Mike Turquette
2013-06-21 12:45 ` Nishanth Menon
2013-06-21 12:45 ` Nishanth Menon
2013-06-21 16:21 ` Mike Turquette
2013-06-21 16:21 ` Mike Turquette
2013-06-19 13:18 ` [PATCHv2 03/11] CLK: divider: fix table parsing logic for DT Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 04/11] clk: omap: introduce clock driver Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 05/11] CLK: OMAP4: Add DPLL clock support Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 06/11] CLK: omap: move part of the machine specific clock header contents to driver Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-21 7:32 ` Tony Lindgren
2013-06-21 7:32 ` Tony Lindgren
2013-06-24 7:42 ` Tero Kristo
2013-06-24 7:42 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 07/11] ARM: OMAP: clock: add DT duplicate clock registration mechanism Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 08/11] CLK: omap: add autoidle support Tero Kristo
2013-06-19 13:18 ` Tero Kristo
2013-06-19 13:19 ` [PATCHv2 09/11] CLK: omap: add support for OMAP gate clock Tero Kristo
2013-06-19 13:19 ` Tero Kristo
2013-06-19 13:19 ` [PATCHv2 10/11] ARM: dts: omap4 clock data Tero Kristo
2013-06-19 13:19 ` Tero Kristo
2013-06-19 13:30 ` Nishanth Menon
2013-06-19 13:30 ` Nishanth Menon
2013-06-19 13:49 ` Tero Kristo
2013-06-19 13:49 ` Tero Kristo
2013-06-19 13:56 ` Nishanth Menon
2013-06-19 13:56 ` Nishanth Menon
2013-06-21 1:24 ` Stephen Boyd
2013-06-21 1:24 ` Stephen Boyd
2013-06-24 7:39 ` Tero Kristo [this message]
2013-06-24 7:39 ` Tero Kristo
2013-06-19 13:19 ` [PATCHv2 11/11] ARM: OMAP4: register DT clocks and remove old data Tero Kristo
2013-06-19 13:19 ` Tero Kristo
2013-06-21 7:25 ` Tony Lindgren
2013-06-21 7:25 ` Tony Lindgren
2013-06-24 7:45 ` Tero Kristo
2013-06-24 7:45 ` Tero Kristo
2013-06-24 7:50 ` Tony Lindgren
2013-06-24 7:50 ` Tony Lindgren
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=51C7F7C5.70201@ti.com \
--to=t-kristo@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--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.