public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] W1: OMAP HDQ1W: use 32-bit register accesses
@ 2012-01-22 20:26 Paul Walmsley
  2012-01-23 15:07 ` Evgeniy Polyakov
  0 siblings, 1 reply; 5+ messages in thread
From: Paul Walmsley @ 2012-01-22 20:26 UTC (permalink / raw)
  To: Evgeniy Polyakov; +Cc: linux-omap, linux-kernel, linux-arm-kernel, neilb


HDQ/1-wire registers are 32 bits long, even if the register contents
fit into 8 bits, so accesses must be 32-bit aligned.  Evidently the
OMAP2/3 interconnects allowed the driver to get away with 8 bit accesses,
but the OMAP4 puts a stop to that:

[    1.488800] Driver for 1-wire Dallas network protocol.
[    1.495025] Bad mode in data abort handler detected
[    1.500122] Internal error: Oops - bad mode: 0 [#1] SMP
[    1.505615] Modules linked in:
[    1.508819] CPU: 0    Not tainted  (3.3.0-rc1-00008-g45030e9 #992)
[    1.515289] PC is at 0xffff0018
[    1.518615] LR is at omap_hdq_probe+0xd4/0x2cc

The OMAP4430 ES2 Rev X TRM does warn about this restriction in section 
23.2.6.2 "HDQ/1-Wire Registers".

Fixes the crash on OMAP4430 ES2 Pandaboard.  Tested also on OMAP34xx and 
OMAP2420; it seems to work fine on those chips, although due to the lack 
of boards with HDQ/1-wire devices here, a more indepth test was not 
possible.

---
Intended for the v3.4 merge window.

 drivers/w1/masters/omap_hdq.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/w1/masters/omap_hdq.c b/drivers/w1/masters/omap_hdq.c
index 63e3eda..291897c 100644
--- a/drivers/w1/masters/omap_hdq.c
+++ b/drivers/w1/masters/omap_hdq.c
@@ -100,20 +100,20 @@ static struct w1_bus_master omap_w1_master = {
 /* HDQ register I/O routines */
 static inline u8 hdq_reg_in(struct hdq_data *hdq_data, u32 offset)
 {
-	return __raw_readb(hdq_data->hdq_base + offset);
+	return __raw_readl(hdq_data->hdq_base + offset);
 }
 
 static inline void hdq_reg_out(struct hdq_data *hdq_data, u32 offset, u8 val)
 {
-	__raw_writeb(val, hdq_data->hdq_base + offset);
+	__raw_writel(val, hdq_data->hdq_base + offset);
 }
 
 static inline u8 hdq_reg_merge(struct hdq_data *hdq_data, u32 offset,
 			u8 val, u8 mask)
 {
-	u8 new_val = (__raw_readb(hdq_data->hdq_base + offset) & ~mask)
+	u8 new_val = (__raw_readl(hdq_data->hdq_base + offset) & ~mask)
 			| (val & mask);
-	__raw_writeb(new_val, hdq_data->hdq_base + offset);
+	__raw_writel(new_val, hdq_data->hdq_base + offset);
 
 	return new_val;
 }
-- 
1.7.8.3


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH] W1: OMAP HDQ1W: use 32-bit register accesses
  2012-01-22 20:26 [PATCH] W1: OMAP HDQ1W: use 32-bit register accesses Paul Walmsley
@ 2012-01-23 15:07 ` Evgeniy Polyakov
  2012-01-23 18:57   ` Paul Walmsley
  0 siblings, 1 reply; 5+ messages in thread
From: Evgeniy Polyakov @ 2012-01-23 15:07 UTC (permalink / raw)
  To: Paul Walmsley; +Cc: linux-omap, linux-kernel, linux-arm-kernel, neilb

Hi Paul

Patchset looks good, feel free to add my ack

On Sun, Jan 22, 2012 at 01:26:23PM -0700, Paul Walmsley (paul@pwsan.com) wrote:
> 
> HDQ/1-wire registers are 32 bits long, even if the register contents
> fit into 8 bits, so accesses must be 32-bit aligned.  Evidently the
> OMAP2/3 interconnects allowed the driver to get away with 8 bit accesses,
> but the OMAP4 puts a stop to that:
> 
> [    1.488800] Driver for 1-wire Dallas network protocol.
> [    1.495025] Bad mode in data abort handler detected
> [    1.500122] Internal error: Oops - bad mode: 0 [#1] SMP
> [    1.505615] Modules linked in:
> [    1.508819] CPU: 0    Not tainted  (3.3.0-rc1-00008-g45030e9 #992)
> [    1.515289] PC is at 0xffff0018
> [    1.518615] LR is at omap_hdq_probe+0xd4/0x2cc
> 
> The OMAP4430 ES2 Rev X TRM does warn about this restriction in section 
> 23.2.6.2 "HDQ/1-Wire Registers".
> 
> Fixes the crash on OMAP4430 ES2 Pandaboard.  Tested also on OMAP34xx and 
> OMAP2420; it seems to work fine on those chips, although due to the lack 
> of boards with HDQ/1-wire devices here, a more indepth test was not 
> possible.
> 
> ---
> Intended for the v3.4 merge window.
> 
>  drivers/w1/masters/omap_hdq.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/w1/masters/omap_hdq.c b/drivers/w1/masters/omap_hdq.c
> index 63e3eda..291897c 100644
> --- a/drivers/w1/masters/omap_hdq.c
> +++ b/drivers/w1/masters/omap_hdq.c
> @@ -100,20 +100,20 @@ static struct w1_bus_master omap_w1_master = {
>  /* HDQ register I/O routines */
>  static inline u8 hdq_reg_in(struct hdq_data *hdq_data, u32 offset)
>  {
> -	return __raw_readb(hdq_data->hdq_base + offset);
> +	return __raw_readl(hdq_data->hdq_base + offset);
>  }
>  
>  static inline void hdq_reg_out(struct hdq_data *hdq_data, u32 offset, u8 val)
>  {
> -	__raw_writeb(val, hdq_data->hdq_base + offset);
> +	__raw_writel(val, hdq_data->hdq_base + offset);
>  }
>  
>  static inline u8 hdq_reg_merge(struct hdq_data *hdq_data, u32 offset,
>  			u8 val, u8 mask)
>  {
> -	u8 new_val = (__raw_readb(hdq_data->hdq_base + offset) & ~mask)
> +	u8 new_val = (__raw_readl(hdq_data->hdq_base + offset) & ~mask)
>  			| (val & mask);
> -	__raw_writeb(new_val, hdq_data->hdq_base + offset);
> +	__raw_writel(new_val, hdq_data->hdq_base + offset);
>  
>  	return new_val;
>  }
> -- 
> 1.7.8.3

-- 
	Evgeniy Polyakov

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] W1: OMAP HDQ1W: use 32-bit register accesses
  2012-01-23 15:07 ` Evgeniy Polyakov
