From: Michael Ellerman <michael@ellerman.id.au>
To: Becky Bruce <beckyb@kernel.crashing.org>
Cc: fujita.tomonori@lab.ntt.co.jp, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 5/5] powerpc: Add 86xx support for SWIOTLB
Date: Tue, 21 Apr 2009 12:14:04 +1000 [thread overview]
Message-ID: <1240280044.17367.12.camel@localhost> (raw)
In-Reply-To: <36CDD079-FEFD-4928-A997-8DE9C2E1D3D0@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
On Mon, 2009-04-20 at 12:58 -0500, Becky Bruce wrote:
> On Apr 20, 2009, at 12:00 PM, Kumar Gala wrote:
> > On Apr 20, 2009, at 11:26 AM, Becky Bruce wrote:
> >>
> >> config PPC_NEED_DMA_SYNC_OPS
> >> def_bool y
> >> depends on (NOT_COHERENT_CACHE || SWIOTLB)
> >> diff --git a/arch/powerpc/kernel/dma-swiotlb.c b/arch/powerpc/
> >> kernel/dma-swiotlb.c
> >> index 29a68e6..3065d03 100644
> >> --- a/arch/powerpc/kernel/dma-swiotlb.c
> >> +++ b/arch/powerpc/kernel/dma-swiotlb.c
> >> @@ -159,3 +159,5 @@ static int __init setup_bus_notifier(void)
> >>
> >> return 0;
> >> }
> >> +
> >> +machine_arch_initcall(mpc86xx_hpcn, setup_bus_notifier);
> >
> > Hmm, not sure what we chatted about here, but I don't want to have
> > to add every board into this file to register the bus notifiers.
>
> We talked about this, and this was what we decided on - I don't really
> like the idea, either, but there's a lot of precedent for it. I'd
> like to do this differently, but I"m not sure what the solution is -
> we'd need to look into that more (or perhaps someone here will have
> some sage advice).
Give it a better name, export it, and call it from the board setup file?
Actually what depends on the board anyway? It's just the dma window
config in the pci_controller isn't it? So maybe you can always call the
notifier, and if the dma mask isn't 36 bits, and the controller has the
window configured then you use swiotlb?
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-21 2:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 16:26 [PATCH 0/5] SWIOTLB for ppc/mpc86xx Becky Bruce
2009-04-20 16:26 ` [PATCH 0/5] enable swiotlb on ppc/86xx Becky Bruce
2009-04-20 16:26 ` [PATCH 0/5] Allow swiotlb use on ppc/mpc86xx Becky Bruce
2009-04-20 16:26 ` [PATCH 1/5] powerpc: Use sg->dma_length in sg_dma_len() macro on 32-bit Becky Bruce
2009-04-20 16:26 ` [PATCH 2/5] powerpc: Add 36-bit device tree for mpc8641hpcn Becky Bruce
2009-04-20 16:26 ` [PATCH 3/5] powerpc: make dma_window_* in pci_controller struct avail on 32b Becky Bruce
2009-04-20 16:26 ` [PATCH 4/5] powerpc: Add support for swiotlb on 32-bit Becky Bruce
2009-04-20 16:26 ` [PATCH 5/5] powerpc: Add 86xx support for SWIOTLB Becky Bruce
2009-04-20 17:00 ` Kumar Gala
2009-04-20 17:58 ` Becky Bruce
2009-04-21 2:14 ` Michael Ellerman [this message]
2009-04-20 16:57 ` [PATCH 4/5] powerpc: Add support for swiotlb on 32-bit Kumar Gala
2009-04-20 18:03 ` Becky Bruce
2009-04-21 2:39 ` FUJITA Tomonori
2009-04-20 18:31 ` Kumar Gala
2009-04-20 19:06 ` Becky Bruce
2009-04-20 20:04 ` Kumar Gala
2009-04-20 20:16 ` Scott Wood
2009-04-20 16:58 ` [PATCH 3/5] powerpc: make dma_window_* in pci_controller struct avail on 32b Kumar Gala
2009-04-21 1:10 ` [PATCH 2/5] powerpc: Add 36-bit device tree for mpc8641hpcn David Gibson
2009-04-21 15:33 ` Becky Bruce
2009-04-22 1:26 ` David Gibson
2009-04-21 21:11 ` Kumar Gala
2009-04-20 20:06 ` [PATCH 1/5] powerpc: Use sg->dma_length in sg_dma_len() macro on 32-bit Kumar Gala
2009-04-21 2:27 ` FUJITA Tomonori
2009-04-21 15:23 ` Becky Bruce
2009-04-20 16:29 ` [PATCH 0/5] Allow swiotlb use on ppc/mpc86xx Becky Bruce
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=1240280044.17367.12.camel@localhost \
--to=michael@ellerman.id.au \
--cc=beckyb@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linuxppc-dev@ozlabs.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).