Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Carlo Caione <carlo@caione.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"Jasper St. Pierre" <jstpierre@mecheye.net>,
	Daniel Drake <drake@endlessm.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Rob Clark <robdclark@gmail.com>,
	inki.dae@samsung.com, linux-samsung-soc@vger.kernel.org,
	sw0312.kim@samsung.com, kgene@kernel.org,
	jy0922.shim@samsung.com, Laura Abbott <lauraa@codeaurora.org>
Subject: Re: [PATCH v2 2/2] arm/dma-mapping: Respect NO_KERNEL_MAPPING when we don't have an IOMMU
Date: Fri, 06 Feb 2015 13:16:57 +0100	[thread overview]
Message-ID: <54D4B0B9.6090300@samsung.com> (raw)
In-Reply-To: <CAOQ7t2ZtWA4gnatMgRuk17BPycM8A6MaPD7s6jeprr3VWqOaPA@mail.gmail.com>

Hello,

On 2015-02-05 11:13, Carlo Caione wrote:
> On Wed, Feb 4, 2015 at 11:21 AM, Marek Szyprowski
> <m.szyprowski@samsung.com> wrote:
>> On 2015-02-04 10:23, Carlo Caione wrote:
>>> From: "Jasper St. Pierre" <jstpierre@mecheye.net>
>>>
>>> Even without an iommu, NO_KERNEL_MAPPING is still convenient to save on
>>> kernel address space in places where we don't need a kernel mapping.
>>> Implement support for it in the two places where we're creating an
>>> expensive mapping.
>>>
>>> __alloc_from_pool uses an internal pool from which we already have
>>> virtual addresses, so it's not relevant, and __alloc_simple_buffer uses
>>> alloc_pages, which will always return a lowmem page, which is already
>>> mapped into kernel space, so we can't prevent a mapping for it in that
>>> case.
>>>
>>> Signed-off-by: Jasper St. Pierre <jstpierre@mecheye.net>
>>> Signed-off-by: Carlo Caione <carlo@caione.org>
>>> Reviewed-by: Rob Clark <robdclark@gmail.com>
>>> Reviewed-by: Daniel Drake <dsd@endlessm.com>
>>
>> Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Thanks. Who is supposed to take this patch? Russel?

I think this will be the best way to get it merged. Please upload it to
http://www.arm.linux.org.uk/developer/patches/

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland

      reply	other threads:[~2015-02-06 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  9:23 [PATCH v2 0/2] dma: fix DMA_ATTR_NO_KERNEL_MAPPING for no-IOMMU platforms Carlo Caione
2015-02-04  9:23 ` [PATCH v2 1/2] drm/exynos: fix DMA_ATTR_NO_KERNEL_MAPPING usage Carlo Caione
2015-02-04 10:20   ` Marek Szyprowski
2015-02-04 10:29     ` Russell King - ARM Linux
2015-02-04 10:57   ` Inki Dae
2015-02-04  9:23 ` [PATCH v2 2/2] arm/dma-mapping: Respect NO_KERNEL_MAPPING when we don't have an IOMMU Carlo Caione
2015-02-04 10:21   ` Marek Szyprowski
2015-02-05 10:13     ` Carlo Caione
2015-02-06 12:16       ` Marek Szyprowski [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=54D4B0B9.6090300@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=carlo@caione.org \
    --cc=drake@endlessm.com \
    --cc=inki.dae@samsung.com \
    --cc=jstpierre@mecheye.net \
    --cc=jy0922.shim@samsung.com \
    --cc=kgene@kernel.org \
    --cc=lauraa@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=robdclark@gmail.com \
    --cc=sw0312.kim@samsung.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