From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>, broonie@kernel.org
Cc: alsa-devel@alsa-project.org, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, Mastan.Katragadda@amd.com,
Arungopal.kondaveeti@amd.com, mario.limonciello@amd.com,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Syed Saba Kareem <Syed.SabaKareem@amd.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 1/9] ASoC: amd: ps: create platform devices based on acp config
Date: Thu, 15 Jun 2023 18:23:46 +0200 [thread overview]
Message-ID: <59da8a18-752a-bc8c-c8c5-19d75d8c87fb@linux.intel.com> (raw)
In-Reply-To: <cd465394-5a19-239e-7aad-caa6f19b0918@amd.com>
On 6/13/23 07:42, Mukunda,Vijendar wrote:
> On 12/06/23 23:39, Pierre-Louis Bossart wrote:
>> =
>>> +static int sdw_amd_scan_controller(struct device *dev)
>>> +{
>>> + struct acp63_dev_data *acp_data;
>>> + struct fwnode_handle *link;
>>> + char name[32];
>>> + u32 sdw_manager_bitmap;
>>> + u8 count = 0;
>>> + u32 acp_sdw_power_mode = 0;
>>> + int index;
>>> + int ret;
>>> +
>>> + acp_data = dev_get_drvdata(dev);
>>> + /*
>>> + * Current implementation is based on MIPI DisCo 2.0 spec.
>>> + * Found controller, find links supported.
>>> + */
>>> + ret = fwnode_property_read_u32_array((acp_data->sdw_fw_node), "mipi-sdw-manager-list",
>>> + &sdw_manager_bitmap, 1);
>>> +
>>> + if (ret) {
>>> + dev_err(dev, "Failed to read mipi-sdw-manager-list: %d\n", ret);
>>> + return -EINVAL;
>>> + }
>>> + count = hweight32(sdw_manager_bitmap);
>>> + /* Check count is within bounds */
>>> + if (count > AMD_SDW_MAX_MANAGERS) {
>>> + dev_err(dev, "Manager count %d exceeds max %d\n", count, AMD_SDW_MAX_MANAGERS);
>>> + return -EINVAL;
>>> + }
>> nit-pick: the count is not enough, you should also check that only bits
>> 0 and 1 are set in mipi-sdw-manager-list...
> As per our design for PS platform,
> we will go with two bit map values as 0x03 and 0x01.
> 1. As per ACP PIN CONFIG, we support Single SDW Manager instance
> which refers to SW0 manager instance. For this, we need to use bitmap
> value as 0x01.
> 2. Other bit map value - 0x03 will be used to populate two SoundWire
> manager instances.
> We have extra sub property "amd-sdw-enable" to invoke the init sequence
> for SoundWire manager.
>
> As we are supporting two bit map value combinations here, it's not required
> to check bit set value. count value is enough to know manager instance count.
> It doesn't break anything.
Not a blocker but you underestimate the creativity of UEFI BIOS writers...
next prev parent reply other threads:[~2023-06-15 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230612095903.2113464-1-Vijendar.Mukunda@amd.com>
2023-06-12 9:58 ` [PATCH V4 1/9] ASoC: amd: ps: create platform devices based on acp config Vijendar Mukunda
2023-06-12 18:09 ` Pierre-Louis Bossart
2023-06-13 5:42 ` Mukunda,Vijendar
2023-06-15 16:23 ` Pierre-Louis Bossart [this message]
2023-06-12 9:58 ` [PATCH V4 2/9] ASoC: amd: ps: handle SoundWire interrupts in acp pci driver Vijendar Mukunda
2023-06-12 9:58 ` [PATCH V4 3/9] ASoC: amd: ps: add SoundWire dma driver Vijendar Mukunda
2023-06-12 9:58 ` [PATCH V4 4/9] ASoC: amd: ps: add SoundWire dma driver dma ops Vijendar Mukunda
2023-06-12 18:06 ` Pierre-Louis Bossart
2023-06-13 7:00 ` Mukunda,Vijendar
2023-06-15 15:50 ` Mukunda,Vijendar
2023-06-15 15:56 ` Mark Brown
2023-06-15 16:09 ` Mukunda,Vijendar
2023-06-15 16:12 ` Mukunda,Vijendar
2023-06-15 16:21 ` Pierre-Louis Bossart
2023-06-15 17:13 ` Mukunda,Vijendar
2023-06-12 9:58 ` [PATCH V4 5/9] ASoC: amd: ps: add support for SoundWire DMA interrupts Vijendar Mukunda
2023-06-12 9:59 ` [PATCH V4 6/9] ASoC: amd: ps: add pm ops support for SoundWire dma driver Vijendar Mukunda
2023-06-12 9:59 ` [PATCH V4 7/9] ASoC: amd: ps: enable SoundWire dma driver build Vijendar Mukunda
2023-06-12 9:59 ` [PATCH V4 8/9] ASoC: amd: update comments in Kconfig file Vijendar Mukunda
2023-06-12 9:59 ` [PATCH V4 9/9] ASoC: amd: ps: add acp_reset flag check in acp pci driver pm ops Vijendar Mukunda
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=59da8a18-752a-bc8c-c8c5-19d75d8c87fb@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=Arungopal.kondaveeti@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Mastan.Katragadda@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Syed.SabaKareem@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=vijendar.mukunda@amd.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