linux-kernel - Re: [PATCH v3 0/4] arm64, thunder: Enable Cavium Thunder SoC Family

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:	Tue, 23 Sep 2014 12:41:22 +0200
From:	Robert Richter <rric@...nel.org>
To:	Will Deacon <will.deacon@....com>,
	Mark Rutland <mark.rutland@....com>,
	Rob Herring <robh+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>
Cc:	Radha Mohan Chintakuntla <rchintakuntla@...ium.com>,
	Olof Johansson <olof@...om.net>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Robert Richter <rrichter@...ium.com>
Subject: Re: [PATCH v3 0/4] arm64, thunder: Enable Cavium Thunder SoC Family

On 12.09.14 19:49:43, Robert Richter wrote:
> From: Robert Richter <rrichter@...ium.com>
> 
> This initial patches enable Cavium Thunder SoC Family. The patches add
> devicetree and Kconfig support and then add Thunder to the defconfig.
> 
> The Thunder system needs more enablement patches for subsystems and
> devices, this includes network, ahci, gicv3/gicv3-its, pci, smmu, kvm.
> We will send separate patch sets for these. All of them base on this
> initial patches.
> 
> I sent a separate patch set independently that introduces support for
> dts vendor subdirs. After both patch sets have been applied I will
> send a patch in addition that moves the dts file into a subdirectory.
> 
> I sent another separate patch that sets NR_CPUS to 64 per default.
> 
> The first patch introduces dts files without having a Kconfig option
> for the soc (ARCH_THUNDER). However, this is introduced in patch 3 and
> added to defconfig in patch 4 as this is my preferred solution. If
> there is still resistance having an ARCH_THUNDER option, just drop
> them.
> 
> Patches are available here:
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/rric/linux.git thunder/init

Will,

it would be good if these patches could be applied.

Thanks,

-Robert

> 
> v3 changes:
> * removed setting NR_CPUS for Thunder, I sent a separate patch that
>   increases this to 64 cpus per default
> * reordered patches, dts files changes are know first using dtb-y
>   instead of ARCH_THUNDER option
> * moved soc nodes to thunder-88xx.dtsi
> 
> v2 changes:
> * rebased to 3.17
> * placed commas between 32-bit portions of 64 bit addresses
> * removed #address-cells and size-cells in gic node
> * get rid of the clocks node
> * changed to gpl/x11 dual license
> * removed memreserve
> * moved gic to bus node
> 
> Radha Mohan Chintakuntla (3):
>   arm64, thunder: Add initial dts for Cavium Thunder SoC
>   arm64, thunder: Document devicetree bindings for Cavium Thunder SoC
>   arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family
> 
> Robert Richter (1):
>   arm64, defconfig: Enable Cavium Thunder SoC in defconfig
> 
>  .../devicetree/bindings/arm/cavium-thunder.txt     |  10 +
>  Documentation/devicetree/bindings/arm/cpus.txt     |   1 +
>  arch/arm64/Kconfig                                 |   5 +
>  arch/arm64/boot/dts/Makefile                       |   1 +
>  arch/arm64/boot/dts/thunder-88xx.dts               |  67 ++++
>  arch/arm64/boot/dts/thunder-88xx.dtsi              | 401 +++++++++++++++++++++
>  arch/arm64/configs/defconfig                       |   1 +
>  7 files changed, 486 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/arm/cavium-thunder.txt
>  create mode 100644 arch/arm64/boot/dts/thunder-88xx.dts
>  create mode 100644 arch/arm64/boot/dts/thunder-88xx.dtsi
> 
> -- 
> 2.1.0
> 
--
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/