Bug 1597577

Summary:	Raspberry PI GPIO edge not triggering irq
Product:	[Fedora] Fedora	Reporter:	Bernhard Schuster <redhat.bugzilla>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	28	CC:	airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone:	---	Flags:	jforbes: needinfo?
Target Release:	---
Hardware:	armv7hl
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 15:14:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bernhard Schuster 2018-07-03 09:14:00 UTC

Description of problem:
GPIO Interrupts are not working as they do on raspbian (use any GPIO toolkit for pri you can find, it won't work on fedora, but works fine on raspbian)


How reproducible:
try to use the interrupt feature of GPIOs with any GPIO library.

Steps to Reproduce:
1. Write a demo app
2. Trigger it by shorting two pins
3. Create a edge
4. wait for the trigger ( which never happens)

Actual results:
No edge detected/irq never called

Expected results:
Edge detection


Additional info:
Works in raspbian, for testing used: https://crates.io/crates/rppal

Comment 1 Justin M. Forbes 2018-07-23 15:10:02 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.17.7-200.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Justin M. Forbes 2018-08-29 15:14:52 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.