From: Shubhrajyoti <shubhrajyoti@ti.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP: I2C: prepare to use hwmod reset in driver
Date: Mon, 19 Dec 2011 23:07:40 +0530 [thread overview]
Message-ID: <4EEF7664.3000203@ti.com> (raw)
In-Reply-To: <4EEF6714.2040208@ti.com>
On Monday 19 December 2011 10:02 PM, Cousson, Benoit wrote:
> Hi Shubhro,
>
> On 12/18/2011 9:01 AM, Shubhrajyoti wrote:
>
> [...]
>
>> The driver does a reset in the error path.
>> Since we are not supposed to access the sysc reg the function is needed.
>
> I'm just wondering what will happen to the driver if this callback is
> not provided during the device creation? This is what will happen
> during DT boot for example?
>
> Is it a mandatory function?
This is used in the recovery mechanism in case of errors like some one
holding the bus and not releasing it etc.
>
> Thanks,
> Benoit
WARNING: multiple messages have this Message-ID (diff)
From: shubhrajyoti@ti.com (Shubhrajyoti)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: I2C: prepare to use hwmod reset in driver
Date: Mon, 19 Dec 2011 23:07:40 +0530 [thread overview]
Message-ID: <4EEF7664.3000203@ti.com> (raw)
In-Reply-To: <4EEF6714.2040208@ti.com>
On Monday 19 December 2011 10:02 PM, Cousson, Benoit wrote:
> Hi Shubhro,
>
> On 12/18/2011 9:01 AM, Shubhrajyoti wrote:
>
> [...]
>
>> The driver does a reset in the error path.
>> Since we are not supposed to access the sysc reg the function is needed.
>
> I'm just wondering what will happen to the driver if this callback is
> not provided during the device creation? This is what will happen
> during DT boot for example?
>
> Is it a mandatory function?
This is used in the recovery mechanism in case of errors like some one
holding the bus and not releasing it etc.
>
> Thanks,
> Benoit
next prev parent reply other threads:[~2011-12-19 17:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 9:55 [GIT PULL] ARM: OMAP: I2C: prepare to use hwmod reset in driver Paul Walmsley
2011-12-16 9:55 ` Paul Walmsley
2011-12-16 19:50 ` Tony Lindgren
2011-12-16 19:50 ` Tony Lindgren
2011-12-16 20:17 ` Paul Walmsley
2011-12-16 20:17 ` Paul Walmsley
2011-12-16 20:41 ` Tony Lindgren
2011-12-16 20:41 ` Tony Lindgren
2011-12-16 20:59 ` Paul Walmsley
2011-12-16 20:59 ` Paul Walmsley
2011-12-17 0:24 ` Tony Lindgren
2011-12-17 0:24 ` Tony Lindgren
2011-12-18 8:01 ` Shubhrajyoti
2011-12-18 8:01 ` Shubhrajyoti
2011-12-19 16:32 ` Cousson, Benoit
2011-12-19 16:32 ` Cousson, Benoit
2011-12-19 17:37 ` Shubhrajyoti [this message]
2011-12-19 17:37 ` Shubhrajyoti
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=4EEF7664.3000203@ti.com \
--to=shubhrajyoti@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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.