@ 2012-01-23 18:57   ` Paul Walmsley
  2012-01-23 20:36     ` Evgeniy Polyakov
  0 siblings, 1 reply; 5+ messages in thread
From: Paul Walmsley @ 2012-01-23 18:57 UTC (permalink / raw)
  To: Evgeniy Polyakov; +Cc: linux-omap, linux-kernel, linux-arm-kernel, neilb

Hi Evgeniy

On Mon, 23 Jan 2012, Evgeniy Polyakov wrote:

> Hi Paul
> 
> Patchset looks good, feel free to add my ack

Thanks, added.  If you have a spare moment, could you see if this one is 
appropriate for acking too?

http://www.spinics.net/lists/arm-kernel/msg156572.html


regards,

- Paul

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] W1: OMAP HDQ1W: use 32-bit register accesses
  2012-01-23 18:57   ` Paul Walmsley
@ 2012-01-23 20:36     ` Evgeniy Polyakov
  2012-01-24  8:00       ` Paul Walmsley
  0 siblings, 1 reply; 5+ messages in thread
From: Evgeniy Polyakov @ 2012-01-23 20:36 UTC (permalink / raw)
  To: Paul Walmsley; +Cc: linux-omap, linux-kernel, linux-arm-kernel, neilb

On Mon, Jan 23, 2012 at 11:57:09AM -0700, Paul Walmsley (paul@pwsan.com) wrote:
> http://www.spinics.net/lists/arm-kernel/msg156572.html

Well, if runtime PM does its job for clock manipulation properly, then
things should be fine. I suppose that ->probe() will fire up first and
you say it boots and detects w1 properly, so patch looks good.
Feel free to add my ack

-- 
	Evgeniy Polyakov

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] W1: OMAP HDQ1W: use 32-bit register accesses
  2012-01-23 20:36     ` Evgeniy Polyakov
@ 2012-01-24  8:00       ` Paul Walmsley
  0 siblings, 0 replies; 5+ messages in thread
From: Paul Walmsley @ 2012-01-24  8:00 UTC (permalink / raw)
  To: Evgeniy Polyakov; +Cc: linux-omap, linux-kernel, linux-arm-kernel, neilb

On Mon, 23 Jan 2012, Evgeniy Polyakov wrote:

> On Mon, Jan 23, 2012 at 11:57:09AM -0700, Paul Walmsley (paul@pwsan.com) wrote:
> > http://www.spinics.net/lists/arm-kernel/msg156572.html
> 
> Well, if runtime PM does its job for clock manipulation properly, then
> things should be fine. I suppose that ->probe() will fire up first and
> you say it boots and detects w1 properly, so patch looks good.
> Feel free to add my ack

Thanks Evgeniy.

- Paul

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2012-01-24  8:00 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-22 20:26 [PATCH] W1: OMAP HDQ1W: use 32-bit register accesses Paul Walmsley
2012-01-23 15:07 ` Evgeniy Polyakov
2012-01-23 18:57   ` Paul Walmsley
2012-01-23 20:36     ` Evgeniy Polyakov
2012-01-24  8:00       ` Paul Walmsley

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox