On 08-05-19, 11:20, Pierre-Louis Bossart wrote:
>
> > > > > + /*
> > > > > + * On some Intel platforms, multiple children of the HDAS
> > > > > + * device can be found, but only one of them is the SoundWire
> > > > > + * controller. The SNDW device is always exposed with
> > >
+ /*
+* On some Intel platforms, multiple children of the HDAS
+* device can be found, but only one of them is the SoundWire
+* controller. The SNDW device is always exposed with
+* Name(_ADR, 0x4000) so filter accordingly
+*/
+ if (adr
On 07-05-19, 09:43, Pierre-Louis Bossart wrote:
>
>
> On 5/7/19 7:26 AM, Vinod Koul wrote:
> > On 03-05-19, 19:29, Pierre-Louis Bossart wrote:
> > > The convention is that the SoundWire controller device is a child of
> > > the HDAudio controller. However there can be more than one child
> > >
On 5/7/19 7:26 AM, Vinod Koul wrote:
On 03-05-19, 19:29, Pierre-Louis Bossart wrote:
The convention is that the SoundWire controller device is a child of
the HDAudio controller. However there can be more than one child
exposed in the DSDT table, and the current namespace walk returns the
On 03-05-19, 19:29, Pierre-Louis Bossart wrote:
> The convention is that the SoundWire controller device is a child of
> the HDAudio controller. However there can be more than one child
> exposed in the DSDT table, and the current namespace walk returns the
> last device.
>
> Add a filter and
The convention is that the SoundWire controller device is a child of
the HDAudio controller. However there can be more than one child
exposed in the DSDT table, and the current namespace walk returns the
last device.
Add a filter and terminate early when a valid _ADR is provided,
otherwise keep
6 matches
Mail list logo
