From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Vladimir Barinov <vbarinov@embeddedalley.com>,
alsa-devel@alsa-project.org,
Lauri Leukkunen <lauri.leukkunen@nokia.com>
Subject: Re: tlv32aic3x, rx-51, regulator
Date: Thu, 05 Jan 2012 13:24:39 +0200 [thread overview]
Message-ID: <4F058877.5010005@bitmer.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1201051057240.13332@pmeerw.net>
Hi
On 05/01/12 12:02, Peter Meerwald wrote:
> Hello,
>
> the tlv320aic3x codec driver requests a number of supplies/regulators
> (IOVDD, DVDD, AVDD, DRVDD), these seem mandatory for the codec driver to
> operate and somehow tied to the rx51 platform
>
They are the supply voltages for the aix3x codecs and not tied to rx51 only.
> I want to use the tlv320aic3x codec driver with some other board where I
> don't care about supplies/regulators -- how is this going to work? do I
> need to have dummy supplies just to keep tlv320aic3x happy?
>
> shouldn't the ai3x_supply_names be something that is optional and passed
> in via platform_data?
>
Simplest option in case you don't have *any* controllable regulator or
if the kernel is not touching them is to not enable CONFIG_REGULATOR.
IMHO optional platform data for CONFIG_REGULATOR=y case doesn't win much
over defining fixed voltage regulators. Either it would be duplicate
information or needs modification to a machine driver anyway. And the
regulator framework can be useful in debugging too, like following the
use_counts via sysfs and so on.
--
Jarkko
prev parent reply other threads:[~2012-01-05 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 10:02 tlv32aic3x, rx-51, regulator Peter Meerwald
2012-01-05 11:24 ` Jarkko Nikula [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=4F058877.5010005@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=alsa-devel@alsa-project.org \
--cc=lauri.leukkunen@nokia.com \
--cc=pmeerw@pmeerw.net \
--cc=vbarinov@embeddedalley.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).