linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv4 30/35] ARM: dts: omap4: add system control module node
Date: Fri, 20 Mar 2015 08:40:09 +0200	[thread overview]
Message-ID: <550BC0C9.4030305@ti.com> (raw)
In-Reply-To: <20150319202533.GL31346@atomide.com>

On 03/19/2015 10:25 PM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [150318 14:35]:
>> * Tero Kristo <t-kristo@ti.com> [150318 07:45]:
>>> --- a/arch/arm/boot/dts/omap4.dtsi
>>> +++ b/arch/arm/boot/dts/omap4.dtsi
>>> @@ -167,36 +167,65 @@
>>> +		scm: scm@4a002000 {
>>> +			compatible = "ti,omap4-ctrl", "simple-bus";
>>> +			reg = <0x4a002000 0x1000>,
>>> +			      <0x4a100000 0x1000>;
>>> +			#address-cells = <2>;
>>> +			#size-cells = <1>;
>>> +			ranges = <0 0 0x4a002000 0x1000>,
>>> +				 <1 0 0x4a100000 0x1000>;
>>
>> Oops I still have a bit of an issue with this, sorry I should have
>> been more clear last time.
>>
>> Now it's hard to figure out which children belong to l4_cfg and which
>> ones to l4_wkup. I suggest we set them up as completely separate blocks
>> as that's what they are.
>>
>> Below is an example of what I think things should look like for omap4,
>> maybe take a look at that and see if that makes sense for you?
>>
>> It may need to be patched in separate parts to keep the patches readable
>> though :)
>
> The example I posted has some l4_cfg vs SCM confusion as pointed out by
> Tero while we chatted about it. Also l4_wkup is a child of l4_cfg on
> omap4, while on omap5 they are separate.
>
> Below are some examples of what we came up with that now follows omap4460
> TRM "Figure 2-1. Interconnect Overview" and "Table 2-3. L4_CFG Memory
> Space Mapping". Also an example for omap3 is included.
>
> Tero, maybe just do the minimal changes for now as we don't need to move
> all of it at once?

Yes, I will be looking at this today.

-Tero

