From: Wei Xu <xuwei5@hisilicon.com>
To: Guodong Xu <guodong.xu@linaro.org>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <arnd@arndb.de>,
<horms+renesas@verge.net.au>, <treding@nvidia.com>,
<kuninori.morimoto.gx@renesas.com>, <alim.akhtar@samsung.com>,
<srinivas.kandagatla@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Enable configs for 96boards HiKey and general arm64
Date: Mon, 18 Apr 2016 16:17:42 +0100 [thread overview]
Message-ID: <5714FA96.706@hisilicon.com> (raw)
In-Reply-To: <1457654951-29944-1-git-send-email-guodong.xu@linaro.org>
Hi Guodong,
On 11/03/2016 00:09, Guodong Xu wrote:
> This patch enables a number of devices currently supported by the Hi6220
> and 96boards HiKey. These include
> a) Hi655x PMIC and regulator
> b) Hi6220 I2C, USB, MMC, mailbox, and reset
> c) CONFIG_PINCTRL_SINGLE, and CONFIG_LEDS_GPIO
>
> Also added general features required in arm64:
> - SPIDEV
> - USB network adapters
Applied to the hisilicon soc tree.
Thanks!
Best Regards,
Wei
>
> v2:
> - rebase to next-20160310, CONFIG_MMC_BLOCK_MINORS=16 is already in.
> - set CONFIG_I2C_DESIGNWARE_PLATFORM to be build as module
> - Add general features for arm64
>
> Akira Tsukamoto (1):
> ARM64: defconfig: enable several common USB network adapters
>
> Guodong Xu (2):
> arm64: defconfig: Enable devices for Hi6220 and 96boards HiKey
> arm64: defconfig: add CONFIG_SPI_SPIDEV as module
>
> arch/arm64/configs/defconfig | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
prev parent reply other threads:[~2016-04-18 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 0:09 Guodong Xu
2016-03-11 0:09 ` [PATCH v2 1/3] arm64: defconfig: Enable devices for Hi6220 and 96boards HiKey Guodong Xu
2016-03-11 0:09 ` [PATCH v2 2/3] arm64: defconfig: add CONFIG_SPI_SPIDEV as module Guodong Xu
2016-03-11 0:09 ` [PATCH v2 3/3] ARM64: defconfig: enable several common USB network adapters Guodong Xu
2016-04-18 15:17 ` Wei Xu [this message]
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=5714FA96.706@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=guodong.xu@linaro.org \
--cc=horms+renesas@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
/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
Powered by JetHome