gpiod_set_transitory(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… gpiod_set_transitory(9) β€” the kernel API manual, bestie edition πŸŽ€

Okay so this page is gpiod_set_transitory(9) and it's lowkey one of the most "do I keep my vibe or lose it" functions in the whole GPIO world. Sit down, hydrate, let's go ✨


✨ NAME ✨

gpiod_set_transitory β€” lose or retain GPIO state on suspend or reset πŸ’€

Like fr, that's it. Does your line remember who it was after a nap, or does it wake up with no memory? That's the whole plot.


🌸 SYNOPSIS 🌸

int gpiod_set_transitory (struct gpio_desc *desc , bool transitory );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • desc β€” descriptor of the GPIO for which to configure persistence. This is the little handle for the line you're being nosy about, iykyk πŸ‘€
  • transitory β€” true to lose state on suspend or reset, false for persistence. So true = "no memories, fresh start, main character reboot energy" and false = "I remember everything, hold the line, periodt" 🫢

πŸ”₯ RETURN πŸ”₯

0 on success, otherwise a negative error code. So if it's 0, slay. If it's negative, something went sideways and you should go read the error code, not the vibes 😭


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/gpio/gpiolib.c β€” and honestly the whole friend group is here, brace yourself:

gpio_to_desc(9), gpio_device_get_desc(9), desc_to_gpio(9), gpiod_hwgpio(9), gpiod_to_chip(9), gpiod_to_gpio_device(9), gpio_device_get_base(9), gpio_device_get_label(9), gpio_device_get_chip(9), gpiochip_find_base_unlocked(9), gpiod_is_equal(9), gpiod_get_direction(9), gpiod_is_single_ended(9), gpiochip_query_valid_mask(9), gpiochip_get_data(9), gpiochip_remove(9), gpio_device_find(9), gpio_device_find_by_label(9), gpio_device_find_by_fwnode(9), gpio_device_get(9), gpio_device_put(9), gpio_device_to_device(9), gpiochip_set_hierarchical_irqchip(9), gpiochip_irq_domain_activate(9), gpiochip_irq_domain_deactivate(9), gpiochip_irq_map(9), gpiochip_add_irqchip(9), gpiochip_irqchip_remove(9), gpiochip_irqchip_add_domain(9), gpiochip_generic_request(9), gpiochip_generic_free(9), gpiochip_generic_config(9), gpiochip_add_pingroup_range(9), gpiochip_add_pin_range_with_pins(9), gpiochip_remove_pin_ranges(9), gpiochip_dup_line_label(9), gpiochip_request_own_desc(9), gpiochip_free_own_desc(9), gpio_set_debounce_timeout(9), gpiod_direction_input(9), gpiod_direction_output_raw(9), gpiod_direction_output(9), gpiod_enable_hw_timestamp_ns(9), gpiod_disable_hw_timestamp_ns(9), gpiod_set_config(9), gpiod_set_debounce(9), gpiod_is_active_low(9), gpiod_toggle_active_low(9), gpiod_get_raw_value(9), gpiod_get_value(9), gpiod_get_raw_array_value(9), gpiod_get_array_value(9), gpiod_set_raw_value(9), gpiod_set_value_nocheck(9), gpiod_set_value(9), gpiod_set_raw_array_value(9), gpiod_set_array_value(9), gpiod_cansleep(9), gpiod_set_consumer_name(9), gpiod_is_shared(9), gpiod_to_irq(9), gpiochip_lock_as_irq(9), gpiochip_unlock_as_irq(9), gpiod_get_raw_value_cansleep(9), gpiod_get_value_cansleep(9), gpiod_get_raw_array_value_cansleep(9), gpiod_get_array_value_cansleep(9), gpiod_set_raw_value_cansleep(9), gpiod_set_value_cansleep(9), gpiod_set_raw_array_value_cansleep(9), gpiod_add_lookup_tables(9), gpiod_set_array_value_cansleep(9), gpiod_add_lookup_table(9), gpiod_remove_lookup_table(9), fwnode_gpiod_get_index(9), gpiod_count(9), gpiod_get(9), gpiod_get_optional(9), gpiod_configure_flags(9), gpiod_get_index(9), gpiod_get_index_optional(9), gpiod_hog(9), gpiochip_free_hogs(9), gpiod_get_array(9), gpiod_get_array_optional(9), gpiod_put(9), gpiod_put_array(9)

No cap, that's the full list β€” I didn't skip a single one, because gatekeeping function references is not the vibe πŸ’œ


And that's the page, bestie 🧚 This little number lives over in ./drivers/gpio, dated October 2026, and it's giving "kernel API manual, but make it cute". Go forth and configure your persistence responsibly πŸ’…βœ¨

πŸ“¦ where this page comes from