Re: [PATCH 6.6 1/2] Revert "spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"

[Jinfeng Wang <jinfeng.wang.cn@windriver.com>]

On 9/3/25 16:22, Greg KH wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, Sep 03, 2025 at 03:58:14PM +0800, jinfeng.wang.cn@windriver.com wrote:
>> From: Jinfeng Wang <jinfeng.wang.cn@windriver.com>
>>
>> This reverts commit 1af6d1696ca40b2d22889b4b8bbea616f94aaa84.
> What is the upstream commit id for this?

I'm sorry, I didn't describe this clearly. Let me try to summarize and 
clarify the issue:

### Background on the Commits and Dependencies:
- **Upstream Commit Chain**:
   - Original feature: 0578a6dbfe75 ("spi: spi-cadence-quadspi: add 
runtime pm support")   – Introduces runtime power management support.
   - Fix 1: 86401132d7bb ("spi: spi-cadence-quadspi: Fix missing unwind 
goto warnings")    – Fix unwind issue introduced by the previous commit.
   - Fix 2: b07f349d1864 ("spi: spi-cadence-quadspi: Fix pm runtime 
unbalance")            – Fix unbalance issue introduced by the previous 
two commits.
   - Fix 3: 04a8ff1bc351 ("spi: cadence-quadspi: fix cleanup of rx_chan 
on failure paths") – Fix cleanup issue introduced by previous commit.

- **Backports to 6.6.y Stable Branch**:
   - Only the later fixes (Fix 2 and Fix 3) were backported:
     - b07f349d1864 as cdfb20e4b34a ("spi: spi-cadence-quadspi: Fix pm 
runtime unbalance") – Note: This backport differs from the upstream commit.
     - 04a8ff1bc351 as 1af6d1696ca4 ("spi: cadence-quadspi: fix cleanup 
of rx_chan on failure paths").
   - The foundational commits (0578a6dbfe75 and 86401132d7bb) were 
**not** backported to 6.6.y.

### The Problem:
- Without reverting these backports, we see the error: "cadence-qspi 
ff8d2000.spi: Unbalanced pm_runtime_enable!" on 6.6.y.
- This error occurs because:
   - The backported fixes (especially cdfb20e4b34a) assume the presence 
of the earlier commits (0578a6dbfe75 and 86401132d7bb), which isn't in 
6.6.y.

### Proposed Solutions and Testing:
- **Option 1: Revert the Backports** (this patch):
   - Revert cdfb20e4b34a and 1af6d1696ca4.
   - Result: The "unbalanced pm_runtime_enable" error disappears, and 
the system works without issues.
- **Option 2: Backport the Foundational Commits**:
   - First revert cdfb20e4b34a and 1af6d1696ca4. Then backport the 
original feature and Fix 1, Fix 2, Fix 3, and 959043afe53a to avoid boot 
hang.(I just identified the cause of boot hang. The commit 959043afe53a 
is key to preventing the hang)
   - Result:  The "unbalanced pm_runtime_enable" error does not appear.

The newer kernels have all these commits including 959043afe53a, so 
there is no boot hang issue in newer kernels.
I think Option 1 is simple and easy to fix "Unbalanced 
pm_runtime_enable!" error. My patches are Option 1. If you have any 
objections, please let me know.

Thanks.

Jinfeng

>
>> There is cadence-qspi ff8d2000.spi: Unbalanced pm_runtime_enable! error
>> without this revert.
>>
>> After reverting commit cdfb20e4b34a ("spi: spi-cadence-quadspi: Fix pm runtime unbalance")
>> and commit 1af6d1696ca4 ("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"),
>> Unbalanced pm_runtime_enable! error does not appear.
>>
>> These two commits are backported from upstream commit b07f349d1864 ("spi: spi-cadence-quadspi: Fix pm runtime unbalance")
>> and commit 04a8ff1bc351 ("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths").
>>
>> The commit 04a8ff1bc351 ("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths")
>> fix commit b07f349d1864 ("spi: spi-cadence-quadspi: Fix pm runtime unbalance").
>>
>> The commit b07f349d1864 ("spi: spi-cadence-quadspi: Fix pm runtime unbalance") fix
>> commit 86401132d7bb ("spi: spi-cadence-quadspi: Fix missing unwind goto warnings").
>>
>> The commit 86401132d7bb ("spi: spi-cadence-quadspi: Fix missing unwind goto warnings") fix
>> commit 0578a6dbfe75 ("spi: spi-cadence-quadspi: add runtime pm support").
> I am sorry, but I can not parse any of this.
>
>> 6.6.y only backport commit b07f349d1864 ("spi: spi-cadence-quadspi: Fix pm runtime unbalance")
>> and commit 04a8ff1bc351 ("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"),
>> but does not backport commit 0578a6dbfe75 ("spi: spi-cadence-quadspi: add runtime pm support")
>> and commit 86401132d7bb ("spi: spi-cadence-quadspi: Fix missing unwind goto warnings").
>> And the backport of commit b07f349d1864 ("spi: spi-cadence-quadspi: Fix pm runtime unbalance")
>> differs with the original patch. So there is Unbalanced pm_runtime_enable error.
>>
>> If revert the backport for commit b07f349d1864 ("spi: spi-cadence-quadspi: Fix pm runtime unbalance")
>> and commit 04a8ff1bc351 ("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"), there is no error.
>> If backport commit 0578a6dbfe75 ("spi: spi-cadence-quadspi: add runtime pm support") and
>> commit 86401132d7bb ("spi: spi-cadence-quadspi: Fix missing unwind goto warnings"), there
>> is hang during booting. I didn't find the cause of the hang.
> Is this hang also in newer kernels?  Why is this only an issue in older
> kernels?
>
> thanks,
>
> greg k-h