public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <jw@emlix.com>
To: Chris Zankel <chris@zankel.net>
Cc: Oskar Schirmer <os@emlix.com>, Daniel Gloeckner <dg@emlix.com>,
	linux-kernel@vger.kernel.org
Subject: [patch 0/8] xtensa: s6000 & s6105
Date: Tue, 10 Mar 2009 14:11:34 +0100	[thread overview]
Message-ID: <20090310115643.653120649@emlix.com> (raw)

Hi,

here is the core series of our s6000 port.

First comes the nommu patch.  Right now we use CONFIG_MMU for
everything that separates the S6000 from existing ports, memorywise.
This is a lot easier and can still be broken up by newer ports when
they have requirements with finer granularity.  Furthermore, we have
only this one nommu box here, so we couldn't test an MMU architecture
and therefor not say for sure we didn't break anything ;)

Then comes the core variant stuff.  We are the first variant that
needs to ship code files, so there is a prereq patch that allows that.

The inclusion of the GPIO driver is a bit arbitrary.  It was the only
one left after stripping out all real peripheral support because we
initially used GPIO in platform_setup().  I send it now to have an
example on variant-specific code and conceptual improvements can then
be excercised on it.

The platform patch is fairly trivial.  One more requirement is that
our platform can define the kernel text offset.  We can not use a
fixed virtual address (nommu, remember? ;)) but have to provide a
physical one that is within bounds of our actual RAM.

The diffstat looks a bit overwhelming, but note that most of it is the
defconfig, the tensilica core definitions and address definitions
where the core has registers mapped.

        Hannes

 arch/xtensa/Kconfig                                |   15 +
 arch/xtensa/Makefile                               |    5 +
 arch/xtensa/configs/s6105_defconfig                |  530 ++++++++++++++++++++
 arch/xtensa/include/asm/cacheflush.h               |   10 +-
 arch/xtensa/include/asm/dma.h                      |    3 +-
 arch/xtensa/include/asm/gpio.h                     |   56 ++
 arch/xtensa/include/asm/io.h                       |    9 +-
 arch/xtensa/include/asm/irq.h                      |    7 +
 arch/xtensa/include/asm/mmu.h                      |    5 +
 arch/xtensa/include/asm/mmu_context.h              |    5 +
 arch/xtensa/include/asm/nommu.h                    |    3 +
 arch/xtensa/include/asm/nommu_context.h            |   25 +
 arch/xtensa/include/asm/page.h                     |    9 +-
 arch/xtensa/include/asm/pgtable.h                  |   13 +-
 arch/xtensa/include/asm/processor.h                |    6 +
 arch/xtensa/kernel/entry.S                         |    3 +-
 arch/xtensa/kernel/head.S                          |    3 +-
 arch/xtensa/kernel/irq.c                           |   14 +
 arch/xtensa/kernel/setup.c                         |    7 +
 arch/xtensa/kernel/traps.c                         |    2 +
 arch/xtensa/kernel/vectors.S                       |    4 +
 arch/xtensa/kernel/vmlinux.lds.S                   |    3 +
 arch/xtensa/mm/Makefile                            |    3 +-
 arch/xtensa/mm/init.c                              |   62 +---
 arch/xtensa/mm/misc.S                              |    2 +
 arch/xtensa/mm/mmu.c                               |   70 +++
 arch/xtensa/platforms/s6105/Makefile               |    3 +
 arch/xtensa/platforms/s6105/device.c               |   67 +++
 .../xtensa/platforms/s6105/include/platform/gpio.h |   27 +
 .../platforms/s6105/include/platform/hardware.h    |   11 +
 .../platforms/s6105/include/platform/serial.h      |    8 +
 arch/xtensa/platforms/s6105/setup.c                |   61 +++
 arch/xtensa/variants/dc232b/Makefile               |    1 +
 arch/xtensa/variants/fsf/Makefile                  |    1 +
 arch/xtensa/variants/s6000/Makefile                |    3 +
 arch/xtensa/variants/s6000/gpio.c                  |   71 +++
 arch/xtensa/variants/s6000/include/variant/core.h  |  431 ++++++++++++++++
 .../variants/s6000/include/variant/hardware.h      |  259 ++++++++++
 arch/xtensa/variants/s6000/include/variant/irq.h   |    9 +
 .../variants/s6000/include/variant/tie-asm.h       |  304 +++++++++++
 arch/xtensa/variants/s6000/include/variant/tie.h   |  191 +++++++
 arch/xtensa/variants/s6000/irq.c                   |   74 +++
 42 files changed, 2320 insertions(+), 75 deletions(-)


             reply	other threads:[~2009-03-10 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 13:11 Johannes Weiner [this message]
2009-03-10 11:56 ` [patch 1/8] xtensa: nommu support Johannes Weiner
2009-03-10 11:56 ` [patch 2/8] xtensa: variant-specific code Johannes Weiner
2009-03-10 11:56 ` [patch 3/8] xtensa: variant irq set callbacks Johannes Weiner
2009-03-10 11:56 ` [patch 4/8] xtensa: s6000 variant core definitions Johannes Weiner
2009-03-10 11:56 ` [patch 5/8] xtensa: s6000 variant Johannes Weiner
2009-03-10 11:56 ` [patch 6/8] xtensa: s6000 gpio driver Johannes Weiner
2009-03-10 11:56 ` [patch 7/8] xtensa: let platform override KERNELOFFSET Johannes Weiner
2009-03-10 11:56 ` [patch 8/8] xtensa: platform stretch s6105 eval board Johannes Weiner
  -- strict thread matches above, loose matches on Subject: below --
2009-03-10 13:03 [patch 0/8] xtensa: s6000 & s6105 Johannes Weiner
2009-03-12  0:44 ` Piet Delaney

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=20090310115643.653120649@emlix.com \
    --to=jw@emlix.com \
    --cc=chris@zankel.net \
    --cc=dg@emlix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=os@emlix.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