From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
bard.liao@intel.com
Subject: Re: [PATCH 1/4] soundwire: add enum to control device number allocation
Date: Thu, 8 Jun 2023 08:25:23 -0500 [thread overview]
Message-ID: <9d2a7b72-b145-ba97-987a-4611fc3db3ad@linux.intel.com> (raw)
In-Reply-To: <ZIF9Hd5Hv/CKQeUW@matsya>
>> +/**
>> + * enum sdw_dev_num_alloc - Device Number allocation strategies
>> + * @SDW_DEV_NUM_ALLOC_DEFAULT: unconstrained first-come-first-serve allocation,
>> + * using range [1, 11]
>> + * @SDW_DEV_NUM_ALLOC_IDA: IDA-based allocation, using range [ida_min, 11]
>> + */
>> +enum sdw_dev_num_alloc {
>> + SDW_DEV_NUM_ALLOC_DEFAULT = 0,
>> + SDW_DEV_NUM_ALLOC_IDA,
>
> Let default be IDA as 0, am sure we are not setting this field in qcom
> or amd controller, lets retain the defaults please
Not following, QCOM or AMD are NOT using the IDA-based version, so the
default is zero.
next prev parent reply other threads:[~2023-06-08 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 3:37 [PATCH 0/4] soundwire: allow for more than 8 devices, keep IDA for wake-capable devices Bard Liao
2023-05-31 3:37 ` [PATCH 1/4] soundwire: add enum to control device number allocation Bard Liao
2023-06-08 7:02 ` Vinod Koul
2023-06-08 13:25 ` Pierre-Louis Bossart [this message]
2023-05-31 3:37 ` [PATCH 2/4] soundwire: introduce SDW_DEV_NUM_ALLOC_IDA_WAKE_ONLY Bard Liao
2023-06-08 7:06 ` Vinod Koul
2023-06-08 15:09 ` Pierre-Louis Bossart
2023-06-21 11:00 ` Vinod Koul
2023-06-21 11:28 ` Pierre-Louis Bossart
2023-05-31 3:37 ` [PATCH 3/4] soundwire: extend parameters of new_peripheral_assigned() callback Bard Liao
2023-06-08 7:07 ` Vinod Koul
2023-06-08 13:24 ` Pierre-Louis Bossart
2023-06-21 10:59 ` Vinod Koul
2023-05-31 3:37 ` [PATCH 4/4] soundwire: intel_auxdevice: use SDW_DEV_NUM_ALLOC_IDA_WAKE_ONLY Bard Liao
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=9d2a7b72-b145-ba97-987a-4611fc3db3ad@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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.