On Wed, 2012-04-25 at 18:01 -0500, Ricardo Neri wrote:
If so, we need to make sure it's not currently called in an atomic
context, because it would break if the function will sleep in the
future. And with make sure I just mean that we check the code and keep
it in mind. Or perhaps adding
On Tue, 2012-04-24 at 23:48 -0500, Ricardo Neri wrote:
On 04/23/2012 08:01 AM, Tomi Valkeinen wrote:
On Wed, 2012-03-28 at 16:38 -0600, Ricardo Neri wrote:
Implement the DSS device driver audio support interface in the HDMI
panel driver and generic driver. The implementation relies on the
+alsa-devel list
On 04/25/2012 01:19 AM, Tomi Valkeinen wrote:
On Tue, 2012-04-24 at 23:48 -0500, Ricardo Neri wrote:
On 04/23/2012 08:01 AM, Tomi Valkeinen wrote:
On Wed, 2012-03-28 at 16:38 -0600, Ricardo Neri wrote:
Implement the DSS device driver audio support interface in the HDMI
panel
On 04/23/2012 08:01 AM, Tomi Valkeinen wrote:
On Wed, 2012-03-28 at 16:38 -0600, Ricardo Neri wrote:
Implement the DSS device driver audio support interface in the HDMI
panel driver and generic driver. The implementation relies on the
IP-specific functions that are defined at DSS probe time.
A
On Wed, 2012-03-28 at 16:38 -0600, Ricardo Neri wrote:
Implement the DSS device driver audio support interface in the HDMI
panel driver and generic driver. The implementation relies on the
IP-specific functions that are defined at DSS probe time.
A HW-safe spinlock is used to protect the
Implement the DSS device driver audio support interface in the HDMI
panel driver and generic driver. The implementation relies on the
IP-specific functions that are defined at DSS probe time.
A HW-safe spinlock is used to protect the audio functions. This is because
the audio functions may be
