From: Paul Walmsley <paul@pwsan.com> To: Rajendra Nayak <rnayak@ti.com> Cc: b-cousson@ti.com, khilman@ti.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Anand Gadiyar <gadiyar@ti.com>, Shubhrajyoti D <shubhrajyoti@ti.com> Subject: Re: [PATCH v2 2/2] ARM: omap: hwmod: Make omap_hwmod_softreset wait for reset status Date: Thu, 12 Apr 2012 11:15:00 -0600 (MDT) [thread overview] Message-ID: <alpine.DEB.2.00.1204121107450.29473@utopia.booyaka.com> (raw) In-Reply-To: <4F86D304.1020902@ti.com> Hi Rajendra, On Thu, 12 Apr 2012, Rajendra Nayak wrote: > On Thursday 12 April 2012 12:29 AM, Paul Walmsley wrote: > > That approach sounds fine to me, but I don't think Fernando's patch will > > help with I2C.. Since it uses a custom reset function omap_i2c_reset(), > > the delay will actually need to go there. > > While working on fixing this I stumbled upon a couple of other > things which don't seem right. > > The i2c custom reset funtion (omap_i2c_reset) uses a hwmod exposed > api to set the SOFTRESET bit, however it then accesses the hwmod > internal structure to poll on RESETDONE status bit. Should there be > another function exposed to poll on RESETDONE too? Sure, something like that would make sense for 3.5. > _reset() function documents its return value to be -ETIMEDOUT, if the > module fails to reset in time, and hence expects the custom reset > function to return the same in such cases. The omap_i2c_reset() function > seems to return 0 even in cases of timeout. However looking more closely > the return value from _reset() does not seem to be used in the framework > today. > > The comment in _ocp_softreset() suggests the intent was to add a new > state to the hwmod state machine. > > /* > * XXX add _HWMOD_STATE_WEDGED for modules that don't come back from > * _wait_target_ready() or _reset() > */ > > is it still the case, or should _reset() just return a void? There's a patch queued to pass along the return status from _reset(): http://marc.info/?l=linux-omap&m=133417544011862&w=2 As far as the new state goes, if you'd like to add a new state to indicate an IP block that fails _reset()/_wait_target_ready() and should be blocked from further use, that sounds good to me... regards, - Paul
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 2/2] ARM: omap: hwmod: Make omap_hwmod_softreset wait for reset status Date: Thu, 12 Apr 2012 11:15:00 -0600 (MDT) [thread overview] Message-ID: <alpine.DEB.2.00.1204121107450.29473@utopia.booyaka.com> (raw) In-Reply-To: <4F86D304.1020902@ti.com> Hi Rajendra, On Thu, 12 Apr 2012, Rajendra Nayak wrote: > On Thursday 12 April 2012 12:29 AM, Paul Walmsley wrote: > > That approach sounds fine to me, but I don't think Fernando's patch will > > help with I2C.. Since it uses a custom reset function omap_i2c_reset(), > > the delay will actually need to go there. > > While working on fixing this I stumbled upon a couple of other > things which don't seem right. > > The i2c custom reset funtion (omap_i2c_reset) uses a hwmod exposed > api to set the SOFTRESET bit, however it then accesses the hwmod > internal structure to poll on RESETDONE status bit. Should there be > another function exposed to poll on RESETDONE too? Sure, something like that would make sense for 3.5. > _reset() function documents its return value to be -ETIMEDOUT, if the > module fails to reset in time, and hence expects the custom reset > function to return the same in such cases. The omap_i2c_reset() function > seems to return 0 even in cases of timeout. However looking more closely > the return value from _reset() does not seem to be used in the framework > today. > > The comment in _ocp_softreset() suggests the intent was to add a new > state to the hwmod state machine. > > /* > * XXX add _HWMOD_STATE_WEDGED for modules that don't come back from > * _wait_target_ready() or _reset() > */ > > is it still the case, or should _reset() just return a void? There's a patch queued to pass along the return status from _reset(): http://marc.info/?l=linux-omap&m=133417544011862&w=2 As far as the new state goes, if you'd like to add a new state to indicate an IP block that fails _reset()/_wait_target_ready() and should be blocked from further use, that sounds good to me... regards, - Paul
next prev parent reply other threads:[~2012-04-12 17:15 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-13 17:25 [PATCH v2 0/2] Fixes in hwmod reset code Rajendra Nayak 2012-03-13 17:25 ` Rajendra Nayak 2012-03-13 17:25 ` [PATCH v2 1/2] ARM: omap: hwmod: Restore sysc after a reset Rajendra Nayak 2012-03-13 17:25 ` Rajendra Nayak 2012-03-13 17:25 ` [PATCH v2 2/2] ARM: omap: hwmod: Make omap_hwmod_softreset wait for reset status Rajendra Nayak 2012-03-13 17:25 ` Rajendra Nayak 2012-04-11 0:11 ` Paul Walmsley 2012-04-11 0:11 ` Paul Walmsley 2012-04-11 11:06 ` Rajendra Nayak 2012-04-11 11:06 ` Rajendra Nayak 2012-04-11 18:59 ` Paul Walmsley 2012-04-11 18:59 ` Paul Walmsley 2012-04-12 13:05 ` Rajendra Nayak 2012-04-12 13:05 ` Rajendra Nayak 2012-04-12 17:15 ` Paul Walmsley [this message] 2012-04-12 17:15 ` Paul Walmsley 2012-04-13 9:26 ` Rajendra Nayak 2012-04-13 9:26 ` Rajendra Nayak 2012-04-13 10:45 ` Paul Walmsley 2012-04-13 10:45 ` Paul Walmsley 2012-04-13 11:22 ` Paul Walmsley 2012-04-13 11:22 ` Paul Walmsley 2012-04-13 12:15 ` Rajendra Nayak 2012-04-13 12:15 ` Rajendra Nayak -- strict thread matches above, loose matches on Subject: below -- 2012-03-13 14:03 [PATCH v2 0/2] Fixes in hwmod reset code Rajendra Nayak 2012-03-13 14:03 ` [PATCH v2 2/2] ARM: omap: hwmod: Make omap_hwmod_softreset wait for reset status Rajendra Nayak 2012-03-13 14:03 ` Rajendra Nayak 2012-04-04 15:34 ` Paul Walmsley 2012-04-04 15:34 ` Paul Walmsley
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=alpine.DEB.2.00.1204121107450.29473@utopia.booyaka.com \ --to=paul@pwsan.com \ --cc=b-cousson@ti.com \ --cc=gadiyar@ti.com \ --cc=khilman@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=rnayak@ti.com \ --cc=shubhrajyoti@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: linkBe 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.