From: David Brownell <david-b@pacbell.net>
To: davinci-linux-open-source@linux.davincidsp.com,
Hans Verkuil <hverkuil@xs4all.nl>
Cc: m-karicheri2@ti.com,
Muralidharan Karicheri <a0868495@dal.design.ti.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 7/10 - v2] DM355 platform changes for vpfe capture driver
Date: Sun, 14 Jun 2009 12:42:45 -0700 [thread overview]
Message-ID: <200906141242.45851.david-b@pacbell.net> (raw)
In-Reply-To: <200906141622.55197.hverkuil@xs4all.nl>
On Sunday 14 June 2009, Hans Verkuil wrote:
> > /* { I2C_BOARD_INFO("tlv320aic3x", 0x1b), }, */
>
> Huh? What's this? I only know the tlv320aic23b and that's an audio driver.
AIC33 is another audio codec chip:
http://focus.ti.com/docs/prod/folders/print/tlv320aic33.html
One can't list audio codecs with other board-specific data until
the ASoC initialization gets re-worked to allow it. That's why
it's commented out of the list-of-i2c-devices-on-the-board.
next prev parent reply other threads:[~2009-06-14 19:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 17:00 [PATCH 0/10 - v2] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver m-karicheri2
2009-06-11 17:00 ` [PATCH 1/10 - v2] vpfe capture bridge driver for DM355 and DM6446 m-karicheri2
2009-06-11 17:00 ` [PATCH 2/10 - v2] ccdc hw device header file for vpfe capture m-karicheri2
2009-06-11 17:00 ` [PATCH 3/10 - v2] dm355 ccdc module for vpfe capture driver m-karicheri2
2009-06-11 17:00 ` [PATCH 4/10 - v2] dm644x " m-karicheri2
2009-06-11 17:00 ` [PATCH 5/10 - v2] ccdc types used across ccdc modules " m-karicheri2
2009-06-11 17:00 ` [PATCH 6/10 - v2] Makefile and config files " m-karicheri2
2009-06-11 17:00 ` [PATCH 7/10 - v2] DM355 platform changes " m-karicheri2
2009-06-11 17:00 ` [PATCH 8/10 - v2] DM6446 " m-karicheri2
2009-06-11 17:00 ` [PATCH 9/10 - v2] remove outdated video driver files of dm6446 m-karicheri2
2009-06-11 17:00 ` [PATCH 10/10 - v2] common vpss module for video drivers m-karicheri2
2009-06-11 23:23 ` Alexey Klimov
2009-06-15 17:42 ` Karicheri, Muralidharan
2009-06-14 14:26 ` Hans Verkuil
2009-06-11 20:23 ` [PATCH 9/10 - v2] remove outdated video driver files of dm6446 Kevin Hilman
2009-06-12 15:07 ` Karicheri, Muralidharan
2009-06-14 14:24 ` [PATCH 8/10 - v2] DM6446 platform changes for vpfe capture driver Hans Verkuil
2009-06-11 20:23 ` [PATCH 7/10 - v2] DM355 " David Brownell
2009-06-14 14:22 ` Hans Verkuil
2009-06-14 19:42 ` David Brownell [this message]
2009-06-15 22:24 ` Karicheri, Muralidharan
2009-06-15 22:40 ` Hans Verkuil
2009-06-11 22:41 ` [PATCH 1/10 - v2] vpfe capture bridge driver for DM355 and DM6446 Alexey Klimov
2009-06-15 17:41 ` Karicheri, Muralidharan
2009-06-14 14:10 ` Hans Verkuil
2009-06-15 21:47 ` Karicheri, Muralidharan
2009-06-15 22:29 ` Hans Verkuil
2009-06-16 14:26 ` Karicheri, Muralidharan
2009-06-17 6:39 ` Hans Verkuil
2009-06-17 15:02 ` Karicheri, Muralidharan
2009-06-17 19:05 ` Hans Verkuil
2009-06-11 20:24 ` [PATCH 0/10 - v2] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver David Brownell
2009-06-12 15:58 ` Karicheri, Muralidharan
-- strict thread matches above, loose matches on Subject: below --
2009-06-09 18:50 [PATCH 7/10 - v2] DM355 platform changes for vpfe capture driver m-karicheri2
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=200906141242.45851.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=a0868495@dal.design.ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m-karicheri2@ti.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