From: Khalid Masum <khalid.masum.92@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [RFC PATCH] Soundwire: Initialize multi_link with fwnode props
Date: Mon, 15 Aug 2022 10:28:05 +0600 [thread overview]
Message-ID: <54dd86bd-416b-3048-9bd0-368afa3aaf2f@gmail.com> (raw)
In-Reply-To: <CAHp75Ve4UaLsUknGKm14_-f5=qsq1s_Ws+j6h0kAY5_XMkSmQw@mail.gmail.com>
On 8/15/22 00:46, Andy Shevchenko wrote:
> On Sun, Aug 14, 2022 at 11:31 AM Khalid Masum <khalid.masum.92@gmail.com> wrote:
>>
>> According to the TODO, In sw_bus_master_add, bus->multi_link is to be
>> populated with properties from FW node props. Make this happen by
>> creating a new fwnode_handle flag FWNODE_FLAG_MULTI_LINKED and use
>> the flag to store the multi_link value from intel_link_startup. Use
>> this flag to initialize bus->multi_link.
>
> ...
>
>> /*
>> * Initialize multi_link flag
>> - * TODO: populate this flag by reading property from FW node
>> */
>> - bus->multi_link = false;
>> + bus->multi_link = (fwnode->flags & FWNODE_FLAG_MULTI_LINKED)
>> + == FWNODE_FLAG_MULTI_LINKED;
>
> NAK (as far as I understood the context of the comment and the change itself).
>
> These flags are for devlink, we do not mix FW properties with those
> internal flags anyhow. The comment suggests that this should be az
> property. Also commit message doesn't explain the relation to devlink.
>
That is a good information to know. Thanks.
I shall try to find out if I can somehow get multi_link's value from
fwnode in any other way and look into devlink in the process.
If you have any suggestions regarding this TODO, please let me know.
Thanks,
-- Khalid Masum
next prev parent reply other threads:[~2022-08-15 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 8:04 [RFC PATCH] Soundwire: Initialize multi_link with fwnode props Khalid Masum
2022-08-14 9:45 ` Greg KH
2022-08-15 4:08 ` Khalid Masum
2022-08-15 6:37 ` Greg KH
2022-08-15 12:30 ` Khalid Masum
2022-08-14 18:46 ` Andy Shevchenko
2022-08-15 4:28 ` Khalid Masum [this message]
2022-08-15 8:16 ` Pierre-Louis Bossart
2022-08-15 12:10 ` Khalid Masum
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=54dd86bd-416b-3048-9bd0-368afa3aaf2f@gmail.com \
--to=khalid.masum.92@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=djrscally@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox