From: Wolfram Sang <wsa@the-dreams.de>
To: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
Cc: linux-i2c@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
naveenkrishna.ch@gmail.com, ben-linux@fluff.org,
cpgs@samsung.com, broonie@kernel.org,
Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [PATCH] i2c: s3c2410: do not put a default class for the adapter
Date: Sat, 15 Feb 2014 16:10:39 +0100 [thread overview]
Message-ID: <20140215151039.GE2579@katana> (raw)
In-Reply-To: <1391761795-28384-1-git-send-email-ch.naveen@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On Fri, Feb 07, 2014 at 01:59:55PM +0530, Naveen Krishna Chatradhi wrote:
> From: Vincent Palatin <vpalatin@chromium.org>
>
> Avoid adding I2C_CLASS_HWMON and I2C_CLASS_SPD class flags to all
> Samsung I2C adapters when the I2C mappings are defined in a device tree.
> So the drivers doing an auto-detection by probing busses won't mess-up
> sensitive I2C devices or trigger long timeouts on non-functional busses.
>
> Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
> Reviewed-by: Olof Johansson <olofj@chromium.org>
> Tested-by: Vincent Palatin <vpalatin@chromium.org>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
I'd prefer to drop it in favour of this series:
http://lkml.org/lkml/2014/2/10/836
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-15 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:29 [PATCH] i2c: s3c2410: do not put a default class for the adapter Naveen Krishna Chatradhi
2014-02-15 15:10 ` Wolfram Sang [this message]
2014-03-12 19:23 ` Wolfram Sang
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=20140215151039.GE2579@katana \
--to=wsa@the-dreams.de \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=ch.naveen@samsung.com \
--cc=cpgs@samsung.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=naveenkrishna.ch@gmail.com \
--cc=vpalatin@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).