>
> Regards,
>
> Tony
>
>
> Example for omap4.dtsi, which ocp being the l3 interconnect:
>
> 	ocp {
> 		compatible = "ti,omap4-l3-noc", "simple-bus";
> 		#address-cells = <1>;
> 		#size-cells = <1>;
> 		ranges;
> 		ti,hwmods = "l3_main_1", "l3_main_2", "l3_main_3";
> 		reg = <0x44000000 0x1000>,
> 		      <0x44800000 0x2000>,
> 		      <0x45000000 0x1000>;
> 		interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>,
> 			     <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;
>
> 		l4_cfg: l4@4a000000 {
> 			compatible = "ti,omap4-l4-cfg", "simple-bus";
> 			#address-cells = <1>;
> 			#size-cells = <1>;
> 			ranges = <0 0x4a000000 0x1000000>;
>
> 			cm1: cm1@4000 {
> 				compatible = "ti,omap4-cm1";
> 				reg = <0x4000 0x2000>;
>
> 				cm1_clocks: clocks {
> 					#address-cells = <1>;
> 					#size-cells = <0>;
> 				};
>
> 				cm1_clockdomains: clockdomains {
> 				};
> 			};
>
> 			cm2: cm2@8000 {
> 				compatible = "ti,omap4-cm2";
> 				reg = <0x8000 0x3000>;
>
> 				cm2_clocks: clocks {
> 					#address-cells = <1>;
> 					#size-cells = <0>;
> 				};
>
> 				cm2_clockdomains: clockdomains {
> 				};
> 			};
>
> 			omap4_scm_core: scm@100000 {
> 				compatible = "ti,omap4-scm-core", "simple-bus";
> 				#address-cells = <1>;
> 				#size-cells = <1>;
> 				ranges = <0 0x100000 0x1000>;
>
> 				omap4_pmx_core: pinmux@40 {
> 					compatible = "ti,omap4-padconf", "pinctrl-single";
> 					reg = <0x40 0x0196>;
> 					#address-cells = <1>;
> 					#size-cells = <0>;
> 					#interrupt-cells = <1>;
> 					interrupt-controller;
> 					pinctrl-single,register-width = <16>;
> 					pinctrl-single,function-mask = <0x7fff>;
> 				};
>
> 				omap4_padconf_global: tisyscon@5a0 {
> 					compatible = "syscon";
> 					reg = <0x5a0 0x170>;
> 					#address-cells = <1>;
> 					#size-cells = <1>;
>
> 					pbias_regulator: pbias_regulator {
> 						compatible = "ti,pbias-omap";
> 						reg = <0x60 0x4>;
> 						syscon = <&omap4_padconf_global>;
> 						pbias_mmc_reg: pbias_mmc_omap4 {
> 							regulator-name = "pbias_mmc_omap4";
> 							regulator-min-microvolt = <1800000>;
> 							regulator-max-microvolt = <3000000>;
> 						};
> 					};
> 				};
> 			};
>
> 			l4_wkup: l4@300000 {
> 				compatible = "ti,omap4-l4-wkup", "simple-bus";
> 				#address-cells = <1>;
> 				#size-cells = <1>;
> 				ranges = <0 0x300000 0x40000>;
>
> 				counter32k: counter@4000 {
> 					compatible = "ti,omap-counter32k";
> 					reg = <0x4000 0x20>;
> 					ti,hwmods = "counter_32k";
> 				};
>
> 				prm: prm@6000 {
> 					compatible = "ti,omap4-prm";
> 					reg = <0x6000 0x3000>;
> 					interrupts = <GIC_SPI 11 IRQ_TYPE_LEVEL_HIGH>;
>
> 					prm_clocks: clocks {
> 						#address-cells = <1>;
> 						#size-cells = <0>;
> 					};
>
> 					prm_clockdomains: clockdomains {
> 					};
> 				};
>
> 				scrm: scrm@a000 {
> 					compatible = "ti,omap4-scrm";
> 					reg = <0xa000 0x2000>;
> 					#address-cells = <1>;
> 					#size-cells = <1>;
> 					ranges = <0 0xa000 0x2000>;
>
> 					scrm_clocks: clocks {
> 						#address-cells = <1>;
> 						#size-cells = <0>;
> 					};
>
> 					scrm_clockdomains: clockdomains {
> 					};
> 				};
>
> 				omap4_pmx_wkup: pinmux@1e040 {
> 					compatible = "ti,omap4-padconf", "pinctrl-single";
> 					reg = <0x1e040 0x0038>;
> 					#address-cells = <1>;
> 					#size-cells = <0>;
> 					#interrupt-cells = <1>;
> 					interrupt-controller;
> 					pinctrl-single,register-width = <16>;
> 					pinctrl-single,function-mask = <0x7fff>;
> 				};
> 			};
> 		};
> 	...
> 	};
>
>
> Example for omap3.dtsi with ocp being the l3 interconnect:
>
> 	ocp {
> 		compatible = "ti,omap3-l3-smx", "simple-bus";
> 		reg = <0x68000000 0x10000>;
> 		interrupts = <9 10>;
> 		#address-cells = <1>;
> 		#size-cells = <1>;
> 		ranges;
> 		ti,hwmods = "l3_main";
>
> 		...
>
> 		l4_core: l4@48000000 {
> 			compatible = "ti,omap3-l4-core", "simple-bus";
> 			#address-cells = <1>;
> 			#size-cells = <1>;
> 			ranges = <0 0x48000000 0x1000000>;
>
> 			scrm: scrm@48002000 {
> 				compatible = "ti,omap3-scrm", "simple-bus";
> 				reg = <0x2000 0x2000>;
> 				#address-cells = <1>;
> 				#size-cells = <1>;
> 				ranges = <0 0x2000 0x2000>;
>
> 				omap3_pmx_core: pinmux@30 {
> 					compatible = "ti,omap3-padconf", "pinctrl-single";
> 					reg = <0x30 0x0238>;
> 					#address-cells = <1>;
> 					#size-cells = <0>;
> 					#interrupt-cells = <1>;
> 					interrupt-controller;
> 					pinctrl-single,register-width = <16>;
> 					pinctrl-single,function-mask = <0xff1f>;
> 				};
>
> 				scm_conf: tisyscon@270 {
> 					compatible = "syscon";
> 					reg = <0x270 0x2f0>;
> 					#address-cells = <1>;
> 					#size-cells = <1>;
>
> 					pbias_regulator: pbias_regulator {
> 						compatible = "ti,pbias-omap";
> 						reg = <0x2b0 0x4>;
> 						syscon = <&scm_conf>;
> 						pbias_mmc_reg: pbias_mmc_omap2430 {
> 							regulator-name = "pbias_mmc_omap2430";
> 							regulator-min-microvolt = <1800000>;
> 							regulator-max-microvolt = <3000000>;
> 						};
> 					};
> 				};
>
> 				omap3_pmx_wkup: pinmux@a00 {
> 					compatible = "ti,omap3-padconf", "pinctrl-single";
> 					reg = <0xa00 0x5c>;
> 					#address-cells = <1>;
> 					#size-cells = <0>;
> 					#interrupt-cells = <1>;
> 					interrupt-controller;
> 					pinctrl-single,register-width = <16>;
> 					pinctrl-single,function-mask = <0xff1f>;
> 				};
>
> 				scrm_clocks: clocks {
> 					#address-cells = <1>;
> 					#size-cells = <0>;
> 				};
>
> 				scrm_clockdomains: clockdomains {
> 				};
> 			};
> 		};
> 		...
> 	};
>


  reply	other threads:[~2015-03-20  6:40 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 14:43 [PATCHv4 00/35] ARM: OMAP2+: PRCM / SCM cleanups against 4.0-rc1 Tero Kristo
2015-03-18 14:43 ` [PATCHv4 01/35] ARM: OMAP2+: PRCM: rename of_prcm_init to omap_prcm_init Tero Kristo
2015-03-18 14:43 ` [PATCHv4 02/35] ARM: OMAP3: PRM: invert the wkst_mask for the prm_clear_mod_irqs Tero Kristo
2015-03-18 14:43 ` [PATCHv4 03/35] ARM: OMAP2+: PRM: add generic API for clear_mod_irqs Tero Kristo
2015-03-18 14:43 ` [PATCHv4 04/35] ARM: OMAP3+: PRM: add common APIs for prm_vp_check/clear_txdone Tero Kristo
2015-03-18 14:43 ` [PATCHv4 05/35] ARM: OMAP4+: PRM: move omap_prm_base_init under OMAP4 PRM driver Tero Kristo
2015-03-18 14:43 ` [PATCHv4 06/35] ARM: OMAP4+: CM: move omap_cm_base_init under OMAP4 CM driver Tero Kristo
2015-03-18 14:43 ` [PATCHv4 07/35] ARM: OMAP4: PRM: move omap4xxx_prm_init earlier in init order Tero Kristo
2015-03-18 14:43 ` [PATCHv4 08/35] clk: ti: fix ti_clk_get_reg_addr error handling Tero Kristo
2015-03-18 14:43 ` [PATCHv4 09/35] Documentation: DT: document PRCM compatible strings for dm81x SoCs Tero Kristo
2015-03-18 14:43 ` [PATCHv4 10/35] ARM: OMAP2+: PRCM: add support for static clock memmap indices Tero Kristo
2015-03-18 14:43 ` [PATCHv4 11/35] ARM: OMAP2+: clock: move clock provider infrastructure to clock driver Tero Kristo
2015-03-18 14:43 ` [PATCHv4 12/35] ARM: OMAP2+: PRCM: split PRCM module init to their own driver files Tero Kristo
2015-03-18 14:43 ` [PATCHv4 13/35] ARM: OMAP2+: CM: determine CM base address from device tree Tero Kristo
2015-03-18 14:43 ` [PATCHv4 14/35] ARM: OMAP2+: PRM: determine PRM " Tero Kristo
2015-03-18 14:44 ` [PATCHv4 15/35] ARM: OMAP2+: control: determine control module base address from DT Tero Kristo
2015-03-18 14:44 ` [PATCHv4 16/35] ARM: OMAP2+: PRM: move SoC specific init calls within a generic API Tero Kristo
2015-03-18 14:44 ` [PATCHv4 17/35] ARM: OMAP4+: PRM: determine prm_device_inst based on DT compatibility Tero Kristo
2015-03-18 14:44 ` [PATCHv4 18/35] ARM: OMAP2+: CM: move SoC specific init calls within a generic API Tero Kristo
2015-03-18 14:44 ` [PATCHv4 19/35] ARM: OMAP4+: PRM: setup prm_features from the PRM init time flags Tero Kristo
2015-03-18 14:44 ` [PATCHv4 20/35] ARM: OMAP4+: PRM: get rid of cpu_is_omap44xx calls from interrupt init Tero Kristo
2015-03-18 14:44 ` [PATCHv4 21/35] ARM: OMAP2+: clock: add low-level support for regmap Tero Kristo
2015-03-18 14:44 ` [PATCHv4 22/35] ARM: OMAP2+: control: remove API for getting control module base address Tero Kristo
2015-03-18 14:44 ` [PATCHv4 23/35] ARM: OMAP2+: id: cache omap_type value Tero Kristo
2015-03-18 18:24   ` Sergei Shtylyov
2015-03-19  7:23     ` Tero Kristo
2015-03-18 14:44 ` [PATCHv4 24/35] ARM: OMAP2+: control: add syscon support for register accesses Tero Kristo
2015-03-18 14:44 ` [PATCHv4 25/35] ARM: dts: omap24xx: merge control module features under scrm node Tero Kristo
2015-03-18 14:44 ` [PATCHv4 26/35] ARM: dts: omap3: " Tero Kristo
2015-03-18 14:44 ` [PATCHv4 27/35] ARM: dts: am33xx: " Tero Kristo
2015-03-18 14:44 ` [PATCHv4 28/35] ARM: dts: am43xx-epos-evm: fix pinmux node layout Tero Kristo
2015-03-18 14:44 ` [PATCHv4 29/35] ARM: dts: am4372: merge control module features under scrm node Tero Kristo
2015-03-18 14:44 ` [PATCHv4 30/35] ARM: dts: omap4: add system control module node Tero Kristo
2015-03-18 21:30   ` Tony Lindgren
2015-03-19 20:25     ` Tony Lindgren
2015-03-20  6:40       ` Tero Kristo [this message]
2015-03-18 14:44 ` [PATCHv4 31/35] ARM: OMAP4: display: convert display to use syscon for dsi muxing Tero Kristo
2015-03-18 14:44 ` [PATCHv4 32/35] ARM: OMAP4+: control: remove support for legacy pad read/write Tero Kristo
2015-03-18 14:44 ` [PATCHv4 33/35] ARM: dts: omap5: add system control module node Tero Kristo
2015-03-18 14:44 ` [PATCHv4 34/35] ARM: dts: dra7: " Tero Kristo
2015-03-18 14:44 ` [PATCHv4 35/35] ARM: OMAP4+: control: add support for initializing control module via DT Tero Kristo
2015-03-18 22:07 ` [PATCHv4 00/35] ARM: OMAP2+: PRCM / SCM cleanups against 4.0-rc1 Tony Lindgren
2015-03-19  7:48   ` Tero Kristo
2015-03-19 16:10     ` Tony Lindgren
2015-03-19  0:00 ` Sakari Ailus
2015-03-19  8:05   ` Tero Kristo

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=550BC0C9.4030305@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --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 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).