From: Antti Palosaari <crope@iki.fi>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: mchehab@redhat.com, linux-media@vger.kernel.org,
dheitmueller@kernellabs.com
Subject: Re: [PATCH 5/5] em28xx: fix+improve+unify i2c error handling, debug messages and code comments
Date: Fri, 14 Dec 2012 19:03:52 +0200 [thread overview]
Message-ID: <50CB5BF8.5070201@iki.fi> (raw)
In-Reply-To: <1355502533-25636-6-git-send-email-fschaefer.oss@googlemail.com>
On 12/14/2012 06:28 PM, Frank Schäfer wrote:
> - check i2c slave address range (only 7 bit addresses supported)
> - do not pass USB specific error codes to userspace/i2c-subsystem
> - unify the returned error codes and make them compliant with
> the i2c subsystem spec
> - check number of actually transferred bytes (via USB) everywehere
> - fix/improve debug messages
> - improve code comments
>
> Signed-off-by: Frank Schäfer <fschaefer.oss@googlemail.com>
> @@ -244,16 +294,20 @@ static int em28xx_i2c_xfer(struct i2c_adapter *i2c_adap,
> dprintk2(2, "%s %s addr=%x len=%d:",
> (msgs[i].flags & I2C_M_RD) ? "read" : "write",
> i == num - 1 ? "stop" : "nonstop", addr, msgs[i].len);
> + if (addr > 0xff) {
> + dprintk2(2, " ERROR: 10 bit addresses not supported\n");
> + return -EOPNOTSUPP;
> + }
There is own flag for 10bit I2C address. Use it (and likely not compare
at all addr validly like that). This kind of address validation check is
quite unnecessary - and after all if it is wanted then correct place is
somewhere in I2C routines.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-12-14 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 16:28 [PATCH 0/5] em28xx: i2c bug fixes and cleanups Frank Schäfer
2012-12-14 16:28 ` [PATCH 1/5] em28xx: clean up the data type mess of the i2c transfer function parameters Frank Schäfer
2012-12-14 16:28 ` [PATCH 2/5] em28xx: respect the message size constraints for i2c transfers Frank Schäfer
2012-12-14 16:55 ` Antti Palosaari
2012-12-15 12:57 ` Frank Schäfer
2012-12-14 16:28 ` [PATCH 3/5] em28xx: fix two severe bugs in function em2800_i2c_recv_bytes() Frank Schäfer
2012-12-14 16:28 ` [PATCH 4/5] em28xx: fix the i2c adapter functionality flags Frank Schäfer
2012-12-14 16:28 ` [PATCH 5/5] em28xx: fix+improve+unify i2c error handling, debug messages and code comments Frank Schäfer
2012-12-14 17:03 ` Antti Palosaari [this message]
2012-12-15 13:01 ` Frank Schäfer
2012-12-15 13:46 ` Antti Palosaari
2012-12-15 16:25 ` Frank Schäfer
2012-12-15 17:16 ` Antti Palosaari
2012-12-16 18:20 ` Frank Schäfer
2012-12-15 17:18 ` Mauro Carvalho Chehab
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=50CB5BF8.5070201@iki.fi \
--to=crope@iki.fi \
--cc=dheitmueller@kernellabs.com \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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.