lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 14 Feb 2013 12:17:09 +0200
From:	Mika Westerberg <mika.westerberg@...el.com>
To:	Vinod Koul <vinod.koul@...el.com>
Cc:	Viresh Kumar <viresh.kumar@...aro.org>,
	Andy Shevchenko <andriy.shevchenko@...ux.jf.intel.com>,
	linux-kernel@...r.kernel.org,
	spear-devel <spear-devel@...t.st.com>,
	Mika Westerberg <mika.westerberg@...ux.jf.intel.com>
Subject: Re: [PATCH] dw_dmac: adjust slave_id accordingly to request line base

On Thu, Feb 14, 2013 at 03:27:38PM +0530, Vinod Koul wrote:
> Not in the CSRT parser. Once your plaform devices are created, you can add your
> own board handler for each platform device. This board code, using the
> data availble from CSRT can go ahead and do the translation and present the
> actual addresses to dmac.
> Would this be doable with ACPI5.

I'm not sure what you mean by own board handler?

AFAIK, the only platform specific code is under arch/x86/platform/* but we
don't have such thing for Lynxpoint and it should not be needed as we can
enumerate the devices from ACPI.

> Somehow I dont like the idea of DMA resource for request lines. DMA
> resources have specific meaning, perhpas IO resource maybe better idea.

Well, it's a DMA request line so we thought that IORESOURCE_DMA would suit
fine there and the drivers that use these are well aware of their usage.
Not sure about IORESOURCE_IO, it has also specific meaning and I don't
think DMA request lines fit there either :-(
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