linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "R, Vignesh" <vigneshr@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Evgeniy Polyakov <zbr@ioremap.net>,
	Jonathan Corbet <corbet@lwn.net>,
	Tony Lindgren <tony@atomide.com>,
	Russell King <linux@arm.linux.org.uk>, NeilBrown <neilb@suse.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: OMAP2: hwmod: AM43XX: Add hwmod support for HDQ-1W
Date: Mon, 2 Mar 2015 13:57:31 +0530	[thread overview]
Message-ID: <54F41EF3.6080302@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503012305550.9987@utopia.booyaka.com>

Hi,

On 3/2/2015 4:39 AM, Paul Walmsley wrote:
> Hi
> 
> On Fri, 27 Feb 2015, Vignesh R wrote:
> 
>> From: "Poddar, Sourav" <sourav.poddar@ti.com>
>>
>> This patch adds hwmod data for hdq/1w driver on AM43xx.
>>
>> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
>> [vigneshr@ti.com: Ported patch to v4.0-rc1]
>> Signed-off-by: Vignesh R <vigneshr@ti.com>
>> ---
>>  arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 36 ++++++++++++++++++++++++++++++
>>  arch/arm/mach-omap2/prcm43xx.h             |  1 +
>>  2 files changed, 37 insertions(+)
>>
>> diff --git a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
>> index 8eb85925e444..d4f1df28475c 100644
>> --- a/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
>> +++ b/arch/arm/mach-omap2/omap_hwmod_43xx_data.c
>> @@ -20,6 +20,7 @@
>>  #include "omap_hwmod_33xx_43xx_common_data.h"
>>  #include "prcm43xx.h"
>>  #include "omap_hwmod_common_data.h"
>> +#include "hdq1w.h"
>>  
>>  
>>  /* IP blocks */
>> @@ -516,6 +517,33 @@ static struct omap_hwmod am43xx_dss_rfbi_hwmod = {
>>  	.parent_hwmod	= &am43xx_dss_core_hwmod,
>>  };
>>  
>> +/* HDQ1W */
>> +static struct omap_hwmod_class_sysconfig am43xx_hdq1w_sysc = {
>> +	.rev_offs       = 0x0000,
>> +	.sysc_offs      = 0x0014,
>> +	.syss_offs      = 0x0018,
>> +	.sysc_flags     = (SYSC_HAS_SOFTRESET),
> 
> This is missing the SYSC_HAS_AUTOIDLE bit.  Is this intentional?

Sorry.. my bad.. I didn't observe this while porting the patch.
I will fix this and repost.

Regards
Vignesh

> 
>> +	.sysc_fields    = &omap_hwmod_sysc_type1,
>> +};
>> +
>> +static struct omap_hwmod_class am43xx_hdq1w_hwmod_class = {
>> +	.name   = "hdq1w",
>> +	.sysc   = &am43xx_hdq1w_sysc,
>> +	.reset	= &omap_hdq1w_reset,
>> +};
>> +
>> +static struct omap_hwmod am43xx_hdq1w_hwmod = {
>> +	.name           = "hdq1w",
>> +	.class          = &am43xx_hdq1w_hwmod_class,
>> +	.clkdm_name     = "l4ls_clkdm",
>> +	.prcm = {
>> +		.omap4 = {
>> +			.clkctrl_offs = AM43XX_CM_PER_HDQ1W_CLKCTRL_OFFSET,
>> +			.modulemode   = MODULEMODE_SWCTRL,
>> +		},
>> +	},
>> +};
>> +
>>  /* Interfaces */
>>  static struct omap_hwmod_ocp_if am43xx_l3_main__l4_hs = {
>>  	.master		= &am33xx_l3_main_hwmod,
>> @@ -790,6 +818,13 @@ static struct omap_hwmod_ocp_if am43xx_l4_ls__dss_rfbi = {
>>  	.user		= OCP_USER_MPU | OCP_USER_SDMA,
>>  };
>>  
>> +static struct omap_hwmod_ocp_if am43xx_l4_ls__hdq1w = {
>> +	.master         = &am33xx_l4_ls_hwmod,
>> +	.slave          = &am43xx_hdq1w_hwmod,
>> +	.clk            = "l4ls_gclk",
>> +	.user           = OCP_USER_MPU | OCP_USER_SDMA,
>> +};
>> +
>>  static struct omap_hwmod_ocp_if *am43xx_hwmod_ocp_ifs[] __initdata = {
>>  	&am33xx_l4_wkup__synctimer,
>>  	&am43xx_l4_ls__timer8,
>> @@ -889,6 +924,7 @@ static struct omap_hwmod_ocp_if *am43xx_hwmod_ocp_ifs[] __initdata = {
>>  	&am43xx_l4_ls__dss,
>>  	&am43xx_l4_ls__dss_dispc,
>>  	&am43xx_l4_ls__dss_rfbi,
>> +	&am43xx_l4_ls__hdq1w,
>>  	NULL,
>>  };
>>  
>> diff --git a/arch/arm/mach-omap2/prcm43xx.h b/arch/arm/mach-omap2/prcm43xx.h
>> index ad7b3e9977f8..48df3b55057e 100644
>> --- a/arch/arm/mach-omap2/prcm43xx.h
>> +++ b/arch/arm/mach-omap2/prcm43xx.h
>> @@ -143,5 +143,6 @@
>>  #define AM43XX_CM_PER_USB_OTG_SS1_CLKCTRL_OFFSET        0x0268
>>  #define AM43XX_CM_PER_USBPHYOCP2SCP1_CLKCTRL_OFFSET	0x05C0
>>  #define AM43XX_CM_PER_DSS_CLKCTRL_OFFSET		0x0a20
>> +#define AM43XX_CM_PER_HDQ1W_CLKCTRL_OFFSET		0x04a0
>>  
>>  #endif
>> -- 
>> 1.9.1
>>
> 
> 
> - Paul
> 

      reply	other threads:[~2015-03-02  8:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  9:24 [PATCH 1/2] ARM: OMAP2: hwmod: AM43XX: Add hwmod support for HDQ-1W Vignesh R
2015-02-27  9:24 ` [PATCH 2/2] w1: masters: omap_hdq: Add support for 1-wire mode Vignesh R
2015-02-27  9:55   ` Arnd Bergmann
2015-02-27 10:31     ` Vignesh R
2015-02-27 10:34       ` Arnd Bergmann
2015-03-02  7:57         ` R, Vignesh
2015-03-01 23:09 ` [PATCH 1/2] ARM: OMAP2: hwmod: AM43XX: Add hwmod support for HDQ-1W Paul Walmsley
2015-03-02  8:27   ` R, Vignesh [this message]

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=54F41EF3.6080302@ti.com \
    --to=vigneshr@ti.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.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=neilb@suse.de \
    --cc=paul@pwsan.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.com \
    --cc=zbr@ioremap.net \
    /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).