Button press detection in Raspberry Pi - Time & Space Complexity

Time Complexity: Button press detection

O(n)

Understanding Time Complexity

When detecting button presses on a Raspberry Pi, the program often waits and checks repeatedly for input.

We want to understand how the time the program takes grows as it keeps checking for button presses.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.IN, pull_up_down=GPIO.PUD_UP)

while True:
    if GPIO.input(18) == GPIO.LOW:
        print("Button pressed!")
        time.sleep(0.2)  # debounce delay

This code continuously checks if a button connected to pin 18 is pressed and prints a message when it is.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The while loop that repeatedly reads the button state.
• How many times: It runs indefinitely, checking the button many times per second.

How Execution Grows With Input

As time passes, the program keeps checking the button state over and over.

Input Size (n)	Approx. Operations
10 (seconds)	Many repeated checks, about 5 per second, so ~50 checks
100 (seconds)	About 500 checks
1000 (seconds)	About 5000 checks

Pattern observation: The number of checks grows directly with time passed, increasing steadily.

Final Time Complexity

Time Complexity: O(n)

This means the program's work grows linearly with how long it runs, checking the button repeatedly.

Common Mistake

[X] Wrong: "The button check only happens once, so time doesn't grow with input."

[OK] Correct: The code uses a loop that runs forever, so it keeps checking many times, making the work grow with time.

Interview Connect

Understanding how repeated checks affect program time helps you explain how real devices respond to inputs over time.

Self-Check

What if we changed the code to use an interrupt instead of a loop? How would the time complexity change?

Practice

1. What does setting a Raspberry Pi GPIO pin as input with a pull-up resistor do when detecting a button press?

easy

A. It keeps the pin at HIGH until the button connects it to LOW when pressed.

B. It keeps the pin at LOW until the button connects it to HIGH when pressed.

C. It disables the pin to save power when the button is not pressed.

D. It makes the pin output a signal when the button is pressed.

Solution

1. Step 1: Understand pull-up resistor behavior

   A pull-up resistor keeps the input pin at a HIGH voltage level by default.

2. Step 2: Detect button press effect on pin

   When the button is pressed, it connects the pin to ground, making the input LOW.

3. Final Answer:

   It keeps the pin at HIGH until the button connects it to LOW when pressed. -> Option A

4. Quick Check:

   Pull-up resistor means default HIGH, press pulls LOW [OK]

Hint: Pull-up means default HIGH, press pulls pin LOW [OK]

Common Mistakes:

• Thinking pull-up sets pin LOW by default
• Confusing input with output pin modes
• Assuming button press sets pin HIGH

2. Which of the following is the correct Python code snippet to set GPIO pin 17 as input with a pull-up resistor on Raspberry Pi?

easy

A. GPIO.setup(17, GPIO.IN, pull_up_down=GPIO.PUD_UP)

B. GPIO.setup(17, GPIO.OUT, pull_up_down=GPIO.PUD_UP)

C. GPIO.setup(17, GPIO.IN)

D. GPIO.setup(17, GPIO.OUT)

Solution

1. Step 1: Identify pin mode for button input

   Button pins must be set as input to read their state.

2. Step 2: Add pull-up resistor parameter

   Use pull_up_down=GPIO.PUD_UP to enable internal pull-up resistor.

3. Final Answer:

   GPIO.setup(17, GPIO.IN, pull_up_down=GPIO.PUD_UP) -> Option A

4. Quick Check:

   Input pin with pull-up resistor = GPIO.IN + PUD_UP [OK]

Hint: Input pin with pull-up uses GPIO.IN and PUD_UP [OK]

Common Mistakes:

• Using GPIO.OUT instead of GPIO.IN
• Omitting pull_up_down parameter
• Setting pull-up resistor on output pin

3. What will be the output of this Python code snippet when the button connected to GPIO 18 is pressed?

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.IN, pull_up_down=GPIO.PUD_UP)

if GPIO.input(18) == GPIO.LOW:
    print("Button Pressed")
else:
    print("Button Not Pressed")

medium

A. No output

B. Button Not Pressed

C. SyntaxError

D. Button Pressed

Solution

1. Step 1: Understand pin setup and input reading

   Pin 18 is set as input with pull-up resistor, so default is HIGH.

2. Step 2: Check condition when button is pressed

   Pressing button pulls pin LOW, so condition GPIO.input(18) == GPIO.LOW is True.

3. Final Answer:

   Button Pressed -> Option D

4. Quick Check:

   Pressed button pulls pin LOW, prints "Button Pressed" [OK]

Hint: Pressed button reads LOW on pull-up input pin [OK]

Common Mistakes:

• Assuming pressed button reads HIGH
• Confusing pull-up with pull-down resistor
• Expecting syntax or runtime errors

4. Identify the error in this Raspberry Pi button press detection code:

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(23, GPIO.IN, pull_up_down=GPIO.PUD_UP)

while True:
    if GPIO.input(23) == GPIO.HIGH:
        print("Button Pressed")
    time.sleep(0.1)

medium

A. time.sleep(0.1) should be before the if statement.

B. The pull_up_down parameter is missing in GPIO.setup.

C. The code should check for GPIO.LOW to detect button press.

D. GPIO.setmode(GPIO.BCM) is incorrect and should be GPIO.BOARD.

Solution

1. Step 1: Review button wiring and logic

   With pull-up resistor, button press pulls pin LOW, not HIGH.

2. Step 2: Check condition in if statement

   Code incorrectly checks for GPIO.HIGH to detect press; should check GPIO.LOW.

3. Final Answer:

   The code should check for GPIO.LOW to detect button press. -> Option C

4. Quick Check:

   Pull-up input reads LOW when pressed, so check GPIO.LOW [OK]

Hint: Pressed button reads LOW on pull-up input pin [OK]

Common Mistakes:

• Checking for HIGH instead of LOW on button press
• Forgetting pull_up_down parameter
• Misplacing sleep causing missed presses

5. You want to detect a button press on GPIO 21 and print "Pressed" only once per press, avoiding multiple prints while the button is held down. Which code snippet correctly implements this behavior?

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(21, GPIO.IN, pull_up_down=GPIO.PUD_UP)

pressed = False
while True:
    if GPIO.input(21) == GPIO.LOW and not pressed:
        print("Pressed")
        pressed = True
    elif GPIO.input(21) == GPIO.HIGH:
        pressed = False
    time.sleep(0.05)

hard

A. This code never prints anything because pressed is always True.

B. This code prints "Pressed" once per press and avoids repeats while held.

C. This code prints "Pressed" continuously while button is held down.

D. This code causes a syntax error due to missing colon.

Solution

1. Step 1: Understand the pressed flag usage

   The variable 'pressed' tracks if the button press was already detected to avoid repeats.

2. Step 2: Analyze the if-elif logic

   When button is LOW and not pressed, it prints once and sets pressed True; when released (HIGH), resets pressed to False.

3. Final Answer:

   This code prints "Pressed" once per press and avoids repeats while held. -> Option B

4. Quick Check:

   pressed flag prevents multiple prints during hold [OK]

Hint: Use a flag variable to print once per press [OK]

Common Mistakes:

• Printing inside loop without flag causes repeated prints
• Not resetting flag on button release
• Syntax errors from missing colons or indentation