From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: add support for SGI Octane (IP30)
Date: Thu, 10 Oct 2019 15:01:36 +0200 [thread overview]
Message-ID: <20191010150136.a30e47b37f8c8aed9e863a5e@suse.de> (raw)
In-Reply-To: <20191009184311.GA20261@infradead.org>
On Wed, 9 Oct 2019 11:43:11 -0700
Christoph Hellwig <hch@infradead.org> wrote:
> > +++ b/arch/mips/sgi-ip30/ip30-pci.c
> > @@ -0,0 +1,19 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * ip30-pci.c: misc PCI related helper code for IP30 architecture
> > + */
> > +
> > +#include <asm/pci/bridge.h>
> > +
> > +dma_addr_t __phys_to_dma(struct device *dev, phys_addr_t paddr)
> > +{
> > + struct pci_dev *pdev = to_pci_dev(dev);
> > + struct bridge_controller *bc = BRIDGE_CONTROLLER(pdev->bus);
> > +
> > + return bc->baddr + paddr;
> > +}
> > +
> > +phys_addr_t __dma_to_phys(struct device *dev, dma_addr_t dma_addr)
> > +{
> > + return dma_addr & ~(0xffUL << 56);
> > +}
>
> This file is duplicated from ip27. I think we should aim to share
> it given the common hardware even if it is mostly trivial.
ok, as far as I can anticipate IP35 verion of this functions will be
the same as well. So I'll move both into pci-xtalk-bridge.c in the
next version of the patch.
Thomas.
--
SUSE Software Solutions Germany GmbH
HRB 247165 (AG München)
Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2019-10-10 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 15:59 [PATCH] MIPS: add support for SGI Octane (IP30) Thomas Bogendoerfer
2019-10-09 18:43 ` Christoph Hellwig
2019-10-10 13:01 ` Thomas Bogendoerfer [this message]
2019-10-10 13:53 ` Christoph Hellwig
2019-10-10 14:48 ` Thomas Bogendoerfer
2019-10-10 14:58 ` Carlo Pisani
2019-10-12 0:33 ` Joshua Kinard
2019-10-14 11:34 ` Thomas Bogendoerfer
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=20191010150136.a30e47b37f8c8aed9e863a5e@suse.de \
--to=tbogendoerfer@suse.de \
--cc=hch@infradead.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.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).