[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200428063736.GB990431@kroah.com>
Date: Tue, 28 Apr 2020 08:37:36 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Vinod Koul <vkoul@...nel.org>
Cc: Bard Liao <yung-chuan.liao@...ux.intel.com>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
tiwai@...e.de, broonie@...nel.org, jank@...ence.com,
srinivas.kandagatla@...aro.org, rander.wang@...ux.intel.com,
ranjani.sridharan@...ux.intel.com, hui.wang@...onical.com,
pierre-louis.bossart@...ux.intel.com, sanyog.r.kale@...el.com,
slawomir.blauciak@...el.com, mengdong.lin@...el.com
Subject: Re: [RFC 1/5] soundwire: bus_type: add sdw_master_device support
On Tue, Apr 28, 2020 at 10:01:44AM +0530, Vinod Koul wrote:
> > > That is not true for everyone, it is only true for Intel, pls call that
> > > out as well...
> >
> > Why is it not true for everyone? How else do you get the pm stuff back
> > to your hardware?
>
> The rest of the world would do using the real controller device. For
> example the soundwire controller on Qualcomm devices is enumerated as a
> DT device and is using these...
>
> If Intel had a standalone controller or enumerated as individual
> functions, it would have been a PCI device and would manage as such
If it is not a standalone controller, what exactly is it? I thought it
was an acpi device, am I mistaken?
What is the device that the proper soundwire controller driver binds to
on an Intel-based system?
thanks,
greg k-h
Powered by blists - more mailing lists