I really see dts warning after dtbs checking and since global irq is to
On October 14, 2024 2:56:58 PM GMT+05:30, Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote:
On 14/10/2024 11:02, Manivannan Sadhasivam wrote:Hmm. I thought you were referring to the DTS warnings (for old DTS) that come out of these changes. But for kernel ABI, yes there is no breakage.
On Fri, Oct 11, 2024 at 06:06:02PM +0200, Krzysztof Kozlowski wrote:Interface changed but all known users are still working, right? "Break"
On 11/10/2024 17:51, Manivannan Sadhasivam wrote:It increases the 'minItems' to 9 from 8, how come it is not an ABI break?
So there is no ABI break in the first place... Commit is misleading.
On October 11, 2024 9:14:31 PM GMT+05:30, Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote:
On 11/10/2024 17:42, Manivannan Sadhasivam wrote:Here it is:
I tried to look for corresponding driver change, but could not, so maybe
On October 11, 2024 8:03:58 PM GMT+05:30, Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote:
On Fri, Oct 11, 2024 at 03:41:37AM -0700, Qiang Yu wrote:Hardware was described but not completely. 'global' IRQ let's the controller driver to handle PCIe link specific events like Link up, Link down etc... They improve user experience like the driver can use those interrupts to start bus enumeration on its own. So breaking the ABI for good in this case.
Document 'global' SPI interrupt along with the existing MSI interrupts soDescribe the hardware, not what the driver will do.
that QCOM PCIe RC driver can make use of it to get events such as PCIe
link specific events, safety events, etc.
Though adding a new interrupt will break the ABI, it is required toThat's poor reason. Hardware was described and missing optional piece
accurately describe the hardware.
(because according to your description above everything was working
fine) is not needed to break ABI.
Sorry, if your driver changes the ABI for this poor reason.Is the above reasoning sufficient?
there is no ABI break in the first place.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4581403f67929d02c197cb187c4e1e811c9e762a
Above explanation is good, but
still feels like improvement and device could work without global clock.
means something does not work, something is affected.
Sorry for the confusion.
- Mani
I might be missingமணிவண்ணன் சதாசிவம்
here something, of course, but I simply do not see any affected user here.
Best regards,
Krzysztof