From: "Sit, Michael Wei Hong" <michael.wei.hong.sit@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "pierre-louis.bossart@linux.intel.com"
<pierre-louis.bossart@linux.intel.com>,
"Rojewski, Cezary" <cezary.rojewski@intel.com>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Sia, Jee Heng" <jee.heng.sia@intel.com>,
"tiwai@suse.com" <tiwai@suse.com>,
"liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>
Subject: RE: [PATCH 4/4] dt-bindings: sound: intel,keembay-i2s: Add channel-max property
Date: Mon, 3 Aug 2020 01:59:10 +0000 [thread overview]
Message-ID: <BYAPR11MB3046DD82FAC2B5C672FC85B29D4D0@BYAPR11MB3046.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200730112948.GB5055@sirena.org.uk>
> -----Original Message-----
> From: Mark Brown <broonie@kernel.org>
> Sent: Thursday, 30 July, 2020 7:30 PM
> To: Sit, Michael Wei Hong <michael.wei.hong.sit@intel.com>
> Cc: alsa-devel@alsa-project.org; tiwai@suse.com; pierre-
> louis.bossart@linux.intel.com; Rojewski, Cezary
> <cezary.rojewski@intel.com>; Shevchenko, Andriy
> <andriy.shevchenko@intel.com>; liam.r.girdwood@linux.intel.com; Sia,
> Jee Heng <jee.heng.sia@intel.com>
> Subject: Re: [PATCH 4/4] dt-bindings: sound: intel,keembay-i2s: Add
> channel-max property
>
> On Thu, Jul 30, 2020 at 01:53:19PM +0800, Michael Sit Wei Hong wrote:
>
> > Add a property that configures the interface to the desired max number
> > of capture channels. The platform may have multiple interfaces with
> > different number of capture channels.
>
> Why? None of the other platforms which support many channels need
> this defining and the constraint code and/or machine driver would
> normally be where this would be handled.
The platform uses the audio-graph-card to create the dai-links, and doesn't use a specific machine driver code.
The platform also has 2 different interfaces which have different supported max-channels.
Using this value in the device-tree to determine the maximum supported channel of the interface.
next prev parent reply other threads:[~2020-08-03 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 5:53 [PATCH 0/4] ASoC: Intel: KMB: TDM Enablement patches Michael Sit Wei Hong
2020-07-30 5:53 ` [PATCH 1/4] ASoC: Intel: KMB: Add 8kHz audio support Michael Sit Wei Hong
2020-07-30 5:53 ` [PATCH 2/4] ASoC: Intel: KMB: Rework disable channel function Michael Sit Wei Hong
2020-07-30 5:53 ` [PATCH 3/4] ASoC: Intel: KMB: Enable TDM audio capture Michael Sit Wei Hong
2020-07-30 5:53 ` [PATCH 4/4] dt-bindings: sound: intel, keembay-i2s: Add channel-max property Michael Sit Wei Hong
2020-07-30 11:29 ` [PATCH 4/4] dt-bindings: sound: intel,keembay-i2s: " Mark Brown
2020-08-03 1:59 ` Sit, Michael Wei Hong [this message]
2020-08-03 10:49 ` Mark Brown
2020-08-04 1:57 ` Sit, Michael Wei Hong
2020-08-04 11:50 ` Mark Brown
2020-08-05 6:21 ` Sit, Michael Wei Hong
2020-08-07 14:31 ` Mark Brown
2020-08-10 9:47 ` Sit, Michael Wei Hong
2020-08-10 12:26 ` Mark Brown
2020-07-30 22:28 ` [PATCH 0/4] ASoC: Intel: KMB: TDM Enablement patches Mark Brown
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=BYAPR11MB3046DD82FAC2B5C672FC85B29D4D0@BYAPR11MB3046.namprd11.prod.outlook.com \
--to=michael.wei.hong.sit@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=jee.heng.sia@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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).