All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristoffer Glembo <kristoffer@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area
Date: Mon, 23 Nov 2009 12:31:32 +0000	[thread overview]
Message-ID: <4B0A80A4.4020704@gaisler.com> (raw)
In-Reply-To: <1257172092-25026-2-git-send-email-kristoffer@gaisler.com>

Hi,


David Miller wrote:
> From: Kristoffer Glembo <kristoffer@gaisler.com>
> Date: Wed, 18 Nov 2009 09:45:41 +0100
> 
>> But I noticed that pci_map_single does not work in later kernels.
>> I guess it stopped working with the patch "sparc: Use
>> asm-generic/pci-dma-compat" since before the that the physical address
>> was obtained through virt_to_phys() and after that it goes through
>> page_to_phys(virt_to_page()) which does not work. Using
>> page_address(virt_to_page()) works but I understand that this does not
>> always evaluate properly.
> 
> "page_address(virt_to_page())" returns a virtual address, whereas
> page_to_phys(virt_to_page()) returns a physical one.
> 

Yeah, I meant virt_to_phys(page_address(virt_to_page())) ..


>> Using page_to_phys(virt_to_page()) results in an address lacking the
>> phys_base offset.
> 
> If it's not adding in phys_base, then it's not returning a legal
> physical address.  Any idea why we don't add phys_base here?  I feel
> like we've discussed this exactly recently, like in the past few
> months.


We did yes. You said that mem_map is not offset at phys_base and then of
course we don't need to add it in page_to_phys. Is mem_map not offset
because typically sp_banks[].base_addr = 0? In our case we pass in one
sp_banks entry which has base_addr = 0x40000000.


Best regards,
Kristoffer




  parent reply	other threads:[~2009-11-23 12:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 14:28 [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2009-11-03 22:45 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific Julian Calaby
2009-11-04 13:39 ` David Miller
2009-11-04 15:50 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2009-11-04 16:36 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller
2009-11-06  9:59 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2009-11-06 10:08 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller
2009-11-16  9:45 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2009-11-16  9:51 ` Kristoffer Glembo
2009-11-16 10:55 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller
2009-11-16 11:03 ` David Miller
2009-11-16 11:06 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2009-11-16 11:21 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller
2009-11-18  8:45 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2009-11-18  9:32 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller
2009-11-23 12:31 ` Kristoffer Glembo [this message]
2009-12-14  4:36 ` David Miller
2009-12-14  7:57 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2010-01-12  7:40 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller
2010-01-12 10:35 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2010-01-12 10:45 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller
2010-01-14 10:43 ` David Miller
2010-01-14 11:05 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific mmu_inval_dma_area Kristoffer Glembo
2010-01-14 11:12 ` [PATCH 2/2] Added leon3_dma_ops and LEON specific David Miller

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=4B0A80A4.4020704@gaisler.com \
    --to=kristoffer@gaisler.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.