From: Daniel Axtens <dja@axtens.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@lists.ozlabs.org, wangyijing@huawei.com,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 04/19] powerpc: Create pci_controller_ops.dma_dev_setup and shim
Date: Tue, 07 Apr 2015 10:31:36 +1000 [thread overview]
Message-ID: <1428366696.22268.28.camel@axtens.net> (raw)
In-Reply-To: <5500778.Q4t9Fg7Irn@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
> Please see https://patchwork.ozlabs.org/patch/431333/ for related work.
>
I'm familiar with that patch series - I've been helping Yijing get it up
to speed on PowerPC.
> I think it would be better not to introduce another architecture-specific
> pci host bridge operations structure, but instead consolidate into
> the one that is already there. We are also adding a generic way to set up
> PCI DMA, so it would seems reasonable to hook into that place.
I see what you're getting at, and I agree that we want to move towards
generic operations.
However, I think this should go in as is at this point, for two main
reasons:
1) This is a good midpoint that makes it easier to move to a generic
structure. Our arch specific stuff is quirky and difficult. This patch
series does a lot to reduce the complexity, and would make it very easy
to move these ops into a generic structure at some future point.
2) Trying to go generic at this point risks making the change set so
complex and wide ranging that it will really struggle to get in. For
example, Yijing's patch set, despite not changing any of the quirky
stuff in PowerPC, is already quite long, and will require agreement from
a lot of people before it can go in.
Much as I would like to have everything as generic as possible, if we
were to try to do the whole job in one go, it'd become a big, difficult,
messy patch set, and would be less likely to happen than if we were to
do it in two steps.
Regards,
Daniel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 860 bytes --]
next prev parent reply other threads:[~2015-04-07 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427778057-9505-1-git-send-email-dja@axtens.net>
[not found] ` <1427778057-9505-5-git-send-email-dja@axtens.net>
2015-04-02 14:13 ` [PATCH v2 04/19] powerpc: Create pci_controller_ops.dma_dev_setup and shim Arnd Bergmann
2015-04-07 0:31 ` Daniel Axtens [this message]
2015-04-07 7:44 ` Arnd Bergmann
2015-04-08 3:31 ` Michael Ellerman
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=1428366696.22268.28.camel@axtens.net \
--to=dja@axtens.net \
--cc=arnd@arndb.de \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=wangyijing@huawei.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