From: Benjamin Krill <ben@codiert•org>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Becky Bruce <becky.bruce@freescale•com>
Subject: Re: [PATCH v2 2/3] powerpc: setup default archdata for {of_}platform via bus_register_notifier
Date: Fri, 20 Mar 2009 08:37:42 +0100 [thread overview]
Message-ID: <20090320073742.GA11318@codiert.org> (raw)
In-Reply-To: <1237470052-4071-2-git-send-email-galak@kernel.crashing.org>
* Kumar Gala | 2009-03-19 08:40:51 [-0500]:
>Since a number of powerpc chips are SoCs we end up having dma-able
>devices that are registered as platform or of_platform devices. We need
>to hook the archdata to setup proper dma_ops for these devices.
>
>Rather than having to add a bus_notify to each platform we add a default
>one at the highest priority (called first) to set the default dma_ops for
>of_platform and platform devices to dma_direct_ops. This allows platform
>code to override the ops by providing their own notifier call back.
>
>In the future to enable >4G DMA support on ppc32 we can hook swiotlb ops.
>
>Signed-off-by: Kumar Gala <galak@kernel•crashing.org>
Acked-by: Benjamin Krill <ben@codiert•org>
Tested on QPACE node card.
next prev parent reply other threads:[~2009-03-20 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 13:40 [PATCH v2 1/3] powerpc/pci: Default to dma_direct_ops for pci dma_ops Kumar Gala
2009-03-19 13:40 ` [PATCH v2 2/3] powerpc: setup default archdata for {of_}platform via bus_register_notifier Kumar Gala
2009-03-19 13:40 ` [PATCH v2 3/3] powerpc: expect all devices calling dma ops to have archdata set Kumar Gala
2009-03-20 7:38 ` Benjamin Krill
2009-03-20 7:37 ` Benjamin Krill [this message]
2009-03-20 7:37 ` [PATCH v2 1/3] powerpc/pci: Default to dma_direct_ops for pci dma_ops Benjamin Krill
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=20090320073742.GA11318@codiert.org \
--to=ben@codiert$(echo .)org \
--cc=becky.bruce@freescale$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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