From: "Kumar, M Chetan" <m.chetan.kumar@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
netdev@vger.kernel.org, davem@davemloft.net,
johannes@sipsolutions.net, ryazanov.s.a@gmail.com,
loic.poulain@linaro.org, ilpo.jarvinen@linux.intel.com,
ricardo.martinez@linux.intel.com,
chiranjeevi.rapolu@linux.intel.com, haijun.liu@mediatek.com,
edumazet@google.com, pabeni@redhat.com,
chandrashekar.devegowda@intel.com, linuxwwan@intel.com,
linuxwwan_5g@intel.com,
Madhusmita Sahu <madhusmita.sahu@intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 net-next 3/5] net: wwan: t7xx: PCIe reset rescan
Date: Fri, 27 Jan 2023 15:57:16 +0530 [thread overview]
Message-ID: <7f5be4cd-ae84-aa24-cf8f-8261c825fafd@linux.intel.com> (raw)
In-Reply-To: <20230126152552.GA1265322@bhelgaas>
On 1/26/2023 8:55 PM, Bjorn Helgaas wrote:
> On Tue, Jan 24, 2023 at 08:45:43PM -0800, Jakub Kicinski wrote:
>> Hi Bjorn,
>>
>> any objections to the kind of shenanigans this is playing?
>
> Yes, thanks for asking. Drivers definitely should not have to do this
> sort of thing.
>
>> On Sat, 21 Jan 2023 19:03:23 +0530 m.chetan.kumar@linux.intel.com wrote:
>>> From: M Chetan Kumar <m.chetan.kumar@linux.intel.com>
>>>
>>> PCI rescan module implements "rescan work queue".
>>> In firmware flashing or coredump collection procedure
>>> WWAN device is programmed to boot in fastboot mode and
>>> a work item is scheduled for removal & detection.
>>>
>>> The WWAN device is reset using APCI call as part driver
>>> removal flow. Work queue rescans pci bus at fixed interval
>>> for device detection, later when device is detect work queue
>>> exits.
>
> I'm not sure what's going on here. Do we need to reset the device
> when the t7xx driver is loaded so the device will load new firmware
> when it comes out of reset?
Flow is, Reset the device to get into firmware download mode then update
the firmware and later reset it to go back to normal mode.
>
> There are a few drivers that do that, e.g., with pci_reset_function().
>
Thanks for the suggestion.
I will explore a bit and also try to use pci_reset_function() interface
and see if it serves the purpose.
>>> +static struct remove_rescan_context t7xx_rescan_ctx;
>
> Apparently this only supports a single t7xx instance in a system? Not
> good.
>
>>> +void t7xx_pci_dev_rescan(void)
>>> +{
>>> + struct pci_bus *b = NULL;
>>> +
>>> + pci_lock_rescan_remove();
>>> + while ((b = pci_find_next_bus(b)))
>>> + pci_rescan_bus(b);
>
> No, this driver absolutely cannot rescan and assign unassigned
> resources for all the PCI buses in the system.
T7xx device falls off the bus due to ACPI reset.
Would you please suggest how we can bring device back on the bus without
such changes inside driver ? Will pci_reset_function() help in this
regard ?
If there is no alternate option, then we shall try using remove and
rescan from user space and drop this patch.
>
> Bjorn
--
Chetan
next prev parent reply other threads:[~2023-01-27 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1674307425.git.m.chetan.kumar@linux.intel.com>
[not found] ` <b58e4062a78053e558cbd40b9c6bb8fb36d01f64.1674307425.git.m.chetan.kumar@linux.intel.com>
2023-01-25 4:45 ` [PATCH v5 net-next 3/5] net: wwan: t7xx: PCIe reset rescan Jakub Kicinski
2023-01-26 15:25 ` Bjorn Helgaas
2023-01-27 10:27 ` Kumar, M Chetan [this message]
2023-01-27 13:30 ` Bjorn Helgaas
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=7f5be4cd-ae84-aa24-cf8f-8261c825fafd@linux.intel.com \
--to=m.chetan.kumar@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chiranjeevi.rapolu@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haijun.liu@mediatek.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=linuxwwan_5g@intel.com \
--cc=loic.poulain@linaro.org \
--cc=madhusmita.sahu@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ricardo.martinez@linux.intel.com \
--cc=ryazanov.s.a@gmail.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).