linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Paul Burton <paul.burton@mips.com>,
	James Hogan <jhogan@kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 00/3] MIPS: SGI-IP27 rework part2
Date: Thu, 18 Apr 2019 15:57:26 -0500	[thread overview]
Message-ID: <20190418205726.GB126710@google.com> (raw)
In-Reply-To: <20190319154755.31049-1-tbogendoerfer@suse.de>

Hi Thomas,

On Tue, Mar 19, 2019 at 04:47:49PM +0100, Thomas Bogendoerfer wrote:
> SGI IP27 (Origin/Onyx2) and SGI IP30 (Octane) have a similair
> architecture and share some hardware (ioc3/bridge). To share
> the software parts this patchset reworks SGI IP27 interrupt
> and pci bridge code. By using features Linux gained during the
> many years since SGI IP27 code was integrated this even results
> in code reduction and IMHO cleaner code.
> 
> Tests have been done on a two module O200 (4 CPUs) and an
> Origin 2000 (8 CPUs).

Thanks for doing all this work!  It seems like it basically converts
some of the SGI PCI code to the structure typical of current host
controller drivers and moves it to drivers/pci/controller, which all
seems great to me.

The patches were kind of in limbo as far as Patchwork.  Lorenzo
handles the native host controller drivers, so I just delegated them
to him, so now they should be on his radar.

Bjorn

> My next step in integrating SGI IP30 support is splitting ioc3eth
> into a MFD and subdevice drivers, which will be submitted soon.
> 
> Changes in v3:
> 
> - dropped patches accepted by Paul
> - moved IP27 specific __phys_to_dma/__dma_to_phys into its own file
> - moved pcibios_to_node into IP27 specific file
> - moved PCI bus address resources setup out of pci-xtalk code into
>   IP27 specific code
> - dropped bit from hub_irq_data and use hwirq from irq_data
> - introduced intr_addr for setting up bridge interrupts (IP30 preperation)
> 
> Changes in v2:
> 
> - replaced HUB_L/HUB_S by __raw_readq/__raw_writeq
> - removed union bridge_ate
> - replaced remaing fields in slice_data by per_cpu data
> - use generic_handle_irq instead of do_IRQ
> - use hierarchy irq domain for stacking bridge and hub interrupt
> - moved __dma_to_phys/__phy_to_dma to mach-ip27/dma-direct.h
> - use dev_to_node() for pcibus_to_node() implementation
> 
> Thomas Bogendoerfer (3):
>   MIPS: SGI-IP27: move IP27 specific code out of pci-ip27.c into new
>     file
>   MIPS: SGI-IP27: use generic PCI driver
>   MIPS: SGI-IP27: abstract chipset irq from bridge
> 
>  arch/mips/Kconfig                          |   3 +
>  arch/mips/include/asm/mach-ip27/topology.h |  11 +-
>  arch/mips/include/asm/pci/bridge.h         |  14 +-
>  arch/mips/include/asm/sn/irq_alloc.h       |  11 +
>  arch/mips/include/asm/xtalk/xtalk.h        |   9 -
>  arch/mips/pci/Makefile                     |   1 -
>  arch/mips/pci/ops-bridge.c                 | 302 --------------
>  arch/mips/pci/pci-ip27.c                   | 214 ----------
>  arch/mips/sgi-ip27/Makefile                |   4 +-
>  arch/mips/sgi-ip27/ip27-init.c             |   2 +
>  arch/mips/sgi-ip27/ip27-irq.c              | 191 ++++-----
>  arch/mips/sgi-ip27/ip27-pci.c              |  30 ++
>  arch/mips/sgi-ip27/ip27-xtalk.c            |  61 ++-
>  drivers/pci/controller/Kconfig             |   3 +
>  drivers/pci/controller/Makefile            |   1 +
>  drivers/pci/controller/pci-xtalk-bridge.c  | 610 +++++++++++++++++++++++++++++
>  include/linux/platform_data/xtalk-bridge.h |  22 ++
>  17 files changed, 822 insertions(+), 667 deletions(-)
>  create mode 100644 arch/mips/include/asm/sn/irq_alloc.h
>  delete mode 100644 arch/mips/pci/ops-bridge.c
>  delete mode 100644 arch/mips/pci/pci-ip27.c
>  create mode 100644 arch/mips/sgi-ip27/ip27-pci.c
>  create mode 100644 drivers/pci/controller/pci-xtalk-bridge.c
>  create mode 100644 include/linux/platform_data/xtalk-bridge.h
> 
> -- 
> 2.13.7
> 

  parent reply	other threads:[~2019-04-18 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 15:47 [PATCH v3 00/3] MIPS: SGI-IP27 rework part2 Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 1/3] MIPS: SGI-IP27: move IP27 specific code out of pci-ip27.c into new file Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 2/3] MIPS: SGI-IP27: use generic PCI driver Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 3/3] MIPS: SGI-IP27: abstract chipset irq from bridge Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 00/3] MIPS: SGI-IP27 rework part2 Thomas Bogendoerfer
2019-04-18 20:57 ` Bjorn Helgaas [this message]
2019-05-06 10:37   ` Thomas Bogendoerfer
2019-05-07  9:42     ` Lorenzo Pieralisi
2019-05-07 15:31   ` Lorenzo Pieralisi
2019-05-07 15:48     ` Thomas Bogendoerfer
2019-05-07 16:30       ` Lorenzo Pieralisi
2019-05-08  6:24       ` Christoph Hellwig

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=20190418205726.GB126710@google.com \
    --to=helgaas@kernel.org \
    --cc=jhogan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=paul.burton@mips.com \
    --cc=ralf@linux-mips.org \
    --cc=tbogendoerfer@suse.de \
    /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).