Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1521938
| From | Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [alsa-devel] [RFC 09/14] SoundWire: Add support to handle Slave status change |
| Date | 2016-11-14 18:50 +0100 |
| Message-ID | <sDtyi-1DM-39@gated-at.bofh.it> (permalink) |
| References | <suHqN-5zP-3@gated-at.bofh.it> <suHqN-5zP-17@gated-at.bofh.it> <sDrZw-Nx-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 11/14/16 10:08 AM, Charles Keepax wrote: > There are some issues with this, as the slave driver only probes > when the device actually shows up on the bus. However often > (especially in embedded contexts) some things may need to be > done to enable the slave. For example it may be held in reset or > its power supplies switched off until they are need. As such it > generally helps if the device probe can be called before it shows > up on the bus, the device probe can then do the necessary actions > to enable the device at which point it will show up on the bus. Yes, this point was made at the LPC miniconference. What's not clear to me is if you would want the codec driver to be notified that the bus is operational and let it handle things like sideband power management for that device, or is someone else needs to know.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC 09/14] SoundWire: Add support to handle Slave status change Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2016-11-14 17:10 +0100
Re: [alsa-devel] [RFC 09/14] SoundWire: Add support to handle Slave status change Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> - 2016-11-14 18:50 +0100
Re: [alsa-devel] [RFC 09/14] SoundWire: Add support to handle Slave status change Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2016-11-15 11:00 +0100
csiph-web