From: Nishanth Menon <nm@ti.com>
To: "Datta, Shubhrajyoti" <shubhrajyoti@ti.com>
Cc: "felipe.balbi@nokia.com" <felipe.balbi@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] [RFC] Remove the debug print noise
Date: Mon, 2 Aug 2010 08:47:06 -0500 [thread overview]
Message-ID: <4C56CC5A.3040708@ti.com> (raw)
In-Reply-To: <0680EC522D0CC943BC586913CF3768C003B38719CA@dbde02.ent.ti.com>
Datta, Shubhrajyoti had written, on 08/02/2010 07:59 AM, the following:
>
>> -----Original Message-----
>> From: Felipe Balbi [mailto:felipe.balbi@nokia.com]
>> Sent: Monday, August 02, 2010 6:22 PM
>> To: Datta, Shubhrajyoti
>> Cc: linux-omap@vger.kernel.org; Tony Lindgren
>> Subject: Re: [PATCH] [RFC] Remove the debug print noise
>>
>> Hi,
>>
>> On Mon, Aug 02, 2010 at 02:47:51PM +0200, ext Shubhrajyoti D wrote:
>>> @@ -626,7 +626,7 @@ static int omap_i2c_xfer_msg(struct i2c_adapter
>> *adap,
>>> if (r < 0)
>>> return r;
>>> if (r == 0) {
>>> - dev_err(dev->dev, "controller timed out\n");
>>> + dev_dbg(dev->dev, "controller timed out\n");
>> you would better be searching for the cause of the timeout. 1 second is
>> enough time (or should be) for any i2c command to complete. If you have
>> an easy way to reproduce this problem, then better search for its
>> rootcause. If I remember correctly, this timeout was put here for a good
>> reason.
>
> The reason I am getting the timeout is that there isn't a device to respond in that address However
> # ./i2cdetect -y -r 3
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- 29 -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- 48 -- -- 4b -- -- -- --
>
> Is more readable than
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: -- i2c_omap i2c_omap.3: controller timed out
> -- -- i2c_omap i2c_omap.3: controller timed out
> -- -- i2c_omap i2c_omap.3: controller timed out
> -- -- i2c_omap i2c_omap.3: controller timed out
> -- -- i2c_omap i2c_omap.3: controller timed out
> -- -- i2c_omap i2c_omap.3: controller timed out
> -- --
>
this is still not a debug message -> dev_warn perhaps to flag that this
is indeed an error from the driver point of view?
>> Tony, any comments ?
>>
>> --
>> balbi
>>
>> DefectiveByDesign.org
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-08-02 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:47 [PATCH] [RFC] Remove the debug print noise Shubhrajyoti D
2010-08-02 12:52 ` Felipe Balbi
2010-08-02 12:59 ` Datta, Shubhrajyoti
2010-08-02 13:47 ` Nishanth Menon [this message]
2010-08-06 9:14 ` Tony Lindgren
2010-08-10 10:39 ` DebBarma, Tarun Kanti
2010-08-10 11:52 ` Felipe Balbi
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=4C56CC5A.3040708@ti.com \
--to=nm@ti.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=shubhrajyoti@ti.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.