From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: Brian Austin <brian.austin@cirrus.com>,
"vinod.koul@linux.intel.com" <vinod.koul@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"ramesh.babu@intel.com" <ramesh.babu@intel.com>,
"joe@nucleusys.com" <joe@nucleusys.com>,
"heelrod@heelrod.ad.cirrus.com" <heelrod@heelrod.ad.cirrus.com>,
"lrg@ti.com" <lrg@ti.com>
Subject: Re: [PATCH v3] ASoC: Add support for cs42l73 codec
Date: Fri, 7 Oct 2011 11:27:41 +0100 [thread overview]
Message-ID: <20111007102740.GF19080@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOZdJXV4+ZUZptZEjqwQugPmmav7wsXkw9ORrsVMPVzOTahc-g@mail.gmail.com>
On Fri, Oct 07, 2011 at 02:13:32AM +0000, Tabi Timur-B04825 wrote:
> > +/* I2C Registers */
> > +/* I2C Address: 1001010[R/W] - 10010100 = 0x94(Write); 10010101 = 0x95(Read) */
> This chip has separate I2C addresses for reading and writing?
This is standard - the I2C address can be quoted in either 8 bit form
(where the lowest bit is a read write flag) or 7 bit form. The
confusing thing here is that the Linux code uses the 7 bit form
exclusively.
prev parent reply other threads:[~2011-10-07 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 16:19 [PATCH v3] ASoC: Add support for cs42l73 codec Brian Austin
2011-10-06 18:57 ` Mark Brown
2011-10-06 19:15 ` Austin, Brian
2011-10-07 10:34 ` Mark Brown
2011-10-07 11:07 ` Vinod Koul
2011-10-07 11:42 ` Mark Brown
2011-10-07 14:05 ` Austin, Brian
2011-10-07 14:27 ` Mark Brown
2011-10-07 14:29 ` Vinod Koul
2011-10-12 15:58 ` Austin, Brian
2011-10-12 21:37 ` Austin, Brian
2011-10-12 21:50 ` Austin, Brian
2011-10-12 21:55 ` Austin, Brian
2011-10-17 19:11 ` Austin, Brian
2011-10-17 20:15 ` Mark Brown
2011-10-07 3:59 ` Vinod Koul
2011-10-07 2:13 ` Tabi Timur-B04825
2011-10-07 10:27 ` Mark Brown [this message]
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=20111007102740.GF19080@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=B04825@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=heelrod@heelrod.ad.cirrus.com \
--cc=joe@nucleusys.com \
--cc=lrg@ti.com \
--cc=ramesh.babu@intel.com \
--cc=vinod.koul@linux.intel.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 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).