Tony,
On 02/28/2014 05:00 PM, Tony Lindgren wrote:
* Suman Anna <s-anna@xxxxxx> [140228 12:46]:
Hi Joerg, Tony,
This is an updated series of the OMAP IOMMU DT adaptation intended
for 3.15 merge window, addressing the comments from the v2 series.
This series is rebased onto 3.14-rc4, and the only change to bindings
is to drop the dma-window property.
The first 7 patches in the series are in drivers/iommu, with the first
3 patches performing some cleanup. The DT bindings and adaptation are
done in patches 4 and 5.
Tony,
Patches 8 through 13 are in arch/arm/mach-omap2 layer, so I am guessing
these would have to go through your tree. Of these, patches 8 and 9 are
cleanup fixes to get OMAP3 IVA MMU working, patches 10 & 11 are fixes
required with DT-boot for OMAP3/4, patches 12 & 13 add the OMAP5 support.
Are patches 8 to 13 OK to apply separately from the iommu patches or
do they need to wait for the iommu patches to get merged first?
Yeah, they don't have any direct dependencies. Patches 8, 9 and 12 are
totally independent. Patches 10, 11 and 13 add the needed platform data
or archdata to get the corresponding DT iommu devices functional by any
users (OMAP3 ISP is the only user in kernel). The only remote dependency
is the compatible string names used in the pdata-quirks.
regards
Suman
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
