public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Avinash.H.M." <avinashhm@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
	Benoit Cousson <b-cousson@ti.com>, Kevin Hilman <khilman@ti.com>
Subject: Re: [PATCH] omap: hwmod: add syss reset done flags to omap2, omap3 hwmods
Date: Fri, 25 Mar 2011 11:56:34 +0530	[thread overview]
Message-ID: <20110325062534.GA25480@avinash-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1103242336410.21987@utopia.booyaka.com>

On Thu, Mar 24, 2011 at 11:38:15PM -0600, Paul Walmsley wrote:
> Hi Avinash,

Hi Paul, 

> 
> > > On Thu, 24 Feb 2011, Avinash.H.M wrote:
> > > 
> > > > Some of the omap2, omap3 peripherals support software reset. This
> > > > can be done through the softreset bit in sysconfig register.
> > > > The reset status can be checked through resetdone bit of
> > > > sysstatus register. syss_has_reset_status is added to the hwmod
> > > > database of peripherals which have resetdone bit in sysstatus register.
> > > > 
> > > > Cc: Rajendra Nayak <rnayak@ti.com>
> > > > Cc: Paul Walmsley <paul@pwsan.com>
> > > > Cc: Benoit Cousson <b-cousson@ti.com>
> > > > Cc: Kevin Hilman <khilman@ti.com>
> > > > Reviewed-by: Govindraj.R <govindraj.raja@ti.com>
> > > > Signed-off-by: Avinash.H.M <avinashhm@ti.com>
> 
> This patch is causing I2C softreset timeouts in the hwmod layer on OMAP2 
> and 3.  Could you please take a look at this and figure out what is going 
> on?

I ll start looking at this. I have a 3430 ES3.1 SDP, where i will check the
difference in behaviour with this patch. 

BTW, is there a test case which i should run to produce 'I2C softreset
timeouts' ? Can you give more information on how to reproduce the issue
?.

br,

- avinash

> 
> thanks,
> 
> - Paul

  reply	other threads:[~2011-03-25  6:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 10:08 [PATCH] omap: hwmod: add syss reset done flags to omap2, omap3 hwmods Avinash.H.M
2011-03-03 21:28 ` Paul Walmsley
2011-03-14 16:16   ` Avinash.H.M.
2011-03-25  5:38     ` Paul Walmsley
2011-03-25  6:26       ` Avinash.H.M. [this message]
2011-03-25  7:20         ` Avinash.H.M.
2011-03-25 17:24           ` Paul Walmsley
2011-03-26 11:35             ` Avinash.H.M.
2011-03-26 19:38               ` Paul Walmsley
2011-03-31 14:40               ` Avinash.H.M.
2011-03-31 15:04                 ` Kevin Hilman
2011-03-31 15:51                   ` Avinash.H.M.
2011-03-31 15:56                     ` Cousson, Benoit
2011-03-31 16:22                       ` Avinash.H.M.
2011-03-25 14:42       ` Cousson, Benoit
2011-03-25 17:23         ` Paul Walmsley
2011-03-26 11:31           ` Avinash.H.M.
2011-03-31 13:06             ` Avinash.H.M.

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=20110325062534.GA25480@avinash-laptop \
    --to=avinashhm@ti.com \
    --cc=b-cousson@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rnayak@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