linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: "Ramos Falcon, Ernesto" <ernesto@ti.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
	"Ramirez Luna, Omar" <omar.ramirez@ti.com>,
	"ohad@wizery.com" <ohad@wizery.com>,
	"ameya.palande@nokia.com" <ameya.palande@nokia.com>,
	"felipe.contreras@nokia.com" <felipe.contreras@nokia.com>,
	"Guzman Lugo, Fernando" <fernando.lugo@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 4/5] staging:ti dspbridge: remove unnecessary volatile variables
Date: Wed, 28 Jul 2010 10:03:49 -0500	[thread overview]
Message-ID: <4C5046D5.6010306@ti.com> (raw)
In-Reply-To: <1280328052-31292-5-git-send-email-ernesto@ti.com>

Ramos Falcon, Ernesto had written, on 07/28/2010 09:40 AM, the following:
> Remove unnecessary volatile variables; use accessor
> functions __raw_readl/__raw_writel instead when applicable.
> 
> Signed-off-by: Ernesto Ramos <ernesto@ti.com>
> ---
>  drivers/staging/tidspbridge/core/tiomap3430.c |    8 ++++----
>  drivers/staging/tidspbridge/dynload/tramp.c   |    4 ++--
>  drivers/staging/tidspbridge/pmgr/cmm.c        |    7 ++++---
>  3 files changed, 10 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/staging/tidspbridge/core/tiomap3430.c b/drivers/staging/tidspbridge/core/tiomap3430.c
> index 08a2f5f..ae1f394 100644
> --- a/drivers/staging/tidspbridge/core/tiomap3430.c
> +++ b/drivers/staging/tidspbridge/core/tiomap3430.c
> @@ -404,7 +404,7 @@ static int bridge_brd_start(struct bridge_dev_context *dev_ctxt,
>  		pr_err("%s: Illegal SM base\n", __func__);
>  		status = -EPERM;
>  	} else
> -		*((volatile u32 *)dw_sync_addr) = 0xffffffff;
> +		__raw_writel(0xffffffff, dw_sync_addr);
curious question: any reason not to use writel instead of __raw_writel?

>  
>  	if (DSP_SUCCEEDED(status)) {
>  		resources = dev_context->resources;
> @@ -584,7 +584,7 @@ static int bridge_brd_start(struct bridge_dev_context *dev_ctxt,
>  		dev_dbg(bridge, "Waiting for Sync @ 0x%x\n", dw_sync_addr);
>  		dev_dbg(bridge, "DSP c_int00 Address =  0x%x\n", dsp_addr);
>  		if (dsp_debug)
> -			while (*((volatile u16 *)dw_sync_addr))
> +			while (__raw_readw(dw_sync_addr))
>  				;;

may be for a later on patch -> we seem to have a potential infinite loop 
here..

>  
>  		/* Wait for DSP to clear word in shared memory */
> @@ -602,7 +602,7 @@ static int bridge_brd_start(struct bridge_dev_context *dev_ctxt,
>  			/* Write the synchronization bit to indicate the
>  			 * completion of OPP table update to DSP
>  			 */
> -			*((volatile u32 *)dw_sync_addr) = 0XCAFECAFE;
> +			__raw_writel(0XCAFECAFE, dw_sync_addr);
>  
>  			/* update board state */
>  			dev_context->dw_brd_state = BRD_RUNNING;
> @@ -1852,7 +1852,7 @@ bool wait_for_start(struct bridge_dev_context *dev_context, u32 dw_sync_addr)
>  	u16 timeout = TIHELEN_ACKTIMEOUT;
>  
>  	/*  Wait for response from board */
> -	while (*((volatile u16 *)dw_sync_addr) && --timeout)
> +	while (__raw_readw(dw_sync_addr) && --timeout)
>  		udelay(10);
>  
>  	/*  If timed out: return false */
> diff --git a/drivers/staging/tidspbridge/dynload/tramp.c b/drivers/staging/tidspbridge/dynload/tramp.c
> index 81314d2..60d22ea 100644
> --- a/drivers/staging/tidspbridge/dynload/tramp.c
> +++ b/drivers/staging/tidspbridge/dynload/tramp.c
> @@ -86,8 +86,8 @@ static u8 priv_h2a(u8 value)
>  static void priv_tramp_sym_gen_name(u32 value, char *dst)
>  {
>  	u32 i;
> -	volatile char *prefix = TRAMP_SYM_PREFIX;
> -	volatile char *dst_local = dst;
> +	char *prefix = TRAMP_SYM_PREFIX;
> +	char *dst_local = dst;
>  	u8 tmp;
>  
>  	/*  Clear out the destination, including the ending NULL */
> diff --git a/drivers/staging/tidspbridge/pmgr/cmm.c b/drivers/staging/tidspbridge/pmgr/cmm.c
> index 874ed64..b7cba1b 100644
> --- a/drivers/staging/tidspbridge/pmgr/cmm.c
> +++ b/drivers/staging/tidspbridge/pmgr/cmm.c
> @@ -1008,6 +1008,7 @@ void *cmm_xlator_alloc_buf(struct cmm_xlatorobject *xlator, void *va_buf,
>  {
>  	struct cmm_xlator *xlator_obj = (struct cmm_xlator *)xlator;
>  	void *pbuf = NULL;
> +	void *tmp_va_buff;
>  	struct cmm_attrs attrs;
>  
>  	DBC_REQUIRE(refs > 0);
> @@ -1019,16 +1020,16 @@ void *cmm_xlator_alloc_buf(struct cmm_xlatorobject *xlator, void *va_buf,
>  
>  	if (xlator_obj) {
>  		attrs.ul_seg_id = xlator_obj->ul_seg_id;
> -		*(volatile u32 *)va_buf = 0;
> +		__raw_writel(0, va_buf);
>  		/* Alloc SM */
>  		pbuf =
>  		    cmm_calloc_buf(xlator_obj->hcmm_mgr, pa_size, &attrs, NULL);
>  		if (pbuf) {
>  			/* convert to translator(node/strm) process Virtual
>  			 * address */
> -			*(volatile u32 **)va_buf =
> -			    (u32 *) cmm_xlator_translate(xlator,
> +			 tmp_va_buff = cmm_xlator_translate(xlator,
>  							 pbuf, CMM_PA2VA);
> +			__raw_writel((u32)tmp_va_buff, va_buf);

a) is the u32 cast of tmp_va_buff really necessary?
b) tmp_va_buff is used only in this branch, why not reduce the scope of 
the variable to just to this if branch
or an optional way could be:
--- a/drivers/staging/tidspbridge/pmgr/cmm.c
+++ b/drivers/staging/tidspbridge/pmgr/cmm.c
@@ -1022,18 +1022,17 @@ void *cmm_xlator_alloc_buf(struct 
cmm_xlatorobject *xlator, void *va_buf,
  	DBC_REQUIRE(xlator_obj->ul_seg_id > 0);

  	if (xlator_obj) {
+		void *t_buf = 0;
  		attrs.ul_seg_id = xlator_obj->ul_seg_id;
-		*(volatile u32 *)va_buf = 0;
  		/* Alloc SM */
  		pbuf =
  		    cmm_calloc_buf(xlator_obj->hcmm_mgr, pa_size, &attrs, NULL);
  		if (pbuf) {
  			/* convert to translator(node/strm) process Virtual
  			 * address */
-			*(volatile u32 **)va_buf =
-			    (u32 *) cmm_xlator_translate(xlator,
-							 pbuf, CMM_PA2VA);
+			t_buf = cmm_xlator_translate(xlator, pbuf, CMM_PA2VA);
  		}
+		writel(t_buf, va_buf);
  	}
  	return pbuf;
  }


>  		}
>  	}
>  	return pbuf;


-- 
Regards,
Nishanth Menon

  parent reply	other threads:[~2010-07-28 15:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 14:40 [PATCH 0/5] staging:ti dspbridge: Checkpatch errors cleanup series Ernesto Ramos
2010-07-28 14:40 ` [PATCH 1/5] staging:ti dspbridge: remove unused typedef REG16 Ernesto Ramos
2010-07-28 14:40   ` [PATCH 2/5] staging:ti dspbridge: remove unnecessary check for NULL pointer in cmm.c Ernesto Ramos
2010-07-28 14:40     ` [PATCH 3/5] staging:ti dspbridge: remove function delete_strm_mgr Ernesto Ramos
2010-07-28 14:40       ` [PATCH 4/5] staging:ti dspbridge: remove unnecessary volatile variables Ernesto Ramos
2010-07-28 14:40         ` [PATCH 5/5] staging:ti dspbridge: replace simple_strtoul by strict_strtoul Ernesto Ramos
2010-07-28 15:09           ` Greg KH
2010-07-28 18:40             ` Andy Shevchenko
2010-07-28 18:56               ` Greg KH
2010-07-28 18:43           ` Andy Shevchenko
2010-08-03 17:33             ` Ramos Falcon, Ernesto
2010-07-28 15:03         ` Nishanth Menon [this message]
2010-08-02 19:46           ` [PATCH 4/5] staging:ti dspbridge: remove unnecessary volatile variables Ramos Falcon, Ernesto
2010-07-28 15:04     ` [PATCH 2/5] staging:ti dspbridge: remove unnecessary check for NULL pointer in cmm.c Nishanth Menon
2010-07-28 15:31       ` Nishanth Menon
2010-07-28 16:53         ` Ramos Falcon, Ernesto
2010-07-28 17:11           ` Felipe Contreras
2010-07-28 17:29             ` Ramos Falcon, Ernesto

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=4C5046D5.6010306@ti.com \
    --to=nm@ti.com \
    --cc=ameya.palande@nokia.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=ernesto@ti.com \
    --cc=felipe.contreras@nokia.com \
    --cc=fernando.lugo@ti.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=omar.ramirez@ti.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).