From: Mark Brown <broonie@kernel.org>
To: "Leslie Hsia(夏邦進_Pegatron)" <Leslie_Hsia@pegatroncorp.com>
Cc: "knaack.h@gmx.de" <knaack.h@gmx.de>,
"lars@metafoo.de" <lars@metafoo.de>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hermes Hsieh(謝旻劭_Pegatron)" <Hermes_Hsieh@pegatroncorp.com>,
"jesse.sung@canonical.com" <jesse.sung@canonical.com>,
"jic23@kernel.org" <jic23@kernel.org>
Subject: Re: [PATCH] subsystem: Amplifier driver for TAS5805M,Texas instruments
Date: Wed, 29 Apr 2020 13:49:33 +0100 [thread overview]
Message-ID: <20200429124933.GJ4201@sirena.org.uk> (raw)
In-Reply-To: <C84B7899-1FC4-43CC-9FAE-8FECE09E8D4E@pegatroncorp.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Tue, Apr 28, 2020 at 06:27:45PM +0000, Leslie Hsia(夏邦進_Pegatron) wrote:
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
> but he thought that this is an amplifier driver,
> and we should put it into /sound/doc/codecs/,
> so would you please give me an advice about the driver belongs to which subsystem?
> Jonathan, what do you think?
A quick google suggests that this is an audio amplifier so I'd expect it
to be in the audio subsystem. If it were in IIO it wouldn't work with
most userspace audio software...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-29 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <754706C925201D4896E92CCAD6B38E4401F0F733E3@PTW-EX-37.PEGA.CORP.PEGATRON>
2020-04-28 11:30 ` [PATCH] subsystem: Amplifier driver for TAS5805M,Texas instruments Mark Brown
2020-04-28 18:27 ` Leslie Hsia(夏邦進_Pegatron)
2020-04-29 12:49 ` Mark Brown [this message]
[not found] <754706C925201D4896E92CCAD6B38E4401F0F6B825@PTW-EX-38.PEGA.CORP.PEGATRON>
2020-04-26 8:55 ` Jonathan Cameron
[not found] <754706C925201D4896E92CCAD6B38E4401F0F61013@PTW-EX-37.PEGA.CORP.PEGATRON>
2020-04-05 11:08 ` Jonathan Cameron
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=20200429124933.GJ4201@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Hermes_Hsieh@pegatroncorp.com \
--cc=Leslie_Hsia@pegatroncorp.com \
--cc=jesse.sung@canonical.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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