public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>,
	Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	Andy Green <andy.green-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Lucas De Marchi
	<lucas.demarchi-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>,
	Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: 10-bit address support in i2c-omap and i2c-davinci
Date: Mon, 7 Nov 2011 09:46:14 +0100	[thread overview]
Message-ID: <20111107094614.0062a3f7@endymion.delvare> (raw)

Both bus drivers i2c-omap and i2c-davinci apparently handle 10-bit addresses:

(i2c-omap.c)
	if (msg->flags & I2C_M_TEN)
		w |= OMAP_I2C_CON_XA;

(i2c-davinci.c)
	/* if the slave address is ten bit address, enable XA bit */
	if (msg->flags & I2C_M_TEN)
		flag |= DAVINCI_I2C_MDR_XA;

However neither driver declares functionality flag I2C_FUNC_10BIT_ADDR,
so chip drivers would normally refuse to bind to these buses. If 10-bit
address support is incomplete or broken then it should be removed
completely. If it works then these drivers should declare so by adding
I2C_FUNC_10BIT_ADDR to the functionality flags they return.

-- 
Jean Delvare

             reply	other threads:[~2011-11-07  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  8:46 Jean Delvare [this message]
2011-11-07 15:09 ` 10-bit address support in i2c-omap and i2c-davinci Kevin Hilman
2011-11-07 16:59   ` 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=20111107094614.0062a3f7@endymion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=andy.green-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=khilman-l0cyMroinI0@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lucas.demarchi-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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