From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/7] ARM: sunxi: Introduce Allwinner A80 support
Date: Wed, 1 Oct 2014 11:33:14 +0200 [thread overview]
Message-ID: <20141001093314.GI6884@lukather> (raw)
In-Reply-To: <CAGb2v64LwgEZkiuej2KKi+CUU3OkUZaBKJ3ZZn_Y64tDD+LRwg@mail.gmail.com>
On Sat, Sep 27, 2014 at 09:16:02PM +0800, Chen-Yu Tsai wrote:
> On Thu, Sep 25, 2014 at 9:25 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Wed, Sep 24, 2014 at 10:48:55PM +0800, Chen-Yu Tsai wrote:
> >> The Allwinner A80 is a new Cortex octo-core A7/A15 big.LITTLE SoC.
> >> While it's processor cores and interconnecting bus are new, it
> >> re-uses many peripherals found in earlier Allwinner SoCs.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >> ---
> >> arch/arm/mach-sunxi/Kconfig | 5 +++++
> >> arch/arm/mach-sunxi/sunxi.c | 9 +++++++++
> >> 2 files changed, 14 insertions(+)
> >>
> >> diff --git a/arch/arm/mach-sunxi/Kconfig b/arch/arm/mach-sunxi/Kconfig
> >> index 1aaa1e1..72f222b 100644
> >> --- a/arch/arm/mach-sunxi/Kconfig
> >> +++ b/arch/arm/mach-sunxi/Kconfig
> >> @@ -42,4 +42,9 @@ config MACH_SUN8I
> >> select MFD_SUN6I_PRCM
> >> select RESET_CONTROLLER
> >>
> >> +config MACH_SUN9I
> >> + bool "Allwinner A80 (sun9i) SoCs support"
> >
> > With the new naming scheme, I wonder wether it makes sense to have the
> > A80 displayed here and in the machine definition.
>
> I expect anything that falls under sun9i to be compatible, or a trimmed
> down version. But that's just me.
Well, compatible is a rather vague notion. They will be different for
sure. Maybe not that different, but still.
> We know that Allwinner has released the A33, which should be compatible
> with the A23, sun8i.
Except that it would not be straight forward for an A33 user for
example that he needs to enable the A23 support.
> And the A83 has been announced, which looks like a trimmed down
> version of the A80. The next SoC should be arm64, and would not
> matter here.
>
> Kevin, Shuge, could you provide us with the codenames for the A33 and
> A83, and what earlier SoC they are based on?
Even though it would be nice to know, it's not really the issue here.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141001/0767e0c3/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Shuge <shuge-0TFLnhJekD6UEPyfVivIlAC/G2K4zDHf@public.gmane.org>,
Meng Zhang
<kevin-0TFLnhJekD6UEPyfVivIlAC/G2K4zDHf@public.gmane.org>,
ctl <ctl-HcjymKqD97rQT0dZR+AlfA@public.gmane.org>,
Gregory CLEMENT
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH v2 1/7] ARM: sunxi: Introduce Allwinner A80 support
Date: Wed, 1 Oct 2014 11:33:14 +0200 [thread overview]
Message-ID: <20141001093314.GI6884@lukather> (raw)
In-Reply-To: <CAGb2v64LwgEZkiuej2KKi+CUU3OkUZaBKJ3ZZn_Y64tDD+LRwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
On Sat, Sep 27, 2014 at 09:16:02PM +0800, Chen-Yu Tsai wrote:
> On Thu, Sep 25, 2014 at 9:25 PM, Maxime Ripard
> <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> wrote:
> > On Wed, Sep 24, 2014 at 10:48:55PM +0800, Chen-Yu Tsai wrote:
> >> The Allwinner A80 is a new Cortex octo-core A7/A15 big.LITTLE SoC.
> >> While it's processor cores and interconnecting bus are new, it
> >> re-uses many peripherals found in earlier Allwinner SoCs.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
> >> ---
> >> arch/arm/mach-sunxi/Kconfig | 5 +++++
> >> arch/arm/mach-sunxi/sunxi.c | 9 +++++++++
> >> 2 files changed, 14 insertions(+)
> >>
> >> diff --git a/arch/arm/mach-sunxi/Kconfig b/arch/arm/mach-sunxi/Kconfig
> >> index 1aaa1e1..72f222b 100644
> >> --- a/arch/arm/mach-sunxi/Kconfig
> >> +++ b/arch/arm/mach-sunxi/Kconfig
> >> @@ -42,4 +42,9 @@ config MACH_SUN8I
> >> select MFD_SUN6I_PRCM
> >> select RESET_CONTROLLER
> >>
> >> +config MACH_SUN9I
> >> + bool "Allwinner A80 (sun9i) SoCs support"
> >
> > With the new naming scheme, I wonder wether it makes sense to have the
> > A80 displayed here and in the machine definition.
>
> I expect anything that falls under sun9i to be compatible, or a trimmed
> down version. But that's just me.
Well, compatible is a rather vague notion. They will be different for
sure. Maybe not that different, but still.
> We know that Allwinner has released the A33, which should be compatible
> with the A23, sun8i.
Except that it would not be straight forward for an A33 user for
example that he needs to enable the A23 support.
> And the A83 has been announced, which looks like a trimmed down
> version of the A80. The next SoC should be arm64, and would not
> matter here.
>
> Kevin, Shuge, could you provide us with the codenames for the A33 and
> A83, and what earlier SoC they are based on?
Even though it would be nice to know, it's not really the issue here.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Shuge <shuge@allwinnertech.com>,
Meng Zhang <kevin@allwinnertech.com>, ctl <ctl@merrii.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: Re: [PATCH v2 1/7] ARM: sunxi: Introduce Allwinner A80 support
Date: Wed, 1 Oct 2014 11:33:14 +0200 [thread overview]
Message-ID: <20141001093314.GI6884@lukather> (raw)
In-Reply-To: <CAGb2v64LwgEZkiuej2KKi+CUU3OkUZaBKJ3ZZn_Y64tDD+LRwg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]
On Sat, Sep 27, 2014 at 09:16:02PM +0800, Chen-Yu Tsai wrote:
> On Thu, Sep 25, 2014 at 9:25 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Wed, Sep 24, 2014 at 10:48:55PM +0800, Chen-Yu Tsai wrote:
> >> The Allwinner A80 is a new Cortex octo-core A7/A15 big.LITTLE SoC.
> >> While it's processor cores and interconnecting bus are new, it
> >> re-uses many peripherals found in earlier Allwinner SoCs.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >> ---
> >> arch/arm/mach-sunxi/Kconfig | 5 +++++
> >> arch/arm/mach-sunxi/sunxi.c | 9 +++++++++
> >> 2 files changed, 14 insertions(+)
> >>
> >> diff --git a/arch/arm/mach-sunxi/Kconfig b/arch/arm/mach-sunxi/Kconfig
> >> index 1aaa1e1..72f222b 100644
> >> --- a/arch/arm/mach-sunxi/Kconfig
> >> +++ b/arch/arm/mach-sunxi/Kconfig
> >> @@ -42,4 +42,9 @@ config MACH_SUN8I
> >> select MFD_SUN6I_PRCM
> >> select RESET_CONTROLLER
> >>
> >> +config MACH_SUN9I
> >> + bool "Allwinner A80 (sun9i) SoCs support"
> >
> > With the new naming scheme, I wonder wether it makes sense to have the
> > A80 displayed here and in the machine definition.
>
> I expect anything that falls under sun9i to be compatible, or a trimmed
> down version. But that's just me.
Well, compatible is a rather vague notion. They will be different for
sure. Maybe not that different, but still.
> We know that Allwinner has released the A33, which should be compatible
> with the A23, sun8i.
Except that it would not be straight forward for an A33 user for
example that he needs to enable the A23 support.
> And the A83 has been announced, which looks like a trimmed down
> version of the A80. The next SoC should be arm64, and would not
> matter here.
>
> Kevin, Shuge, could you provide us with the codenames for the A33 and
> A83, and what earlier SoC they are based on?
Even though it would be nice to know, it's not really the issue here.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-01 9:33 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 14:48 [PATCH v2 0/7] ARM: sunxi: Add basic support for Allwinner A80 SoC Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-24 14:48 ` [PATCH v2 1/7] ARM: sunxi: Introduce Allwinner A80 support Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-25 13:25 ` Maxime Ripard
2014-09-25 13:25 ` Maxime Ripard
2014-09-25 13:25 ` Maxime Ripard
2014-09-27 13:16 ` Chen-Yu Tsai
2014-09-27 13:16 ` Chen-Yu Tsai
2014-09-27 13:16 ` Chen-Yu Tsai
2014-10-01 9:33 ` Maxime Ripard [this message]
2014-10-01 9:33 ` Maxime Ripard
2014-10-01 9:33 ` Maxime Ripard
2014-10-03 6:23 ` Chen-Yu Tsai
2014-10-03 6:23 ` Chen-Yu Tsai
2014-10-07 20:11 ` Maxime Ripard
2014-10-07 20:11 ` Maxime Ripard
2014-10-07 20:11 ` Maxime Ripard
2014-09-24 14:48 ` [PATCH v2 2/7] ARM: sunxi: Add debug uart used by sun9i (Allwinner A80) Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-25 13:27 ` Maxime Ripard
2014-09-25 13:27 ` Maxime Ripard
2014-09-25 13:27 ` Maxime Ripard
2014-09-24 14:48 ` [PATCH v2 3/7] ARM: dts: sunxi: Add Allwinner A80 dtsi Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-25 13:33 ` Maxime Ripard
2014-09-25 13:33 ` Maxime Ripard
2014-09-24 14:48 ` [PATCH v2 4/7] ARM: dts: sun9i: Add A80 Optimus Board support Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-25 13:34 ` Maxime Ripard
2014-09-25 13:34 ` Maxime Ripard
2014-09-27 13:10 ` Chen-Yu Tsai
2014-09-27 13:10 ` Chen-Yu Tsai
2014-09-27 13:10 ` Chen-Yu Tsai
2014-09-29 9:53 ` Maxime Ripard
2014-09-29 9:53 ` Maxime Ripard
2014-09-29 10:04 ` Chen-Yu Tsai
2014-09-29 10:04 ` Chen-Yu Tsai
2014-09-29 10:04 ` Chen-Yu Tsai
2014-10-01 10:03 ` Maxime Ripard
2014-10-01 10:03 ` Maxime Ripard
2014-10-01 10:03 ` Maxime Ripard
2014-10-06 7:02 ` Chen-Yu Tsai
2014-10-06 7:02 ` Chen-Yu Tsai
2014-10-06 7:02 ` Chen-Yu Tsai
2014-10-07 20:12 ` Maxime Ripard
2014-10-07 20:12 ` Maxime Ripard
2014-10-07 20:12 ` Maxime Ripard
2014-09-24 14:48 ` [PATCH v2 5/7] devicetree: bindings: Add vendor prefix for Merrii Technology Co., Ltd Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-24 14:48 ` Chen-Yu Tsai
2014-09-25 13:34 ` Maxime Ripard
2014-09-25 13:34 ` Maxime Ripard
2014-09-24 14:49 ` [PATCH v2 6/7] devicetree: bindings: Document supported Allwinner sunxi SoCs Chen-Yu Tsai
2014-09-24 14:49 ` Chen-Yu Tsai
2014-09-24 14:49 ` Chen-Yu Tsai
2014-09-25 13:36 ` Maxime Ripard
2014-09-25 13:36 ` Maxime Ripard
2014-09-25 13:36 ` Maxime Ripard
2014-09-27 13:08 ` Chen-Yu Tsai
2014-09-27 13:08 ` Chen-Yu Tsai
2014-09-27 13:08 ` Chen-Yu Tsai
2014-09-29 9:52 ` Maxime Ripard
2014-09-29 9:52 ` Maxime Ripard
2014-09-24 14:49 ` [PATCH v2 7/7] Documentation: sunxi: Add A80 datasheet link Chen-Yu Tsai
2014-09-24 14:49 ` Chen-Yu Tsai
2014-09-24 14:49 ` Chen-Yu Tsai
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=20141001093314.GI6884@lukather \
--to=maxime.ripard@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.