From: Keerthy <a0393675@ti.com>
To: Paul Walmsley <paul@pwsan.com>, Keerthy <j-keerthy@ti.com>
Cc: devicetree@vger.kernel.org, tony@atomide.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] ARM: AM43XX: HWMOD: Add rtc hwmod
Date: Fri, 19 Feb 2016 13:29:23 +0530 [thread overview]
Message-ID: <56C6CB5B.20804@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602190720490.27696@utopia.booyaka.com>
On Friday 19 February 2016 12:51 PM, Paul Walmsley wrote:
> On Fri, 19 Feb 2016, Keerthy wrote:
>
>> The patch adds rtc hwmod. RTC module The RTC module is physically
>> present on the AM438x SoC used on AM43X-EPOS-EVM, but it is permanently
>> disabled. A secure RTC is used instead on these devices, where needed.
>> . Hence adding it selectively using a seprate list to get RTC Module
>> functional on the other am43x SoCs used on am437x-gp-evm and
>> am437x-sk-evm.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>>
>> Changes in v2:
>>
>> Inverted the checking logic to accommodate registering for all
>> the SoCs compatible to am4372 and removed the negating am438x logic
>> to register rtc hwmods as suggested by Paul.
>>
>> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 14 +++++++++++++-
>> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> OK thanks; I've queued the following patch for v4.6 or if I get unlucky,
> v4.7.
Thanks Paul!
>
> - Paul
>
> From: Keerthy <j-keerthy@ti.com>
> Date: Fri, 19 Feb 2016 10:08:55 +0530
> Subject: [PATCH] ARM: AM43XX: hwmod: Add rtc hwmod
>
> The patch registers the rtc hwmod on AM437x chips. The RTC module is
> physically present on the AM438x SoC used on AM43X-EPOS-EVM, but it is
> permanently disabled. A secure RTC is used instead on these devices,
> where needed. Hence adding it selectively using a separate list to get
> RTC Module functional on the other am43x SoCs used on am437x-gp-evm
> and am437x-sk-evm.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> [paul@pwsan.com: cleaned up patch description]
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> index e97a894b5f88..97fd399202dc 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> @@ -1020,9 +1020,21 @@ static struct omap_hwmod_ocp_if *am43xx_hwmod_ocp_ifs[] __initdata = {
> NULL,
> };
>
> +static struct omap_hwmod_ocp_if *am43xx_rtc_hwmod_ocp_ifs[] __initdata = {
> + &am33xx_l4_wkup__rtc,
> + NULL,
> +};
> +
> int __init am43xx_hwmod_init(void)
> {
> + int ret;
> +
> omap_hwmod_am43xx_reg();
> omap_hwmod_init();
> - return omap_hwmod_register_links(am43xx_hwmod_ocp_ifs);
> + ret = omap_hwmod_register_links(am43xx_hwmod_ocp_ifs);
> +
> + if (!ret && of_machine_is_compatible("ti,am4372"))
> + ret = omap_hwmod_register_links(am43xx_rtc_hwmod_ocp_ifs);
> +
> + return ret;
> }
>
WARNING: multiple messages have this Message-ID (diff)
From: a0393675@ti.com (Keerthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] ARM: AM43XX: HWMOD: Add rtc hwmod
Date: Fri, 19 Feb 2016 13:29:23 +0530 [thread overview]
Message-ID: <56C6CB5B.20804@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602190720490.27696@utopia.booyaka.com>
On Friday 19 February 2016 12:51 PM, Paul Walmsley wrote:
> On Fri, 19 Feb 2016, Keerthy wrote:
>
>> The patch adds rtc hwmod. RTC module The RTC module is physically
>> present on the AM438x SoC used on AM43X-EPOS-EVM, but it is permanently
>> disabled. A secure RTC is used instead on these devices, where needed.
>> . Hence adding it selectively using a seprate list to get RTC Module
>> functional on the other am43x SoCs used on am437x-gp-evm and
>> am437x-sk-evm.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>>
>> Changes in v2:
>>
>> Inverted the checking logic to accommodate registering for all
>> the SoCs compatible to am4372 and removed the negating am438x logic
>> to register rtc hwmods as suggested by Paul.
>>
>> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 14 +++++++++++++-
>> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> OK thanks; I've queued the following patch for v4.6 or if I get unlucky,
> v4.7.
Thanks Paul!
>
> - Paul
>
> From: Keerthy <j-keerthy@ti.com>
> Date: Fri, 19 Feb 2016 10:08:55 +0530
> Subject: [PATCH] ARM: AM43XX: hwmod: Add rtc hwmod
>
> The patch registers the rtc hwmod on AM437x chips. The RTC module is
> physically present on the AM438x SoC used on AM43X-EPOS-EVM, but it is
> permanently disabled. A secure RTC is used instead on these devices,
> where needed. Hence adding it selectively using a separate list to get
> RTC Module functional on the other am43x SoCs used on am437x-gp-evm
> and am437x-sk-evm.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> [paul at pwsan.com: cleaned up patch description]
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> index e97a894b5f88..97fd399202dc 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> @@ -1020,9 +1020,21 @@ static struct omap_hwmod_ocp_if *am43xx_hwmod_ocp_ifs[] __initdata = {
> NULL,
> };
>
> +static struct omap_hwmod_ocp_if *am43xx_rtc_hwmod_ocp_ifs[] __initdata = {
> + &am33xx_l4_wkup__rtc,
> + NULL,
> +};
> +
> int __init am43xx_hwmod_init(void)
> {
> + int ret;
> +
> omap_hwmod_am43xx_reg();
> omap_hwmod_init();
> - return omap_hwmod_register_links(am43xx_hwmod_ocp_ifs);
> + ret = omap_hwmod_register_links(am43xx_hwmod_ocp_ifs);
> +
> + if (!ret && of_machine_is_compatible("ti,am4372"))
> + ret = omap_hwmod_register_links(am43xx_rtc_hwmod_ocp_ifs);
> +
> + return ret;
> }
>
WARNING: multiple messages have this Message-ID (diff)
From: Keerthy <a0393675@ti.com>
To: Paul Walmsley <paul@pwsan.com>, Keerthy <j-keerthy@ti.com>
Cc: <tony@atomide.com>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<robh+dt@kernel.org>
Subject: Re: [PATCH v2 2/2] ARM: AM43XX: HWMOD: Add rtc hwmod
Date: Fri, 19 Feb 2016 13:29:23 +0530 [thread overview]
Message-ID: <56C6CB5B.20804@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602190720490.27696@utopia.booyaka.com>
On Friday 19 February 2016 12:51 PM, Paul Walmsley wrote:
> On Fri, 19 Feb 2016, Keerthy wrote:
>
>> The patch adds rtc hwmod. RTC module The RTC module is physically
>> present on the AM438x SoC used on AM43X-EPOS-EVM, but it is permanently
>> disabled. A secure RTC is used instead on these devices, where needed.
>> . Hence adding it selectively using a seprate list to get RTC Module
>> functional on the other am43x SoCs used on am437x-gp-evm and
>> am437x-sk-evm.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>>
>> Changes in v2:
>>
>> Inverted the checking logic to accommodate registering for all
>> the SoCs compatible to am4372 and removed the negating am438x logic
>> to register rtc hwmods as suggested by Paul.
>>
>> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 14 +++++++++++++-
>> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> OK thanks; I've queued the following patch for v4.6 or if I get unlucky,
> v4.7.
Thanks Paul!
>
> - Paul
>
> From: Keerthy <j-keerthy@ti.com>
> Date: Fri, 19 Feb 2016 10:08:55 +0530
> Subject: [PATCH] ARM: AM43XX: hwmod: Add rtc hwmod
>
> The patch registers the rtc hwmod on AM437x chips. The RTC module is
> physically present on the AM438x SoC used on AM43X-EPOS-EVM, but it is
> permanently disabled. A secure RTC is used instead on these devices,
> where needed. Hence adding it selectively using a separate list to get
> RTC Module functional on the other am43x SoCs used on am437x-gp-evm
> and am437x-sk-evm.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> [paul@pwsan.com: cleaned up patch description]
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> index e97a894b5f88..97fd399202dc 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
> @@ -1020,9 +1020,21 @@ static struct omap_hwmod_ocp_if *am43xx_hwmod_ocp_ifs[] __initdata = {
> NULL,
> };
>
> +static struct omap_hwmod_ocp_if *am43xx_rtc_hwmod_ocp_ifs[] __initdata = {
> + &am33xx_l4_wkup__rtc,
> + NULL,
> +};
> +
> int __init am43xx_hwmod_init(void)
> {
> + int ret;
> +
> omap_hwmod_am43xx_reg();
> omap_hwmod_init();
> - return omap_hwmod_register_links(am43xx_hwmod_ocp_ifs);
> + ret = omap_hwmod_register_links(am43xx_hwmod_ocp_ifs);
> +
> + if (!ret && of_machine_is_compatible("ti,am4372"))
> + ret = omap_hwmod_register_links(am43xx_rtc_hwmod_ocp_ifs);
> +
> + return ret;
> }
>
next prev parent reply other threads:[~2016-02-19 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 4:38 [PATCH v2 0/2] arm: am43xx: Register rtc hwmod Keerthy
2016-02-19 4:38 ` Keerthy
2016-02-19 4:38 ` Keerthy
2016-02-19 4:38 ` [PATCH v2 1/2] ARM: dts: am43x-epos-evm: Add the am438 compatible string Keerthy
2016-02-19 4:38 ` Keerthy
2016-02-19 4:38 ` Keerthy
[not found] ` <1455856735-11515-2-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-02-19 18:55 ` Tony Lindgren
2016-02-19 18:55 ` Tony Lindgren
2016-02-19 18:55 ` Tony Lindgren
[not found] ` <1455856735-11515-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-02-19 4:38 ` [PATCH v2 2/2] ARM: AM43XX: HWMOD: Add rtc hwmod Keerthy
2016-02-19 4:38 ` Keerthy
2016-02-19 4:38 ` Keerthy
2016-02-19 7:21 ` Paul Walmsley
2016-02-19 7:21 ` Paul Walmsley
2016-02-19 7:59 ` Keerthy [this message]
2016-02-19 7:59 ` Keerthy
2016-02-19 7:59 ` Keerthy
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=56C6CB5B.20804@ti.com \
--to=a0393675@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 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.