From: amery@hanoverdisplays.com (Alejandro Mery)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: davinci: fix eDMA probing for dm365
Date: Mon, 4 Dec 2017 13:33:57 +0000 [thread overview]
Message-ID: <20171204133359.45625-1-amery@hanoverdisplays.com> (raw)
Hi, as an intermediate step toward migrating a davinci dm365 based product from 2.6.32.71
to 4.14(.3+) I'm trying to get the dm365 evm (evaluation board) to work
The very first problem is `edma: probe of edma.0 failed with error -5` caused by dm365 not
been included on some refactoring done by Peter Ujfalusi in 2015 which got solved by the
cherry-picking the following changes into dm365.c
* cef5b0da4019 2015-10-14 Peter Ujfalusi ARM: davinci: Add dma_mask to eDMA devices
* 7ab388e85faa 2015-10-14 Peter Ujfalusi ARM: davinci: Use platform_device_register_full() to create pdev for eDMA
next reply other threads:[~2017-12-04 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 13:33 Alejandro Mery [this message]
2017-12-04 13:33 ` [PATCH 1/2] ARM: davinci: Use platform_device_register_full() to create pdev for dm365's eDMA Alejandro Mery
2017-12-04 13:33 ` [PATCH 2/2] ARM: davinci: Add dma_mask to dm365's eDMA device Alejandro Mery
2017-12-05 12:31 ` [PATCH 0/2] ARM: davinci: fix eDMA probing for dm365 Peter Ujfalusi
2017-12-05 12:34 ` [PATCH v2 0/3] ARM: davinci: fix eDMA for DM365 Alejandro Mery
2017-12-05 12:34 ` [PATCH v2 1/3] ARM: davinci: Use platform_device_register_full() to create pdev for dm365's eDMA Alejandro Mery
2017-12-07 5:57 ` Sekhar Nori
2017-12-05 12:34 ` [PATCH v2 2/3] ARM: davinci: Add dma_mask to dm365's eDMA device Alejandro Mery
2017-12-07 6:03 ` Sekhar Nori
2017-12-05 12:34 ` [PATCH v2 3/3] ARM: davinci: fix mmc entries in DM365's eDMA slaves table Alejandro Mery
2017-12-07 6:10 ` Sekhar Nori
2017-12-07 6:16 ` [PATCH v2 0/3] ARM: davinci: fix eDMA for DM365 Sekhar Nori
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=20171204133359.45625-1-amery@hanoverdisplays.com \
--to=amery@hanoverdisplays.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox