From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: amd-seattle: Adding device tree for AMD Seattle platform
Date: Sun, 26 Oct 2014 13:43:07 +0100 [thread overview]
Message-ID: <544CEC5B.4020104@suse.de> (raw)
In-Reply-To: <544C2D67.8000405@suse.de>
Am 26.10.2014 um 01:08 schrieb Alexander Graf:
> On 24.10.14 14:20, suravee.suthikulpanit at amd.com wrote:
>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>> index 48b7437..e4c052f 100644
>> --- a/arch/arm64/Kconfig
>> +++ b/arch/arm64/Kconfig
>> @@ -137,6 +137,11 @@ source "kernel/Kconfig.freezer"
>>
>> menu "Platform selection"
>>
>> +config ARCH_SEATTLE
>> + bool "AMD Seattle SoC Family"
>> + help
>> + This enables support for AMD Seattle SOC Family
>> +
>> config ARCH_THUNDER
>> bool "Cavium Inc. Thunder SoC Family"
>> help
>> diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile
>> index f8001a6..6c27047 100644
>> --- a/arch/arm64/boot/dts/Makefile
>> +++ b/arch/arm64/boot/dts/Makefile
>> @@ -1,6 +1,7 @@
>> dtb-$(CONFIG_ARCH_THUNDER) += thunder-88xx.dtb
>> dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb foundation-v8.dtb
>> dtb-$(CONFIG_ARCH_XGENE) += apm-mustang.dtb
>> +dtb-$(CONFIG_ARCH_SEATTLE) += amd-seattle.dtb
>
> This option doesn't exist in upstream kernels, does it? Why not just
> make it dtb-y?
CONFIG_ARCH_SEATTLE is being added one hunk above. :)
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer; HRB 16746 AG N?rnberg
next prev parent reply other threads:[~2014-10-26 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 12:20 [PATCH] arm64: amd-seattle: Adding device tree for AMD Seattle platform suravee.suthikulpanit at amd.com
2014-10-25 23:08 ` Alexander Graf
2014-10-26 12:43 ` Andreas Färber [this message]
2014-10-26 14:08 ` Alexander Graf
2014-10-27 14:29 ` Suravee Suthikulanit
2014-10-27 23:25 ` Alexander Graf
2014-10-28 13:07 ` Suravee Suthikulanit
2014-10-28 14:30 ` Alexander Graf
2014-10-30 13:33 ` Liviu Dudau
2014-10-26 14:09 ` Andreas Färber
2014-10-27 14:30 ` Suravee Suthikulanit
2014-10-27 13:50 ` Mark Rutland
2014-10-27 18:34 ` Suravee Suthikulanit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544CEC5B.4020104@suse.de \
--to=afaerber@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).