From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org,
hennerich-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org
Subject: Re: [PATCH] i2c-pcf8575: check for errors when accessing the chip
Date: Thu, 15 May 2008 20:54:16 +0200 [thread overview]
Message-ID: <20080515205416.0a6bdaf9@hyperion.delvare> (raw)
In-Reply-To: <1210862127-9493-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Hi Wolfram,
On Thu, 15 May 2008 16:35:27 +0200, Wolfram Sang wrote:
> Make the driver check and report error cases when reading from or writing to
> the chip. It used to assume 'always success' and could even deliver bogus
> values.
>
> Signed-off-by: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
> ---
>
> The PCF on my system seems broken, it does not respond (and I can't probe as my
> master doesn't support smbus_quick). The broken chip went unnoticed as the
> driver reported some (= bogus) values. So, I can only test the properly
> reported error cases, hopefully someone else can confirm the working case.
> (Michael and Bart, sorry for double post)
>
> drivers/i2c/chips/pcf8575.c | 29 +++++++++++++++++++++--------
> 1 files changed, 21 insertions(+), 8 deletions(-)
This driver is deprecated and you should be using
drivers/gpio/pcf857x.c instead if you can. That driver properly handles
I/O errors as far as I can see.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-05-15 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:35 [PATCH] i2c-pcf8575: check for errors when accessing the chip Wolfram Sang
[not found] ` <1210862127-9493-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-05-15 18:54 ` Jean Delvare [this message]
[not found] ` <20080515205416.0a6bdaf9-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-05-15 19:15 ` Wolfram Sang
[not found] ` <20080515191559.GA16057-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-05-15 19:21 ` Jean Delvare
[not found] ` <20080515212108.17b3c578-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-05-15 19:47 ` Wolfram Sang
2008-05-15 19:33 ` Jean Delvare
[not found] <1210861753-9449-1-git-send-email-w.sang@pengutronix.de>
[not found] ` <1210861753-9449-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-05-16 6:10 ` Bart Van Assche
2008-05-22 11:14 ` Bart Van Assche
[not found] ` <e2e108260805220414t5e9017gfe3e82ceb6cf38ad-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-22 13:45 ` Robert Schwebel
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=20080515205416.0a6bdaf9@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hennerich-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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.