From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] i2c-i801: Add PCI idents for Patsburg 'IDF' SMBus controllers
Date: Sun, 31 Oct 2010 21:11:59 +0100 [thread overview]
Message-ID: <20101031211159.0766e5f2@endymion.delvare> (raw)
In-Reply-To: <1288538652.4570.52.camel-uXGAPMMVk8bAQYKIod7YupZV94DADvEd@public.gmane.org>
On Sun, 31 Oct 2010 11:24:12 -0400, David Woodhouse wrote:
> These are the extra 'Integrated Device Function' SMBus controllers found
> on the Patsburg chipset. Mention the absence of slave mode support.
>
> Signed-off-by: David Woodhouse <David.Woodhouse-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> ---
> Seth already added the host controller ID, calling it 'Patsburg'. So
> I'll call it 'Patsburg' too, and just add the additional controllers.
Applied, thanks.
>
> We should probably add a column in the hardware support table indicating
> which devices support slave mode. The Patsburg host does; the IDF
> controllers don't. Not sure how many older devices have slave mode.
I agree. Feel free to only add the yes/no flag in that column for the
devices for which you know the answer, and we can populate the rest
later. All the datasheets are available so it should be doable although
this will take some time due to the large number of supported devices.
That being said, this column will really only start being interesting
if/when we actually implement support for the slave mode. Not sure who
needs this.
--
Jean Delvare
prev parent reply other threads:[~2010-10-31 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 15:24 [PATCH 2/2] i2c-i801: Add PCI idents for Patsburg 'IDF' SMBus controllers David Woodhouse
[not found] ` <1288538652.4570.52.camel-uXGAPMMVk8bAQYKIod7YupZV94DADvEd@public.gmane.org>
2010-10-31 20:11 ` Jean Delvare [this message]
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=20101031211159.0766e5f2@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox