public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Laszlo Fiat <laszlo.fiat@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: block: Use the mmc host device index as the mmcblk device index
Date: Mon, 11 Apr 2016 15:46:05 +0300	[thread overview]
Message-ID: <570B9C8D.2000600@intel.com> (raw)
In-Reply-To: <CAPDyKFp8pfZ1iY7HsAZL1f2qgTuLcimDL_f1k59RMcUq5f-iRQ@mail.gmail.com>

On 11/04/16 11:25, Ulf Hansson wrote:
> + Adrian
> 
> On 10 April 2016 at 20:04, Laszlo Fiat <laszlo.fiat@gmail.com> wrote:
>> Hello,
>>
> 
> Hi Laszlo,
> 
> Thanks for your report!
> 
>> I have tested this patch on top of v4.6-rc2 + our usual out-of-tree
>> patches from [1], and there is still no SDIO wifi showing up on
>> baytrail-t. dmesg is available at [2].
>>
>> [1] https://github.com/hadess/rtl8723bs/tree/master/patches
>> [2] https://bugzilla.kernel.org/show_bug.cgi?id=112571#c9
>>
> 
> I understand this issue isn't for an upstream kernel, as you are
> carrying out of tree patches to enable sdhci, sdhci-acpi and sdhci-pci
> to work for your platform.
> 
> As my bandwidth is limited, normally I can't spend time on
> non-upstream kernel reported regressions. Anyway, I decided to help
> study the kernel log in a bit more detail, but unfortunate I am not
> able to figure out what goes wrong.
> 
>>From looking at the errors and a stack trace that gets dumped in the
> kernel log, my guess is that the problem lies within sdhci/sdhci-acpi.
> The errors seems related to your out of tree patches.
> 
> Regarding commit 520bd7a8b415 ("mmc: core: Optimize boot time by
> detecting cards simultaneously"), even if it seems to be triggering
> the regression for you, I find it highly unlikely that this is the
> root cause.
> 
> Someone that knows Baytrail/sdhci-acpi needs to help out with
> debugging. Perhaps Adrian or some other Intel folkz are available!?

Need to know exactly what patches you have.  Is it only the ones from [1] above?

You could do an acpidump and also try the failing case with CONFIG_MMC_DEBUG=y.


  reply	other threads:[~2016-04-11 12:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  7:57 [PATCH] mmc: block: Use the mmc host device index as the mmcblk device index Ulf Hansson
2016-04-07 12:07 ` Jaehoon Chung
2016-04-07 13:07   ` Ulf Hansson
2016-04-14  1:25     ` Jaehoon Chung
2016-04-14  7:26       ` Ulf Hansson
2016-04-10 18:04 ` Laszlo Fiat
2016-04-11  8:25   ` Ulf Hansson
2016-04-11 12:46     ` Adrian Hunter [this message]
2016-04-12 18:15       ` Laszlo Fiat
2016-04-13 11:19         ` Adrian Hunter
2016-04-13 18:19           ` Laszlo Fiat
2016-05-16  8:47             ` Ulf Hansson
2016-05-16  9:12               ` Adrian Hunter
2016-05-16 11:43                 ` Adrian Hunter
     [not found]                   ` <5739F7C1.707@gmail.com>
2016-05-16 16:56                     ` Laszlo Fiat
2016-05-16 20:30                       ` Laszlo Fiat
2016-05-16 21:45                         ` Ulf Hansson
2016-05-17 18:11                           ` Laszlo Fiat
2016-04-12  6:59 ` Ulf Hansson

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=570B9C8D.2000600@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=laszlo.fiat@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