From: adrian.hunter@intel.com (Adrian Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mach-imx: sdhci-esdhc-imx: initialize DMA mask
Date: Wed, 13 Apr 2016 11:07:16 +0300 [thread overview]
Message-ID: <570DFE34.6040206@intel.com> (raw)
In-Reply-To: <570DA8C3.5030206@nvidia.com>
On 13/04/16 05:02, Alexandre Courbot wrote:
> On 04/13/2016 12:31 AM, Russell King - ARM Linux wrote:
>> On Tue, Apr 12, 2016 at 09:25:04PM +0900, Alexandre Courbot wrote:
>>> Clearly these devices need to be fixed. If we want to give them a grace
>>> period, we could also (temporarily) not propagate the return value of
>>> dma_set_mask_and_coherent() and limit ourselves to emitting a big warning
>>> about the inconsistency of having SDHCI_USE_SDMA/SDHCI_USE_ADMA in the host
>>> flags while not setting a dma mask.
>>
>> Isn't it just easier to fix the root problem? It'll be one patch.
>>
>> There's no need to add churn by changing sdhci stuff, then fixing the
>> imx stuff, and then reverting the sdhci changes.
>
> I think Adrian was concerned that other SDHCI drivers might unknowingly be
> in the same case.
Yes, that is the concern.
> That being said I am also in favor of fixing the root
> issue instead of adding temporary glue that we might eventually forget to
> remove...
Yes, temporary glue just defers the problem.
>
> How long it will take for everyone to fix their drivers is another question,
> since the device doesn't clearly break, but falls back to a degraded mode
> with a warning.
>
It looks like DeviceTree, PCI and ACPI enumerated devices always set up a
dma_mask. I guess that just leaves devices enumerated from hard-coded
platform data. I will have a look for any more of those, and also send an
email for affected people to check their device setup and drivers.
next prev parent reply other threads:[~2016-04-13 8:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 8:20 [PATCH] ARM: mach-imx: sdhci-esdhc-imx: initialize DMA mask Alexander Kurz
2016-04-11 8:35 ` Uwe Kleine-König
2016-04-11 10:10 ` Adrian Hunter
2016-04-11 16:13 ` Alexander Kurz
2016-04-12 6:05 ` Adrian Hunter
2016-04-12 8:40 ` Russell King - ARM Linux
2016-04-12 9:59 ` Adrian Hunter
2016-04-12 12:25 ` Alexandre Courbot
2016-04-12 15:31 ` Russell King - ARM Linux
2016-04-13 2:02 ` Alexandre Courbot
2016-04-13 8:07 ` Adrian Hunter [this message]
2016-04-16 21:48 ` Arnd Bergmann
2016-04-18 6:58 ` Adrian Hunter
2016-04-18 14:33 ` Arnd Bergmann
[not found] ` <57232233.1030702@intel.com>
2016-04-29 8:59 ` Potential issue with SDHCI DMA Adrian Hunter
2016-04-29 8:59 ` Adrian Hunter
2016-04-29 9:19 ` Jisheng Zhang
2016-04-29 9:19 ` Jisheng Zhang
2016-04-12 15:29 ` [PATCH] ARM: mach-imx: sdhci-esdhc-imx: initialize DMA mask Russell King - ARM Linux
2016-04-11 12:46 ` Sergei Shtylyov
2016-04-13 1:38 ` Shawn Guo
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=570DFE34.6040206@intel.com \
--to=adrian.hunter@intel.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 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.