public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Fabien Marteau <lepingouin.tux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: SMBus quick command problem
Date: Fri, 9 Jan 2009 16:12:22 +0100	[thread overview]
Message-ID: <20090109161222.4c75ffda@hyperion.delvare> (raw)
In-Reply-To: <ce62e9d00901090703y5af1ba4diedf37d30da5d158a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Fri, 9 Jan 2009 16:03:11 +0100, Fabien Marteau wrote:
> Thanks Jean,
> 
> In fact I'm using the i2c-ocore (opencore) controller, and the «SMBus
> Quick Command» block the bus with the Linux standard driver
> (drivers/i2c/busses/i2c-ocores.c):
> http://www.opencores.org/forums.cgi/cores/2008/10/003391
> 
> Then to solve this problem I'm re-writing the driver to support each
> SMBus commands separately, following the linux documentation.
> If writing '1' on quick command block the bus, I will skip this test.

I don't get where you're going with rewriting the driver. You'll end up
with a larger driver doing exactly the same, without taking benefit of
the SMBus emulation layer from i2c-core. If the hardware has a problem
with Quick commands, rewriting the driver won't solve that. Better
intercept that case in the current driver and return an error.

Not that it really matters though, as I have yet to see any real-world
use case for the Quick command with data bit = 1. So what problem are
you trying to solve exactly?

-- 
Jean Delvare

  parent reply	other threads:[~2009-01-09 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  9:01 SMBus quick command problem Fabien Marteau
     [not found] ` <ce62e9d00901080101ocfa0388g91698776eb9704cb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-09 14:27   ` Jean Delvare
     [not found]     ` <20090109152752.29b3c5de-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-09 15:03       ` Fabien Marteau
     [not found]         ` <ce62e9d00901090703y5af1ba4diedf37d30da5d158a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-09 15:12           ` Jean Delvare [this message]
     [not found]             ` <20090109161222.4c75ffda-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-09 17:11               ` Fabien Marteau
     [not found]                 ` <ce62e9d00901090911r7454ae5fr61c69a22704ed86b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-09 17:38                   ` Jean Delvare

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=20090109161222.4c75ffda@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=lepingouin.tux-Re5JQEeQqe8AvxtiuMwx3w@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