On Fri, Aug 17, 2012 at 23:43:44, Nori, Sekhar wrote:
Hi Gururaja,
On 8/14/2012 6:12 PM, Hebbar, Gururaja wrote:
Davinci McASP header driver are shared by few OMAP platforms (like
TI81xx, AM335x). Splitting asp header into Davinci platform specific
header and Audio specific header helps
On Sat, Aug 18, 2012 at 04:03:58, Mark Brown wrote:
On Tue, Aug 14, 2012 at 06:12:01PM +0530, Hebbar, Gururaja wrote:
Davinci McASP header driver are shared by few OMAP platforms (like
TI81xx, AM335x). Splitting asp header into Davinci platform specific
header and Audio specific header
Hi Gururaja,
On 8/14/2012 6:12 PM, Hebbar, Gururaja wrote:
Davinci McASP header driver are shared by few OMAP platforms (like
TI81xx, AM335x). Splitting asp header into Davinci platform specific
header and Audio specific header helps to share them across platforms.
Audio specific defines
On Tue, Aug 14, 2012 at 06:12:01PM +0530, Hebbar, Gururaja wrote:
Davinci McASP header driver are shared by few OMAP platforms (like
TI81xx, AM335x). Splitting asp header into Davinci platform specific
header and Audio specific header helps to share them across platforms.
This doesn't apply
Davinci McASP header driver are shared by few OMAP platforms (like
TI81xx, AM335x). Splitting asp header into Davinci platform specific
header and Audio specific header helps to share them across platforms.
Audio specific defines is moved to to common
linux/platform_data/davinci_asp.h so that