From: Vivek Pernamitta <quic_vpernami@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.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 17:41:00 +0530 [thread overview]
Message-ID: <43424518-e73c-4136-bb0c-d4cb30062d7b@quicinc.com> (raw)
In-Reply-To: <68f18f09-913d-4ef9-bd13-ad32c1d5f8ca@oss.qualcomm.com>
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>
>> ---
>> drivers/bus/mhi/host/pci_generic.c | 26 +++++++++++++++++++++++++-
>> 1 file changed, 25 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/bus/mhi/host/pci_generic.c b/drivers/bus/mhi/host/pci_generic.c
>> index 4bafe93b56c54e2b091786e7fcd68a36c8247b8e..2d1381006293412fbc593316e5c7f0f59ac74da8 100644
>> --- a/drivers/bus/mhi/host/pci_generic.c
>> +++ b/drivers/bus/mhi/host/pci_generic.c
>> @@ -45,6 +45,8 @@
>> * @sideband_wake: Devices using dedicated sideband GPIO for wakeup instead
>> * of inband wake support (such as sdx24)
>> * @no_m3: M3 not supported
>> + * @reset_on_driver_unbind: Set true for devices support SOC reset and
>> + * perform it when unbinding driver
>> */
>> struct mhi_pci_dev_info {
>> const struct mhi_controller_config *config;
>> @@ -58,6 +60,7 @@ struct mhi_pci_dev_info {
>> unsigned int mru_default;
>> bool sideband_wake;
>> bool no_m3;
>> + bool reset_on_driver_unbind;
>> };
>>
>> #define MHI_CHANNEL_CONFIG_UL(ch_num, ch_name, el_count, ev_ring) \
>> @@ -300,6 +303,7 @@ static const struct mhi_pci_dev_info mhi_qcom_qdu100_info = {
>> .dma_data_width = 32,
>> .sideband_wake = false,
>> .no_m3 = true,
>> + .reset_on_driver_unbind = true,
>
> 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
>
>> };
>>
>> static const struct mhi_channel_config mhi_qcom_sa8775p_channels[] = {
>> @@ -970,6 +974,7 @@ struct mhi_pci_device {
>> struct work_struct recovery_work;
>> struct timer_list health_check_timer;
>> unsigned long status;
>> + bool reset_on_driver_unbind;
>> };
>>
>> static int mhi_pci_read_reg(struct mhi_controller *mhi_cntrl,
>> @@ -1270,6 +1275,11 @@ static int mhi_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
>> mhi_cntrl->mru = info->mru_default;
>> mhi_cntrl->name = info->name;
>>
>> + /* Assign reset functionalities only for PF */
>> + if (pdev->is_physfn)
>> + mhi_pdev->reset_on_driver_unbind = info->reset_on_driver_unbind;
>> +
>> +
>
> Double \n
sure will correct in next patchset
>
>> if (info->edl_trigger)
>> mhi_cntrl->edl_trigger = mhi_pci_generic_edl_trigger;
>>
>> @@ -1336,7 +1346,7 @@ static int mhi_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
>> return err;
>> }
>>
>> -static void mhi_pci_remove(struct pci_dev *pdev)
>> +static void mhi_pci_resource_deinit(struct pci_dev *pdev)
>> {
>> struct mhi_pci_device *mhi_pdev = pci_get_drvdata(pdev);
>> struct mhi_controller *mhi_cntrl = &mhi_pdev->mhi_cntrl;
>> @@ -1352,6 +1362,20 @@ static void mhi_pci_remove(struct pci_dev *pdev)
>> /* balancing probe put_noidle */
>> if (pci_pme_capable(pdev, PCI_D3hot))
>> pm_runtime_get_noresume(&pdev->dev);
>> +}
>> +
>> +static void mhi_pci_remove(struct pci_dev *pdev)
>> +{
>> + struct mhi_pci_device *mhi_pdev = pci_get_drvdata(pdev);
>> + struct mhi_controller *mhi_cntrl = &mhi_pdev->mhi_cntrl;
>> +
>> + /* Disable SRIOV */
>> + pci_disable_sriov(pdev);
>> + mhi_pci_resource_deinit(pdev);
>> + if (mhi_pdev->reset_on_driver_unbind) {
>
> Can we not simply check for pdev->is_physfn?
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.
>
>> + dev_info(&pdev->dev, "perform SOC reset\n");
>
> Is the logspam really necessary?
>
>> + mhi_soc_reset(mhi_cntrl);
>> + }
>
> Konrad
next prev parent reply other threads:[~2025-07-23 12:11 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 [this message]
2025-07-23 12:51 ` Konrad Dybcio
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=43424518-e73c-4136-bb0c-d4cb30062d7b@quicinc.com \
--to=quic_vpernami@quicinc.com \
--cc=Vivek.Pernamitta@quicinc.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
/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®