public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Jaedon Shin <jaedon.shin@gmail.com>,
	Ulf Hansson <ulf.hansson@linaro.org>
Cc: Alan Cooper <alcooperx@gmail.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	bcm-kernel-feedback-list@broadcom.com, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-brcmstb: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA
Date: Thu, 25 Aug 2016 09:41:32 -0700	[thread overview]
Message-ID: <de010fff-1f22-96bb-f41f-99169fb6bb19@gmail.com> (raw)
In-Reply-To: <5A6224B1-2845-4059-A537-EBEA7E6F09E6@gmail.com>

On 08/19/2016 07:05 AM, Jaedon Shin wrote:
> Hi Ulf,
> 
>> On Aug 19, 2016, at 10:44 PM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
>>
>> On 19 August 2016 at 04:25, Jaedon Shin <jaedon.shin@gmail.com> wrote:
>>> Hi Alan,
>>>
>>> On Aug 18, 2016, at 11:27 PM, Alan Cooper <alcooperx@gmail.com> wrote:
>>>>
>>>> It would be better to make this a MIPS only setting because this issue
>>>> only exists for MIPS chips and some newer ARM chips will support 64
>>>> bit DMA.
>>>> Also, since there's been a general effort to reduce the use QUIRKs,
>>>> you could clear the SDHCI_CAN_64BIT in CAPS1 instead of using the
>>>> QUIRK.
>>>>
>>>> @@ -101,6 +101,9 @@ static int sdhci_brcmstb_probe(struct platform_device *pdev)
>>>>       host->caps1 = sdhci_readl(host, SDHCI_CAPABILITIES_1);
>>>>       host->caps1 &= ~(SDHCI_SUPPORT_SDR50 | SDHCI_SUPPORT_SDR104 |
>>>>                       SDHCI_SUPPORT_DDR50);
>>>> +#if defined(CONFIG_MIPS)
>>>> +       host->caps1 &= ~SDHCI_CAN_64BIT;
>>>> +#endif
>>>>       host->quirks |= SDHCI_QUIRK_MISSING_CAPS |
>>>>               SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;
>>>
>>> It's better to me, but we should use host->cap instead of host->cap1. I will update
>>> patch with your comment.
>>
>> Please, then also send this to the public linux-mmc list.
>>
>> Kind regards
>> Uffe
>>
> 
> I'm sorry I could not add the public linux-mmc list this mail thread, but 
> I have already sent the updated patch with linux-mmc.
> 
> https://patchwork.kernel.org/patch/9289189/

Humm, is not this one of these cases where we would expect the
compatible string to dictacte whether enabling 64_BIT_DMA makes sense or
not?

The patch is technically correct though.
-- 
Florian

  reply	other threads:[~2016-08-25 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160808015803.2528-1-jaedon.shin@gmail.com>
     [not found] ` <8f42998e-6d5b-2ac7-3814-f7a4d6e8a6b9@intel.com>
     [not found]   ` <CAOGqxeX8kcD9rX4nd+o=RTggEoPLZfK40GdBWKTT6-BTpxSvbg@mail.gmail.com>
     [not found]     ` <AD331215-7115-426D-A089-263D6A0E54BF@gmail.com>
     [not found]       ` <CAPDyKFqkoF2GU6QGc7GW1S2p8+A=XpU48sREcLiSkadPKHuibw@mail.gmail.com>
2016-08-19 14:05         ` [PATCH] mmc: sdhci-brcmstb: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA Jaedon Shin
2016-08-25 16:41           ` Florian Fainelli [this message]
2016-08-26  6:49             ` Ulf Hansson
2016-08-26 13:29               ` Arnd Bergmann
2016-08-27  4:02             ` Jaedon Shin
2016-08-27 19:56               ` Florian Fainelli
2016-08-28 10:53                 ` Jaedon Shin
2016-08-29  9:44                 ` Arnd Bergmann
2016-08-29 15:40                   ` Alan Cooper
2016-08-30 14:04                     ` Arnd Bergmann

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=de010fff-1f22-96bb-f41f-99169fb6bb19@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=alcooperx@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=jaedon.shin@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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