[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90417477-c8ba-22e0-de4f-07ef10fc014a@linux.intel.com>
Date: Fri, 28 Feb 2020 09:53:36 -0600
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
tiwai@...e.de, broonie@...nel.org, vkoul@...nel.org,
jank@...ence.com, srinivas.kandagatla@...aro.org,
slawomir.blauciak@...el.com,
Bard liao <yung-chuan.liao@...ux.intel.com>,
Rander Wang <rander.wang@...ux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Hui Wang <hui.wang@...onical.com>,
Sanyog Kale <sanyog.r.kale@...el.com>
Subject: Re: [PATCH 1/8] soundwire: bus_type: add master_device/driver support
> As you are adding new sysfs files here, is there a follow-on patch for
> Documentation/ABI/ updates?
Yes that's the plan. The original patches for sysfs were submitted as an
RFC:
https://mailman.alsa-project.org/pipermail/alsa-devel/2019-May/148699.html
Most of the sysfs entries would mirror the value of _DSD properties, but
that's still very useful to check platform integration issues. Some of
the DSDT blocks are overwritten at run-time depending on BIOS menu
selections, so it's impossible to figure out what the firmware exposes
to the OS just by looking at the DSDT contents extracted with acpica tools.
Powered by blists - more mailing lists