[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73907607-0763-576d-b24e-4773dfb15f0b@linux.intel.com>
Date: Tue, 21 Jan 2020 11:31:32 -0600
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Vinod Koul <vkoul@...nel.org>
Cc: alsa-devel@...a-project.org, tiwai@...e.de,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
broonie@...nel.org, srinivas.kandagatla@...aro.org,
jank@...ence.com, slawomir.blauciak@...el.com,
Sanyog Kale <sanyog.r.kale@...el.com>,
Bard liao <yung-chuan.liao@...ux.intel.com>,
Rander Wang <rander.wang@...ux.intel.com>
Subject: Re: [alsa-devel] [PATCH v5 09/17] soundwire: intel: remove platform
devices and use 'Master Devices' instead
> A rename away from probe will certainly be very helpful as
> you would also agree that terms 'probe' and 'remove' have a very
> special meaning in kernel, so let us avoid these
ok, so would the following be ok with you?
/**
* struct sdw_md_driver - SoundWire 'Master Device' driver
*
* @init: allocations and initializations (hardware may not be enabled yet)
* @startup: initialization handled after the hardware is enabled, all
* clock/power dependencies are available
* @shutdown: cleanups before hardware is disabled (optional)
* @exit: free all remaining resources
* @autonomous_clock_stop_enable: enable/disable driver control while
* in clock-stop mode, typically in always-on/D0ix modes. When the driver
* yields control, another entity in the system (typically firmware
* running on an always-on microprocessor) is responsible to tracking
* Slave-initiated wakes
*/
struct sdw_md_driver {
int (*init)(struct sdw_master_device *md, void *link_ctx);
int (*startup)(struct sdw_master_device *md);
int (*shutdown)(struct sdw_master_device *md);
int (*exit)(struct sdw_master_device *md);
int (*autonomous_clock_stop_enable)(struct sdw_master_device *md,
bool state);
};
Powered by blists - more mailing lists