From: Alim Akhtar <alim.akhtar@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-samsung-soc@vger.kernel.org
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [v3] arm: dts: exynos: Enable DMA support for UART modules on Exynos5 SoCs
Date: Thu, 22 Dec 2016 17:37:21 +0530 [thread overview]
Message-ID: <585BC1F9.2060603@samsung.com> (raw)
In-Reply-To: <2b04debd-c221-aa26-797f-f9a7557d3043@samsung.com>
On 12/22/2016 04:48 PM, Marek Szyprowski wrote:
> Hi Alim,
>
> On 2016-12-22 12:14, Alim Akhtar wrote:
>> Hello,
>>
>> On 12/19/2016 03:30 PM, Marek Szyprowski wrote:
>>> UART modules can use DMA for offloading data transfers and reducing
>>> interrupts, so enable this feature for Exynos5 boards. Tested on
>>> Google ChromeBook Snow (Exynos5250), Odroid XU (Exynos5410) and Odroid
>>> XU3 (Exynos5422) boards.
>>>
>>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>>> ---
>>> v3:
>>> - added Exynos5410
>>
>> make failed with this patch with below error:
>> DTC arch/arm/boot/dts/exynos5410-odroidxu.dtb
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma0"
>>
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma0"
>>
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma1"
>>
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma1"
>>
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma0"
>>
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma0"
>>
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma1"
>>
>> ERROR (phandle_references): Reference to non-existent node or label
>> "pdma1"
>>
>> ERROR: Input tree has errors, aborting (use -f to force output)
>> make[1]: *** [arch/arm/boot/dts/exynos5410-odroidxu.dtb] Error 2
>> make: *** [dtbs] Error 2
>> -------------------------------------
>>
>> I tried building against linux-next with tag v4.9.
>>
>> 69973b8 Linux 4.9
>> 2e4333c Merge branch 'upstream' of
>> git://git.linux-mips.org/pub/scm/ralf/upstream-linus
>> ba73515 MIPS: Lantiq: Fix mask of GPE frequency
>>
>> Let me know if I am missing other patches.
>
> Please apply it on top of for-next branch from
> git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
>
Thanks Marek for the above link.
Tested this patch on exynos5800 peach-pi board.
Tested-by: Alim Akhtar <alim.akhtar@samsung.com>
> > [...]
>
> Best regards
next prev parent reply other threads:[~2016-12-22 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 12:27 [PATCH] ARM: dts: exynos: Enable DMA support for UART modules on Exynos542x SoCs Marek Szyprowski
2016-12-16 12:39 ` [PATCH v2] arm: dts: exynos: Enable DMA support for UART modules on Exynos5 SoCs Marek Szyprowski
2016-12-16 16:50 ` Krzysztof Kozlowski
2016-12-19 6:37 ` Marek Szyprowski
2016-12-19 9:55 ` Marek Szyprowski
2016-12-19 10:00 ` [PATCH v3] " Marek Szyprowski
2016-12-22 11:14 ` [v3] " Alim Akhtar
2016-12-22 11:18 ` Marek Szyprowski
2016-12-22 12:07 ` Alim Akhtar [this message]
2016-12-29 14:09 ` [PATCH v3] " Krzysztof Kozlowski
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=585BC1F9.2060603@samsung.com \
--to=alim.akhtar@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=s.nawrocki@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