From: Kishon Vijay Abraham I <kishon@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org, bcousson@baylibre.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
nsekhar@ti.com, linux@arm.linux.org.uk
Subject: Re: [PATCH v2 1/4] ARM: dts: dra7: Add dt node for the sycon pcie
Date: Tue, 13 Oct 2015 03:35:07 +0530 [thread overview]
Message-ID: <561C2E93.3020809@ti.com> (raw)
In-Reply-To: <20151012220322.GF23801@atomide.com>
Hi,
On Tuesday 13 October 2015 03:33 AM, Tony Lindgren wrote:
> * Kishon Vijay Abraham I <kishon@ti.com> [151012 14:50]:
>> Hi Tony,
>>
>> On Tuesday 13 October 2015 02:51 AM, Tony Lindgren wrote:
>>> * Kishon Vijay Abraham I <kishon@ti.com> [150915 06:37]:
>>>> Add new device tree node for the control module register space where
>>>> PCIe registers are present.
>>>>
>>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>>> ---
>>>> arch/arm/boot/dts/dra7.dtsi | 5 +++++
>>>> 1 file changed, 5 insertions(+)
>>>>
>>>> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
>>>> index 5d65db9..0769b5d 100644
>>>> --- a/arch/arm/boot/dts/dra7.dtsi
>>>> +++ b/arch/arm/boot/dts/dra7.dtsi
>>>> @@ -154,6 +154,11 @@
>>>> compatible = "syscon";
>>>> reg = <0x1c04 0x0020>;
>>>> };
>>>> +
>>>> + scm_conf_pcie: tisyscon@1c24 {
>>>> + compatible = "syscon";
>>>> + reg = <0x1c24 0x0024>;
>>>> + };
>>>> };
>>>>
>>>> cm_core_aon: cm_core_aon@5000 {
>>>
>>>
>>> Why don't you just extend the existing scm_conf1 area? This is not all pcie
>>> specific for scm_conf_pcie, at least for PLLEN_CONTROL, RMII_CLK_SETTING
>>> and MUXSEL_32K_CLKIN.
>>
>> scm_conf_pcie has only PCIe registers (it starts at 0x4A003C24).
>> PLLEN_CONTROL and others are at 0x4A003C14 as per
>> DRA75x_DRA74x_SR1.1_NDA_TRM_vW.
>
> Oh sorry I guess I was looking at a wrong address then.
>
>> Since PCIe itself has a bunch of registers for itself, thought of
>> creating a separate dt node. But I can extend scm_conf1 area.
>
> Why not just ioremap them then? Do these need to be shared with
> some other driver?
yeah, some are used by PCIe controller driver and some are used by PCIe
PHY driver.
Thanks
Kishon
next prev parent reply other threads:[~2015-10-12 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 13:33 [PATCH v2 0/4] ARM: dts: use syscon property instead of ctrl-module Kishon Vijay Abraham I
2015-09-15 13:33 ` [PATCH v2 1/4] ARM: dts: dra7: Add dt node for the sycon pcie Kishon Vijay Abraham I
2015-10-12 21:21 ` Tony Lindgren
[not found] ` <20151012212149.GZ23801-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-10-12 21:46 ` Kishon Vijay Abraham I
2015-10-12 22:03 ` Tony Lindgren
2015-10-12 22:05 ` Kishon Vijay Abraham I [this message]
[not found] ` <561C2E93.3020809-l0cyMroinI0@public.gmane.org>
2015-10-12 22:12 ` Tony Lindgren
[not found] ` <20151012221255.GG23801-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-10-12 22:18 ` Kishon Vijay Abraham I
[not found] ` <561C31B7.3060604-l0cyMroinI0@public.gmane.org>
2015-10-12 22:23 ` Tony Lindgren
2015-09-15 13:33 ` [PATCH v2 2/4] ARM: dts: dra7: Use "syscon-phy-power" and "syscon-pcs" in PCIe PHY node Kishon Vijay Abraham I
2015-09-15 13:33 ` [PATCH v2 3/4] ARM: dts: dra7: Use "ti, dra7x-usb2-phy2" compatible string for USB2 PHY2 Kishon Vijay Abraham I
2015-09-15 13:33 ` [PATCH v2 4/4] ARM: dts: <am4372/dra7/omap5>: Use "syscon-phy-power" instead of "ctrl-module" Kishon Vijay Abraham I
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=561C2E93.3020809@ti.com \
--to=kishon@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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 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).