[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 Zhang Rui (rui.zh...@intel.com) changed: What|Removed |Added Status|NEEDINFO|CLOSED Resolution|--- |INSUFFICIENT_DATA --- Comment #16 from Zhang Rui (rui.zh...@intel.com) --- Bug closed as there is no response from the bug reporter. Please feel free to reopen it if you can provide the info required. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #15 from Zhang Rui (rui.zh...@intel.com) --- so let's focus on the second issue only. Do you have a pattern that can fix it? if no, can you please check if the problem is gone with DSDT fixed as I suggested in comment #2? the bogus piece of ASL code can be removed as I mentioned in comment #7. Only if we have a pattern that works, we can think about how to fix it in Linux kernel. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #14 from Zoltan Boszormenyi (zbos...@pr.hu) --- (In reply to Zhang Rui from comment #13) > Sorry, I'm a little confused. > > (In reply to Zoltan Boszormenyi from comment #10) > > (In reply to Zhang Rui from comment #8) > > > Hi, Zoltan, any updates? > > > > Regarding the tablet in question, it turned out that the touchscreen is > > actually I2C and is correctly handled by the i2c-hid-acpi driver. We didn't > > have this driver enabled before. > > Does the problem go away after you enabling this driver? > If yes, is there any other problem that blocks us from closing this bug > report? > If no, do you mean it is still the IRQ problem still exists after enabling > the i2c-hid-acpi driver? And can you try custom DSDT as I suggested? There were two orthogonal issues here. 1. the touchscreen didn't work, believed to be UART based but actually I2C and fixed by i2c-hid-acpi 2. the ttyS0 UART IRQ is wrong if the IRQ subsection for the specific device contains an empty IRQ () or IRQNoFlags () subsection. This ticket is about the latter. Possibly the Linux kernel's default IRQ parameters are wrong and the IOAPIC is programmed wrongly. My patch that I attached here tries to collect the default legacy IRQ parameters from the PCI Interrupt Link device, but the kernel fails to use it. Without irq_set_irq_type() in the patch, the IRQ stays edge triggered with extra messages in dmesg telling the IRQ is overridden to edge triggered. With irq_set_irq_type() in the patch, the IRQ becomes fasteoi instead of level triggered, resulting in the IRQ being disabled very quickly. Possibly a small change may make the patch work but I don't know enough to make it work. It is also possible that by the time this code is reached, it's too late for IRQ setup in the APIC/IOAPIC. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #13 from Zhang Rui (rui.zh...@intel.com) --- Sorry, I'm a little confused. (In reply to Zoltan Boszormenyi from comment #10) > (In reply to Zhang Rui from comment #8) > > Hi, Zoltan, any updates? > > Regarding the tablet in question, it turned out that the touchscreen is > actually I2C and is correctly handled by the i2c-hid-acpi driver. We didn't > have this driver enabled before. Does the problem go away after you enabling this driver? If yes, is there any other problem that blocks us from closing this bug report? If no, do you mean it is still the IRQ problem still exists after enabling the i2c-hid-acpi driver? And can you try custom DSDT as I suggested? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #12 from Zoltan Boszormenyi (zbos...@pr.hu) --- (In reply to Zoltan Boszormenyi from comment #10) > ... that also didn't help. Obviously, the touchscreen now works, but I have been testing by opening the ttyS0 device and observing /proc/interrupts for IRQ 4. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #10 from Zoltan Boszormenyi (zbos...@pr.hu) --- (In reply to Zhang Rui from comment #8) > Hi, Zoltan, any updates? Regarding the tablet in question, it turned out that the touchscreen is actually I2C and is correctly handled by the i2c-hid-acpi driver. We didn't have this driver enabled before. FWIW, I also found https://bugzilla.kernel.org/show_bug.cgi?id=213031 and have been testing previous incarnations of the patch. It didn't help. I even had something like the attached patch which have built on the test patch from this other ticket and tried discovering the IRQ parameteres from the ACPI PCI Interrupt Link Device found in DSDT. And that also didn't help. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #11 from Zoltan Boszormenyi (zbos...@pr.hu) --- Created attachment 297387 --> https://bugzilla.kernel.org/attachment.cgi?id=297387=edit ACPI PCI Interrupt Device IRQ discovery -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #9 from Zhang Rui (rui.zh...@intel.com) --- and also, please confirm if this patch helps or not. https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge=0ec4e55e9f571f08970ed115ec0addc691eda613 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #8 from Zhang Rui (rui.zh...@intel.com) --- Hi, Zoltan, any updates? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #7 from Zhang Rui (rui.zh...@intel.com) --- just remove the PSOC method that contains the bogus line and rebuild your DSDT. I tried this and it works. I think it is okay to delete this PSOC because it is not used anywhere. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #6 from Zoltan Boszormenyi (zbos...@pr.hu) --- (In reply to Zhang Rui from comment #1) > Please attach the full acpidump output and dmesg output after boot. I provided the necessary information. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 Zoltan Boszormenyi (zbos...@pr.hu) changed: What|Removed |Added CC||raf...@kernel.org -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #5 from Zoltan Boszormenyi (zbos...@pr.hu) --- I was unable to recompile the DSDT because of this error printed by iasl -tc: ... DSDT.dsl 23617: Local1 = WIDR /* \_SB_.PCI0.I2C7.WIDR */ Error6058 - Invalid type ^ ([Device] found, Store operator requires [Integer|String|Buffer|Package|DdbHandle|Reference]) ... Compilation failed. 1 Errors, 100 Warnings, 186 Remarks No AML files were generated due to compiler error(s) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #4 from Zoltan Boszormenyi (zbos...@pr.hu) --- Created attachment 297203 --> https://bugzilla.kernel.org/attachment.cgi?id=297203=edit acpidump output -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 --- Comment #3 from Zoltan Boszormenyi (zbos...@pr.hu) --- Created attachment 297201 --> https://bugzilla.kernel.org/attachment.cgi?id=297201=edit dmesg -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 Zhang Rui (rui.zh...@intel.com) changed: What|Removed |Added Status|ASSIGNED|NEEDINFO -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353
--- Comment #2 from Zhang Rui (rui.zh...@intel.com) ---
and what if you change the BUF0 ASL code to
IRQ (Level, ActiveLow, Shared, )
{4}
and build the kernel with the customized DSDT?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
[Bug 213353] IRQs for onboard UARTs are not level-triggered with IRQNoFlags even if the parent section has the defaults in PRS
https://bugzilla.kernel.org/show_bug.cgi?id=213353 Zhang Rui (rui.zh...@intel.com) changed: What|Removed |Added Status|NEW |ASSIGNED CC||rui.zh...@intel.com --- Comment #1 from Zhang Rui (rui.zh...@intel.com) --- Please attach the full acpidump output and dmesg output after boot. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
