linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Chen-Yu Tsai <wens@csie.org>, Stephen Boyd <sboyd@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-sunxi@googlegroups.com
Subject: Re: [PATCH 1/5] arm: sunxi: add support for V3s SoC
Date: Tue, 10 Jan 2017 19:09:26 +0100	[thread overview]
Message-ID: <20170110180926.ilqtygttpfgbetvu@lukather> (raw)
In-Reply-To: <20170103151629.19447-2-icenowy@aosc.xyz>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

On Tue, Jan 03, 2017 at 11:16:25PM +0800, Icenowy Zheng wrote:
> Allwinner V3s is a low-end single-core Cortex-A7 SoC, with 64MB
> integrated DRAM, and several peripherals.
> 
> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
> ---
>  Documentation/arm/sunxi/README | 4 ++++
>  arch/arm/mach-sunxi/sunxi.c    | 1 +
>  2 files changed, 5 insertions(+)
> 
> diff --git a/Documentation/arm/sunxi/README b/Documentation/arm/sunxi/README
> index cd0243302bc1..91ec8f2055be 100644
> --- a/Documentation/arm/sunxi/README
> +++ b/Documentation/arm/sunxi/README
> @@ -67,6 +67,10 @@ SunXi family
>          + Datasheet
>            http://dl.linux-sunxi.org/H3/Allwinner_H3_Datasheet_V1.0.pdf
>  
> +      - Allwinner V3s (sun8i)
> +        + Datasheet
> +          https://www.goprawn.com/forum/allwinner-cams/783-allwinner-v3s-soc-datasheet
> +

Please don't put random links in there, but at least something that we
know will be there in a couple of weeks/monthes/years

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

       reply	other threads:[~2017-01-10 18:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170103151629.19447-1-icenowy@aosc.xyz>
     [not found] ` <20170103151629.19447-2-icenowy@aosc.xyz>
2017-01-10 18:09   ` Maxime Ripard [this message]
     [not found]     ` <2706391484163632@web1g.yandex.ru>
2017-01-12 17:17       ` [PATCH 1/5] arm: sunxi: add support for V3s SoC Maxime Ripard
     [not found] ` <20170103151629.19447-3-icenowy@aosc.xyz>
2017-01-10 18:10   ` [PATCH 2/5] clk: sunxi-ng: add support for V3s CCU Maxime Ripard
     [not found]     ` <2705031484163593@web1g.yandex.ru>
     [not found]       ` <2714901484163893@web1g.yandex.ru>
2017-01-12 17:19         ` Maxime Ripard
     [not found] ` <20170103151629.19447-5-icenowy@aosc.xyz>
2017-01-10 18:21   ` [PATCH 4/5] ARM: dts: sunxi: add dtsi file for V3s SoC Maxime Ripard
     [not found] ` <20170103151629.19447-4-icenowy@aosc.xyz>
2017-01-10 18:18   ` [PATCH 3/5] pinctrl: sunxi: add driver " Maxime Ripard
2017-01-11 15:24   ` Linus Walleij

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=20170110180926.ilqtygttpfgbetvu@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=devicetree@vger.kernel.org \
    --cc=icenowy@aosc.xyz \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=sboyd@codeaurora.org \
    --cc=wens@csie.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).