From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Vivek Pernamitta <quic_vpernami@quicinc.com>,
Vivek.Pernamitta@quicinc.com,
Manivannan Sadhasivam <mani@kernel.org>
Cc: mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] bus: mhi: host: pci_generic: Remove MHI driver and ensure graceful device recovery
Date: Wed, 23 Jul 2025 14:51:06 +0200 [thread overview]
Message-ID: <ba37a9c9-3fd3-46fc-8d72-e57be45fc562@oss.qualcomm.com> (raw)
In-Reply-To: <43424518-e73c-4136-bb0c-d4cb30062d7b@quicinc.com>
On 7/23/25 2:11 PM, Vivek Pernamitta wrote:
>
>
> On 7/10/2025 6:12 PM, Konrad Dybcio wrote:
>> On 7/10/25 10:58 AM, Vivek.Pernamitta@quicinc.com wrote:
>>> From: Vivek Pernamitta <quic_vpernami@quicinc.com>
>>>
>>> When the MHI driver is removed from the host side, it is crucial to ensure
>>> graceful recovery of the device. To achieve this, the host driver will
>>> perform the following steps:
>>>
>>> 1. Disable SRIOV for any SRIOV-enabled devices on the Physical Function.
>>> 2. Perform a SOC_RESET on Physical Function (PF).
>>>
>>> Disabling SRIOV ensures that all virtual functions are properly shut down,
>>> preventing any potential issues during the reset process. Performing
>>> SOC_RESET on each physical function guarantees that the device is fully
>>> reset and ready for subsequent operations.
>>>
>>> Signed-off-by: Vivek Pernamitta <quic_vpernami@quicinc.com>
>>> ---
[...]
>> It seems rather unlikely that out off all MHI devices, only QDU100
>> needs this quirk when working under SR-IOV
> The reset_on_driver_unbind flag has been explicitly added for the QDU100
> device. While other devices might enter RAMDUMP mode and wait when a SOC
> reset is issued, the QDU100 device will pass through without entering
> RAMDUMP mode
Rather inconveniently, this is not something that you mentioned in
the commit message.. Especially in the middle of a series that focuses
on enabling SR-IOV which suggests it's strictly related to virtualization,
making it difficult or impossible to understand the problem that this
patch is actually solving.
Please rewrite the commit message.
Konrad
next prev parent reply other threads:[~2025-07-23 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 8:58 [PATCH v2 0/5] bus: mhi: host: Enable SRIOV support in MHI driver Vivek.Pernamitta
2025-07-10 8:58 ` [PATCH v2 1/5] bus: mhi: host: Add support for separate controller configurations for VF and PF Vivek.Pernamitta
2025-07-10 8:58 ` [PATCH v2 2/5] bus: mhi: host: pci_generic: Read SUBSYSTEM_VENDOR_ID for VF's to check status Vivek.Pernamitta
2025-08-06 16:59 ` Manivannan Sadhasivam
2025-08-07 7:09 ` Krishna Chaitanya Chundru
2025-08-07 8:13 ` Manivannan Sadhasivam
2025-08-07 8:15 ` Krishna Chaitanya Chundru
2025-08-07 8:26 ` Manivannan Sadhasivam
2025-07-10 8:58 ` [PATCH v2 3/5] bus: mhi: host: pci_generic: Remove MHI driver and ensure graceful device recovery Vivek.Pernamitta
2025-07-10 12:42 ` Konrad Dybcio
2025-07-23 12:11 ` Vivek Pernamitta
2025-07-23 12:51 ` Konrad Dybcio [this message]
2025-08-06 17:28 ` Manivannan Sadhasivam
2025-07-10 8:58 ` [PATCH v2 4/5] bus: mhi: host: pci_generic: Add SRIOV support for PCIe device Vivek.Pernamitta
2025-07-10 12:43 ` Konrad Dybcio
2025-07-10 8:58 ` [PATCH v2 5/5] bus: host: mhi: Need to honor sys_err at power_up state Vivek.Pernamitta
2025-07-10 12:46 ` Konrad Dybcio
2025-08-06 17:32 ` Manivannan Sadhasivam
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=ba37a9c9-3fd3-46fc-8d72-e57be45fc562@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Vivek.Pernamitta@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_vpernami@quicinc.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
all inboxes | Powered by JetHome®