All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Sam Van Den Berge <sam.van.den.berge@telenet.be>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Olof Johansson <olof@lixom.net>,
	Kevin Hilman <khilman@kernel.org>,
	arm@kernel.org, Kukjin Kim <kgene@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9
Date: Mon, 12 Sep 2016 11:38:21 +0200	[thread overview]
Message-ID: <9c7bb7bd-d347-03af-93c7-93534f43932d@samsung.com> (raw)
In-Reply-To: <20160908192434.GA609@sam-MacBookPro>

On 09/08/2016 09:24 PM, Sam Van Den Berge wrote:
> Thanks for the suggestion and apologies for the late response. Last couple of 
> days I've been figuring out what this would involve and I decided that I want
> to give this a try. I found this patch series [1] that I'll use as an example.
> If I understand it correctly, I'll need to create a dma_slave_map and
> pass that via the platform data into the s3c24xx-dma driver. There I'll
> need to fill in the filter_map of the dma slave device. Right?

Yes, AFAIU that's what needs to be done.  Subsequently, related DMA
clients could be updated to not use dma_request_slave_channel_compat().

-- 
Thanks,
Sylwester

WARNING: multiple messages have this Message-ID (diff)
From: s.nawrocki@samsung.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9
Date: Mon, 12 Sep 2016 11:38:21 +0200	[thread overview]
Message-ID: <9c7bb7bd-d347-03af-93c7-93534f43932d@samsung.com> (raw)
In-Reply-To: <20160908192434.GA609@sam-MacBookPro>

On 09/08/2016 09:24 PM, Sam Van Den Berge wrote:
> Thanks for the suggestion and apologies for the late response. Last couple of 
> days I've been figuring out what this would involve and I decided that I want
> to give this a try. I found this patch series [1] that I'll use as an example.
> If I understand it correctly, I'll need to create a dma_slave_map and
> pass that via the platform data into the s3c24xx-dma driver. There I'll
> need to fill in the filter_map of the dma slave device. Right?

Yes, AFAIU that's what needs to be done.  Subsequently, related DMA
clients could be updated to not use dma_request_slave_channel_compat().

-- 
Thanks,
Sylwester

  parent reply	other threads:[~2016-09-12  9:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  9:18 [GIT PULL 0/4] ARM: exynos: Stuff for v4.9 Krzysztof Kozlowski
2016-08-30  9:18 ` Krzysztof Kozlowski
2016-08-30  9:18 ` [GIT PULL 4/4] ARM: defconfig: Exynos " Krzysztof Kozlowski
2016-08-30  9:18   ` Krzysztof Kozlowski
2016-09-02 15:47   ` Arnd Bergmann
2016-09-02 15:47     ` Arnd Bergmann
2016-09-02 16:30     ` Krzysztof Kozlowski
2016-09-02 16:30       ` Krzysztof Kozlowski
2016-08-30  9:18 ` [GIT PULL 2/4] ARM: dts: exynos: DeviceTree " Krzysztof Kozlowski
2016-08-30  9:18   ` Krzysztof Kozlowski
2016-09-13 14:11   ` Arnd Bergmann
2016-09-13 14:11     ` Arnd Bergmann
2016-08-30  9:18 ` [GIT PULL 3/4] arm64: dts: exynos: DeviceTree ARM64 " Krzysztof Kozlowski
2016-08-30  9:18   ` Krzysztof Kozlowski
2016-09-14 14:52   ` Arnd Bergmann
2016-09-14 14:52     ` Arnd Bergmann
2016-08-30  9:18 ` [GIT PULL 1/4] ARM: exynos: SoC/Mach " Krzysztof Kozlowski
2016-08-30  9:18   ` Krzysztof Kozlowski
2016-09-02 16:26   ` Arnd Bergmann
2016-09-02 16:26     ` Arnd Bergmann
2016-09-02 16:32     ` Krzysztof Kozlowski
2016-09-02 16:32       ` Krzysztof Kozlowski
2016-09-05  8:06       ` Sylwester Nawrocki
2016-09-05  8:06         ` Sylwester Nawrocki
2016-09-08 19:24         ` Sam Van Den Berge
2016-09-08 19:24           ` Sam Van Den Berge
     [not found]           ` <CGME20160912093826eucas1p1ac2f1f08b49026f456b52f507d0de9f4@eucas1p1.samsung.com>
2016-09-12  9:38             ` Sylwester Nawrocki [this message]
2016-09-12  9:38               ` Sylwester Nawrocki

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=9c7bb7bd-d347-03af-93c7-93534f43932d@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sam.van.den.berge@telenet.be \
    /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.