From: Liam Girdwood <lrg@ti.com>
To: Ricardo Neri <ricardo.neri@ti.com>
Cc: broonie@opensource.wolfsonmicro.com, s-guiriec@ti.com,
linux-omap@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/3] ASoC: OMAP: HDMI: Update machine driver name
Date: Wed, 14 Nov 2012 10:16:56 +0000 [thread overview]
Message-ID: <50A36F98.7060103@ti.com> (raw)
In-Reply-To: <1352860249-26348-2-git-send-email-ricardo.neri@ti.com>
On 14/11/12 02:30, Ricardo Neri wrote:
> Being the name of a machine driver, it aims to describe the connection between
> the HDMI IP of the processor and the companion chip it uses to connect to the
> outside world. This name tries to follow the same naming convention as in
> the OMAP-ABE-TWL6040 machine driver.
>
> TPD12S015 is an HDMI companion chip for DC-DC step-up, I2C level shifter and
> low-capacitance ESD protection. This chip is used on all OMAP4 Pandaboards an
> SDPs as well as in OMAP5 EVMs.
>
Is the TPD12S015 passive or actively controlled by the CPU in this case ?
If it's passive then it's not really worth changing the driver name since
other OMAP4/5 devices may use other HDMI companion chips (an we can reuse this
driver without changes).
Liam
next prev parent reply other threads:[~2012-11-14 10:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 2:30 [PATCH 0/3] Updated names for ASoC OMAP HDMI drivers Ricardo Neri
2012-11-14 2:30 ` [PATCH 1/3] ASoC: OMAP: HDMI: Update machine driver name Ricardo Neri
2012-11-14 10:16 ` Liam Girdwood [this message]
2012-11-14 17:00 ` Ricardo Neri
2012-11-14 2:30 ` [PATCH 2/3] ASoC: OMAP: HDMI: Update CPU DAI " Ricardo Neri
2012-11-14 2:30 ` [PATCH 3/3] ASoC: OMAP: HDMI: Obtain DMA port from resources Ricardo Neri
2012-11-14 3:27 ` Mark Brown
2012-11-14 17:07 ` Ricardo Neri
2012-11-14 23:08 ` Mark Brown
2012-11-15 2:33 ` Ricardo Neri
2012-11-15 4:10 ` Mark Brown
2012-11-15 16:22 ` Ricardo Neri
2012-11-15 9:45 ` Tomi Valkeinen
2012-11-15 12:36 ` Tomi Valkeinen
2012-11-16 1:39 ` Ricardo Neri
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=50A36F98.7060103@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@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 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.