Linux PARISC architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Takashi Iwai <tiwai@suse.de>
Cc: ralf@linux-mips.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-mips@linux-mips.org,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] mips: Add dma_mmap_coherent()
Date: Fri, 22 Aug 2008 11:41:31 +0200	[thread overview]
Message-ID: <20080822094131.GA6717@alpha.franken.de> (raw)
In-Reply-To: <s5hbpzl8tvz.wl%tiwai@suse.de>

On Fri, Aug 22, 2008 at 08:07:44AM +0200, Takashi Iwai wrote:
> I don't think that this must work for *every* platform, too, and it's
> not expected from the driver.  The systems without uncached memory
> access can simply return an error from  dma_mmap_coherent() call, so
> that the driver can disable the mmap.  That'd be enough.

true, I've used snd_pcm_indirect for HAL2 driver, which works even on
SGI IP28 machines.

> Now, how to handle these exceptions: a question comes into my mind
> again -- how does the framebuffer handle these as well?

most framebuffers have a dedicated set of video memory and this memory is
just mmaped uncached either via TLB/MMU (MIPS) or rules inside
the system (PARISC uses IO space memory, which is always uncached). 
The code which does this mmaping is in drivers/video/fbmem.c plus
fb_pgprotect out of an include/asm header file. 

For framebuffers without dedicated video memory the memory is mmaped
write through or uncached. A driver, which uses this, is 
drivers/video/gbefb.c.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2008-08-22  9:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s5hk5eezcfe.wl%tiwai@suse.de>
2008-08-20 16:27 ` [PATCH] mips: Add dma_mmap_coherent() James Bottomley
2008-08-20 16:53   ` Takashi Iwai
2008-08-20 17:58     ` James Bottomley
2008-08-21 10:19       ` Takashi Iwai
2008-08-21 13:55         ` James Bottomley
2008-08-21 16:01           ` Takashi Iwai
2008-08-21 16:03             ` Takashi Iwai
2008-08-21 21:41               ` Thomas Bogendoerfer
2008-08-22  6:07                 ` Takashi Iwai
2008-08-22  9:41                   ` Thomas Bogendoerfer [this message]
2008-08-22 10:23                     ` Takashi Iwai
2008-08-22 14:36                       ` Thomas Bogendoerfer
2008-08-22 14:47                         ` Takashi Iwai
2008-08-21 10:20       ` Ralf Baechle
2008-08-21 10:25         ` Takashi Iwai
2008-08-22 12:04 Joel Soete
2008-08-22 12:17 ` Takashi Iwai
2008-08-23 19:39   ` Joel Soete
2008-08-26 15:25     ` Takashi Iwai
2008-08-26 21:01       ` Grant Grundler
2008-08-27  5:42         ` Takashi Iwai
2008-08-27 10:38           ` Ralf Baechle
2008-08-27 14:06           ` James Bottomley

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=20080822094131.GA6717@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=tiwai@suse.de \
    /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