All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 2/2] arm-soc: Add support for tango4 platforms
Date: Wed, 18 Nov 2015 11:39:55 -0800	[thread overview]
Message-ID: <7hegfnxfjo.fsf@deeprootsystems.com> (raw)
In-Reply-To: <yw1xegfnfa0g.fsf@unicorn.mansr.com> ("Måns Rullgård"'s message of "Wed, 18 Nov 2015 18:16:47 +0000")

M?ns Rullg?rd <mans@mansr.com> writes:

> Kevin Hilman <khilman@kernel.org> writes:
>
>> Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:
>>
>>> Add support for Sigma Designs ARM-based Tango4 "Secure Media Processor"
>>> platforms (i.e. smp8734, smp8756, smp8758, smp8759) built around the
>>> Cortex-A9 MPCore r3p0 (all dual-core, except the 8756).
>>>
>>> Support for older MIPS-based platforms can be found elsewhere:
>>> https://github.com/mansr/linux-tangox
>>>
>>> Signed-off-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
>>> ---
>>>  arch/arm/Kconfig              |  2 ++
>>>  arch/arm/Makefile             |  1 +
>>>  arch/arm/mach-tangox/Kconfig  | 12 ++++++++++++
>>>  arch/arm/mach-tangox/Makefile |  2 ++
>>>  arch/arm/mach-tangox/setup.c  | 32 ++++++++++++++++++++++++++++++++
>>>  arch/arm/mach-tangox/smc.S    |  9 +++++++++
>>>  arch/arm/mach-tangox/smc.h    |  5 +++++
>>
>> Potential bike-shed fodder, but, a dumb question: is the family name
>> actually "tangox" or is the "x" for the number (tango3, tango4, etc.)
>>
>> Assuming it's the later based on usage throughout the patch, I think
>> it'd be better to just use "tango" throughout instead of tangox.
>
> The x indeed stands for a number.  I have no idea what tango1 was or if
> it ever existed.  Tango2 (SMP863x) and tango3 (SMP86[457]x) were MIPS
> based.  Tango4 is ARM based (mostly, the SMP8910 is MIPS) but otherwise
> very similar to tango3.

Thanks for the clarification.

> Since we don't know what tango5 will look like,
> mach-tango4 might be more suitable here.  If tango5 turns out to be
> sufficiently similar, there's no harm from adding support for that to
> the mach-tango4 code (just look at mach-omap2).

Well, mach-omap2 leads to enough confusion that I don't think we need to
use that as a model. ;)  IMO, mach-tango is a better starting point.

> Most of the drivers support both tango3 and tango4, but apparently some
> changes are planned for tango5.

Thanks for the clarification,

Kevin

  reply	other threads:[~2015-11-18 19:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 15:09 [PATCH v9 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-11-18 15:10 ` [PATCH v9 1/2] arm-soc: Import initial tango4 device tree Marc Gonzalez
2015-11-18 16:05   ` Måns Rullgård
2015-11-18 16:34     ` Marc Gonzalez
2015-11-18 16:38       ` Måns Rullgård
2015-11-18 17:11         ` Olof Johansson
2015-11-18 17:18           ` Måns Rullgård
2015-11-19 13:53             ` Marc Gonzalez
2015-11-19 14:43               ` Måns Rullgård
     [not found]                 ` <564EFB18.3050104@sigmadesigns.com>
2015-11-20 12:08                   ` Tango4 clkgen block Måns Rullgård
2015-11-18 15:12 ` [PATCH v9 2/2] arm-soc: Add support for tango4 platforms Marc Gonzalez
2015-11-18 18:04   ` Kevin Hilman
2015-11-18 18:16     ` Måns Rullgård
2015-11-18 19:39       ` Kevin Hilman [this message]
2015-11-19 17:24     ` Marc Gonzalez
2015-11-19 19:32       ` Kevin Hilman
2015-11-19 19:49   ` Kevin Hilman
2015-11-20 10:04     ` Marc Gonzalez
2015-11-24 18:05       ` Kevin Hilman

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=7hegfnxfjo.fsf@deeprootsystems.com \
    --to=khilman@kernel.org \
    --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.