linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Crane Cai <crane.cai-5C7GfCeVMHo@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Shane Huang <shane.huang-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH] I2C: add driver for SMBus Control Method Interface
Date: Fri, 11 Sep 2009 16:27:40 +0800	[thread overview]
Message-ID: <20090911082740.GC22058@crane-desktop> (raw)
In-Reply-To: <20090909180431.5253d624-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

Hi Jean,

On Wed, Sep 09, 2009 at 06:04:31PM +0200, Jean Delvare wrote:
> Hi Crane,
> 
> On Thu, 27 Aug 2009 10:29:58 +0800, Crane Cai wrote:
> > This driver supports the SMBus Control Method Interface. It needs BIOS declare
> > ACPI control methods via SMBus Control Method Interface Spec.
> > http://smbus.org/specs/smbus_cmi10.pdf
> > 
> > Hi Jean,
> > This driver can give BIOS a chance to avoid SMBus access conflicts on runtime.
> > And it obeys the SMBus CMI spec.
> > Please apply.
> 
> This is very interesting. Do you happen to have, or know, systems which
> actually implement this? Were you able to test your code?
Till now I only know our internal BIOS implement this control method. 
The code has been tested.
> 
> How can I check if any of my systems do implement this?
Now BIOS team give us an option to let these control methods exported.
> 
> Full review below, inline. I had many comments but they are really
> small things, overall your code is very good and getting the driver in
> shape for 2.6.32 seems totally feasible.
Thanks, these comments are very important to me. I will rework my code on them
and retest and resubmit a new version. It needs some days.
> 

-- 
Best Regards,
- Crane

  parent reply	other threads:[~2009-09-11  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  2:29 [PATCH] I2C: add driver for SMBus Control Method Interface Crane Cai
2009-09-09 16:04 ` Jean Delvare
     [not found]   ` <20090909180431.5253d624-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-11  8:27     ` Crane Cai [this message]
2009-09-16  9:35     ` Crane Cai

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=20090911082740.GC22058@crane-desktop \
    --to=crane.cai-5c7gfcevmho@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shane.huang-5C7GfCeVMHo@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;
as well as URLs for NNTP newsgroup(s).