Skip to content

ar71xx: flag FritzBox 4020 buttons as active low #1544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 1, 2018

Conversation

blocktrron
Copy link
Member

This is a pull request for the current Gluon stable branch. It is not against Gluon master as @NeoRaider might want to consider cherry-picking this commit for the openwrt-18.06 branch, making a downstream patch obsolete.


Buttons of AVM FritzBox 4020 are incorrectly flagged as active high.

This was an oversight as RFKill button was working as expected even
with incorrectly flagged GPIO.

Config mode is still accessable but will start on any button press, not
only for the ones >= 10 seconds.

This commit corrects this behavior to the expected one (10 second long
press necessary to enter config mode).

Buttons of AVM FritzBox 4020 are incorrectly flagged as active high.

This was an oversight as RFKill button was working as expected even
with incorrectly flagged GPIO.

Config mode is still accessable but will start on any button press, not
only for the ones >= 10 seconds.

This commit corrects this behavior to the expected one (10 second long
press necessary to enter config mode).
@rotanid rotanid added the 3. topic: hardware Topic: Hardware Support label Oct 1, 2018
@rotanid rotanid merged commit faddb3d into freifunk-gluon:v2018.1.x Oct 1, 2018
@neocturne
Copy link
Member

I cherry-picked the commit to openwrt-18.06, so our next update will contain the fix.

@blocktrron blocktrron deleted the pr-4020-gpio branch January 17, 2019 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. topic: hardware Topic: Hardware Support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants