All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Shubhrajyoti <shubhrajyoti@ti.com>
Cc: balajitk@ti.com, rnayak@ti.com, santosh.shilimkar@ti.com,
	linux-i2c@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv5 1/3] OMAP: I2C: Reset support
Date: Thu, 04 Aug 2011 08:05:20 -0700	[thread overview]
Message-ID: <87d3gl43pr.fsf@ti.com> (raw)
In-Reply-To: <4E3A3B48.2050108@ti.com> (shubhrajyoti@ti.com's message of "Thu, 04 Aug 2011 11:55:12 +0530")

Shubhrajyoti <shubhrajyoti@ti.com> writes:

> On Wednesday 03 August 2011 04:53 AM, Kevin Hilman wrote:
>> Shubhrajyoti D<shubhrajyoti@ti.com>  writes:
>>
>>>   Under some error conditions the i2c  driver may do a reset.
>>    ^                                    ^
>> minor: extra whitespace
>>
>>>   Adding a reset field and support in the platform.
>> s/platform/device-specific code/
>>
> Yes will fix these.
>>> Signed-off-by: Shubhrajyoti D<shubhrajyoti@ti.com>
>> That being said, omap_device_shutdown() should already do a clean
>> shutdown + reset for you, and i2c-omap.h already has a pointer for
>> ->device_shutdown() so a new device_reset() should not be needed.
>>
>> IOW, simply adding pdata->device_shutdown = omap_device_shutdown()
>> should work.
> i2C has a special reset sequence ie Disable -> reset -> enable -> Poll
> on reset done.
> This function is implemented in omap_i2c_reset. The
>
> omap_hwmod_reset calls ->  _reset
>
> which calls ocp_softrest  or custom reset if it is present.The latter
> is true for I2C.
>
> However I see that
>
> omap_device_shutdown ->  _assert_hardreset However for I2c there doesnt seem to be a HW reset line.
>
>
> Am I missing something?
>

No, my fault.

I thought omap_device_shutdown() also did soft reset, but I see that's
not the case.  You can ignore my comments about using
omap_device_shutdown.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 1/3] OMAP: I2C: Reset support
Date: Thu, 04 Aug 2011 08:05:20 -0700	[thread overview]
Message-ID: <87d3gl43pr.fsf@ti.com> (raw)
In-Reply-To: <4E3A3B48.2050108@ti.com> (shubhrajyoti@ti.com's message of "Thu, 04 Aug 2011 11:55:12 +0530")

Shubhrajyoti <shubhrajyoti@ti.com> writes:

> On Wednesday 03 August 2011 04:53 AM, Kevin Hilman wrote:
>> Shubhrajyoti D<shubhrajyoti@ti.com>  writes:
>>
>>>   Under some error conditions the i2c  driver may do a reset.
>>    ^                                    ^
>> minor: extra whitespace
>>
>>>   Adding a reset field and support in the platform.
>> s/platform/device-specific code/
>>
> Yes will fix these.
>>> Signed-off-by: Shubhrajyoti D<shubhrajyoti@ti.com>
>> That being said, omap_device_shutdown() should already do a clean
>> shutdown + reset for you, and i2c-omap.h already has a pointer for
>> ->device_shutdown() so a new device_reset() should not be needed.
>>
>> IOW, simply adding pdata->device_shutdown = omap_device_shutdown()
>> should work.
> i2C has a special reset sequence ie Disable -> reset -> enable -> Poll
> on reset done.
> This function is implemented in omap_i2c_reset. The
>
> omap_hwmod_reset calls ->  _reset
>
> which calls ocp_softrest  or custom reset if it is present.The latter
> is true for I2C.
>
> However I see that
>
> omap_device_shutdown ->  _assert_hardreset However for I2c there doesnt seem to be a HW reset line.
>
>
> Am I missing something?
>

No, my fault.

I thought omap_device_shutdown() also did soft reset, but I see that's
not the case.  You can ignore my comments about using
omap_device_shutdown.

Kevin

  reply	other threads:[~2011-08-04 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 10:36 [PATCHv5 0/3] I2C driver updates Shubhrajyoti D
2011-07-29 10:36 ` Shubhrajyoti D
2011-07-29 10:36 ` [PATCHv5 2/3] OMAP: I2C: Remove the reset in the init path Shubhrajyoti D
2011-07-29 10:36   ` Shubhrajyoti D
     [not found]   ` <1311935813-8481-3-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-08-02 23:27     ` Kevin Hilman
2011-08-02 23:27       ` Kevin Hilman
     [not found]       ` <87d3gn75sh.fsf-l0cyMroinI0@public.gmane.org>
2011-08-04 16:41         ` Shubhrajyoti
2011-08-04 16:41           ` Shubhrajyoti
     [not found] ` <1311935813-8481-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-07-29 10:36   ` [PATCHv5 1/3] OMAP: I2C: Reset support Shubhrajyoti D
2011-07-29 10:36     ` Shubhrajyoti D
     [not found]     ` <1311935813-8481-2-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-08-02 23:23       ` Kevin Hilman
2011-08-02 23:23         ` Kevin Hilman
     [not found]         ` <87sjpj75yq.fsf-l0cyMroinI0@public.gmane.org>
2011-08-04  6:25           ` Shubhrajyoti
2011-08-04  6:25             ` Shubhrajyoti
2011-08-04 15:05             ` Kevin Hilman [this message]
2011-08-04 15:05               ` Kevin Hilman
2011-07-29 10:36   ` [PATCHv5 3/3] OMAP: I2C: Remove the SYSC register definition Shubhrajyoti D
2011-07-29 10:36     ` Shubhrajyoti D

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=87d3gl43pr.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=balajitk@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.com \
    --cc=santosh.shilimkar@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: link
Be 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.