From: Shinya Kuribayashi <shinya.kuribayashi.px-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
To: Linus Walleij <linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Cc: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sundar R Iyer
<sundar.iyer-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Subject: Re: [PATCH 3/4] i2c-nomadik: support smbus emulation
Date: Fri, 24 Sep 2010 12:47:15 +0900 [thread overview]
Message-ID: <4C9C1F43.4080105@renesas.com> (raw)
In-Reply-To: <1285225443-1036-1-git-send-email-linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
On 9/23/2010 4:04 PM, Linus Walleij wrote:
> We can do smbus emulation so flag this and drop the duplicate
> flags implied from smbus emulation.
> @@ -803,10 +803,7 @@ static irqreturn_t i2c_irq_handler(int irq, void *arg)
>
> static unsigned int nmk_i2c_functionality(struct i2c_adapter *adap)
> {
> - return I2C_FUNC_I2C
> - | I2C_FUNC_SMBUS_BYTE_DATA
> - | I2C_FUNC_SMBUS_WORD_DATA
> - | I2C_FUNC_SMBUS_I2C_BLOCK;
> + return I2C_FUNC_I2C | I2C_FUNC_SMBUS_EMUL;
> }
>
> static const struct i2c_algorithm nmk_i2c_algo = {
(failed to figure out from the driver, so would like to make sure)
Is this I2C core capable of I2C_FUNC_SMBUS_QUICK? Unless it's capable
of full SMBus emulation, it would be better to turn off relevant flags
for safety. I'm not objecting to the patch, but just wondered.
--
Shinya Kuribayashi
Renesas Electronics
next prev parent reply other threads:[~2010-09-24 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 7:04 [PATCH 3/4] i2c-nomadik: support smbus emulation Linus Walleij
[not found] ` <1285225443-1036-1-git-send-email-linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
2010-09-24 3:47 ` Shinya Kuribayashi [this message]
[not found] ` <4C9C1F43.4080105-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2010-09-27 9:00 ` Linus Walleij
[not found] ` <AANLkTimUWdKcMAA_1TrXNL4YDYJ7dUhVh9LLYQ_48NLh-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-27 9:09 ` Shinya Kuribayashi
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=4C9C1F43.4080105@renesas.com \
--to=shinya.kuribayashi.px-zm6kxycvzfbbdgjk7y7tuq@public.gmane.org \
--cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sundar.iyer-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.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 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.