From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
andreas.noever@gmail.com, michael.jamet@intel.com,
yehezkel.bernat@intel.com
Subject: Re: [PATCH] thunderbolt: icm: Remove Apple check for Alpine Ridge
Date: Mon, 7 Aug 2017 16:00:06 +0800 [thread overview]
Message-ID: <CAAd53p6uJ_LRtLycay=bQG1TsnWeDcKx_b6ZK650-m91vMHWAg@mail.gmail.com> (raw)
In-Reply-To: <20170807075150.GN2369@lahna.fi.intel.com>
On Mon, Aug 7, 2017 at 3:51 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> At this point we should find out that the ICM is already running and the
> function never calls pci2cio_write().
I guess you mean this code section:
/* Check if the ICM firmware is already running */
val = ioread32(nhi->iobase + REG_FW_STS);
if (val & REG_FW_STS_ICM_EN)
return 0;
>
> The reason why it is not happening needs to be resolved.
>
>> pcie2cio_write()
>> pci_write_config_dword(pdev, vnd_cap + PCIE2CIO_WRDATA, data);
>>
>> > Is there an actual issue you are trying to solve here?
>>
>> Yes, please take a look at [1].
>>
>> Although both the patch I sent and the diff above still failed to
>> probe the device
>> But there are no more NULL pointer dereference.
>>
>> [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/comments/11
>
> I would like to understand what the actual problem is here because in
> normal cases we should not end up starting ICM firmware in the first
> place.
>
> So no, let's not fix it like this until we know the root cause.
>
> I'll be participating the discussion on the above bug in hopes we could
> figure out the root cause.
Thanks for the information and explanation.
next prev parent reply other threads:[~2017-08-07 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170807044912.18146-1-kai.heng.feng@canonical.com>
2017-08-07 6:50 ` [PATCH] thunderbolt: icm: Remove Apple check for Alpine Ridge Kai-Heng Feng
2017-08-07 7:02 ` Mika Westerberg
2017-08-07 7:20 ` Kai-Heng Feng
2017-08-07 7:51 ` Mika Westerberg
2017-08-07 8:00 ` Kai-Heng Feng [this message]
2017-08-07 8:06 ` Mika Westerberg
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='CAAd53p6uJ_LRtLycay=bQG1TsnWeDcKx_b6ZK650-m91vMHWAg@mail.gmail.com' \
--to=kai.heng.feng@canonical.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=yehezkel.bernat@intel.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;
as well as URLs for NNTP newsgroup(s).