On Wednesday 26 November 2014, suravee.suthikulpa...@amd.com wrote:
> From: Suravee Suthikulpanit <suravee.suthikulpa...@amd.com>
>
> Initial revision of device tree for AMD Seattle Development platform.
>
> Cc: Arnd Bergmann <a...@arndb.de>
> Cc: Marc Zyngier <marc.zyng...@arm.com>
> Cc: Mark Rutland <mark.rutl...@arm.com>
> Cc: Will Deacon <will.dea...@arm.com>
> Cc: Catalin Marinas <catalin.mari...@arm.com>
> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpa...@amd.com>
> Signed-off-by: Thomas Lendacky <thomas.lenda...@amd.com>
> Signed-off-by: Joel Schopp <joel.sch...@amd.com>
> ---
> V5 Changes:
> * Rebase to arm-soc for-next (per Olof)
> * Restructure the DTS/DTSI into board and SoC configurations (per Olof)
> * Add model property at the top level (per Olof)
> * Move pcie0 under smb and change smb's ranges property to empty since pcie
> is not in the same range. (per Olof)
> * Change v2m0's ranges property (per Arnd)
> * Change timer interrupt type to level-trigger (per Marc)
Applied to next/arm64, thanks!
Looking at this one more time, I had another question:
> + smb0: smb {
> + compatible = "simple-bus";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + /* DDR range is 40-bit addressing */
> + dma-ranges = <0x80 0x0 0x80 0x0 0x7f 0xffffffff>;
> +
What is a DDR range?
Also, what is special about the last byte? Did you intentionally
leave it out? I think when we calculate the dma mask, we will
use 0x3fffffffff so we don't step on the last byte, which I assume
is not what you intended.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
