From: Timur Tabi <timur.tabi@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: CONFIG_ISA_DMA_API without CONFIG_GENERIC_ISA_DMA
Date: Tue, 29 Jun 2010 16:27:57 -0500 [thread overview]
Message-ID: <AANLkTimEt2YMXHtsHoqTCdfLW_vmTFl2PJNPV_eJy02m@mail.gmail.com> (raw)
In-Reply-To: <4B86E05A.1080705@freescale.com>
On Thu, Feb 25, 2010 at 3:40 PM, Scott Wood <scottwood@freescale.com> wrote=
:
> Commit fb4f0e8832e0075849b41b65f6bb9fdfa7593b99 (Enable GENERIC_ISA_DMA i=
f
> FSL_ULI1575 to fix compile issue) tries to deal with this, but it ties it=
to
> CONFIG_FSL_ULI1575, which is not selected in a p4080ds-only config.
>
> It seems that ULI isn't really relevant to the actual problem, which is t=
hat
> we enable ISA DMA API support without selecting an implementation. =A0Whe=
ther
> a certain chip is on the board that has an actual ISA interface is
> irrelevant to the build breakage.
>
> Where did the dependency list for GENERIC_ISA_DMA come from? =A0Are there=
any
> legitimate cases on powerpc where we want to select ISA_DMA_API but not
> GENERIC_ISA_DMA (i.e. we have an alternate implementation)?
I've been bitten by this issue as well on the P1022DS. If I enable
ALSA, then some ISA support also gets compile (by itself, that's
probably a bug), and that code calls claim_dma_lock().
This problem's been around for a long time. I would have encountered
it on the MPC8610 HPCD, but that board has an ULI 1575. The P1022Ds
doesn't.
--=20
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2010-06-29 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 20:40 CONFIG_ISA_DMA_API without CONFIG_GENERIC_ISA_DMA Scott Wood
2010-06-29 21:27 ` Timur Tabi [this message]
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=AANLkTimEt2YMXHtsHoqTCdfLW_vmTFl2PJNPV_eJy02m@mail.gmail.com \
--to=timur.tabi@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).