From: Lars-Peter Clausen <lars@metafoo.de>
To: Florian Meier <florian.meier@koalo.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] ASoC: Adding trivial codec drivers
Date: Sun, 05 Jan 2014 17:01:22 +0100 [thread overview]
Message-ID: <52C981D2.2020800@metafoo.de> (raw)
In-Reply-To: <52C95977.5070400@koalo.de>
On 01/05/2014 02:09 PM, Florian Meier wrote:
> This is not intended to be a real patch.
> I would just like to ask if this is the preferred way
> to add codec and machine driver for codecs without
> I2C or SPI configuration possibilities or should I
> rather use a more generic approach?
>
Should be fine. There are a couple of other similar drivers.
- Lars
WARNING: multiple messages have this Message-ID (diff)
From: Lars-Peter Clausen <lars@metafoo.de>
To: Florian Meier <florian.meier@koalo.de>
Cc: Mark Brown <broonie@kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] [RFC] ASoC: Adding trivial codec drivers
Date: Sun, 05 Jan 2014 17:01:22 +0100 [thread overview]
Message-ID: <52C981D2.2020800@metafoo.de> (raw)
In-Reply-To: <52C95977.5070400@koalo.de>
On 01/05/2014 02:09 PM, Florian Meier wrote:
> This is not intended to be a real patch.
> I would just like to ask if this is the preferred way
> to add codec and machine driver for codecs without
> I2C or SPI configuration possibilities or should I
> rather use a more generic approach?
>
Should be fine. There are a couple of other similar drivers.
- Lars
next prev parent reply other threads:[~2014-01-05 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 13:09 [RFC] ASoC: Adding trivial codec drivers Florian Meier
2014-01-05 16:01 ` Lars-Peter Clausen [this message]
2014-01-05 16:01 ` [alsa-devel] " Lars-Peter Clausen
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=52C981D2.2020800@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=florian.meier@koalo.de \
--cc=linux-kernel@vger.kernel.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 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.