drivers/leds/leds-expresswire.c
Source file repositories/reference/linux-study-clean/drivers/leds/leds-expresswire.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/leds/leds-expresswire.c- Extension
.c- Size
- 2198 bytes
- Lines
- 83
- Domain
- Driver Families
- Bucket
- drivers/leds
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bits.hlinux/delay.hlinux/export.hlinux/gpio/consumer.hlinux/irqflags.hlinux/types.hlinux/leds-expresswire.h
Detected Declarations
function expresswire_power_offfunction expresswire_enablefunction expresswire_startfunction expresswire_endfunction expresswire_set_bitfunction expresswire_write_u8
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* Shared library for Kinetic's ExpressWire protocol.
* This protocol works by pulsing the ExpressWire IC's control GPIO.
* ktd2692 and ktd2801 are known to use this protocol.
*/
#include <linux/bits.h>
#include <linux/delay.h>
#include <linux/export.h>
#include <linux/gpio/consumer.h>
#include <linux/irqflags.h>
#include <linux/types.h>
#include <linux/leds-expresswire.h>
void expresswire_power_off(struct expresswire_common_props *props)
{
gpiod_set_value_cansleep(props->ctrl_gpio, 0);
fsleep(props->timing.poweroff_us);
}
EXPORT_SYMBOL_NS_GPL(expresswire_power_off, "EXPRESSWIRE");
void expresswire_enable(struct expresswire_common_props *props)
{
unsigned long flags;
local_irq_save(flags);
gpiod_set_value(props->ctrl_gpio, 1);
udelay(props->timing.detect_delay_us);
gpiod_set_value(props->ctrl_gpio, 0);
udelay(props->timing.detect_us);
gpiod_set_value(props->ctrl_gpio, 1);
local_irq_restore(flags);
}
EXPORT_SYMBOL_NS_GPL(expresswire_enable, "EXPRESSWIRE");
static void expresswire_start(struct expresswire_common_props *props)
{
gpiod_set_value(props->ctrl_gpio, 1);
udelay(props->timing.data_start_us);
}
static void expresswire_end(struct expresswire_common_props *props)
{
gpiod_set_value(props->ctrl_gpio, 0);
udelay(props->timing.end_of_data_low_us);
gpiod_set_value(props->ctrl_gpio, 1);
udelay(props->timing.end_of_data_high_us);
}
static void expresswire_set_bit(struct expresswire_common_props *props, bool bit)
{
if (bit) {
gpiod_set_value(props->ctrl_gpio, 0);
udelay(props->timing.short_bitset_us);
gpiod_set_value(props->ctrl_gpio, 1);
udelay(props->timing.long_bitset_us);
} else {
gpiod_set_value(props->ctrl_gpio, 0);
udelay(props->timing.long_bitset_us);
gpiod_set_value(props->ctrl_gpio, 1);
udelay(props->timing.short_bitset_us);
}
}
void expresswire_write_u8(struct expresswire_common_props *props, u8 val)
{
unsigned long flags;
local_irq_save(flags);
expresswire_start(props);
for (int i = 7; i >= 0; i--)
expresswire_set_bit(props, val & BIT(i));
expresswire_end(props);
local_irq_restore(flags);
}
EXPORT_SYMBOL_NS_GPL(expresswire_write_u8, "EXPRESSWIRE");
Annotation
- Immediate include surface: `linux/bits.h`, `linux/delay.h`, `linux/export.h`, `linux/gpio/consumer.h`, `linux/irqflags.h`, `linux/types.h`, `linux/leds-expresswire.h`.
- Detected declarations: `function expresswire_power_off`, `function expresswire_enable`, `function expresswire_start`, `function expresswire_end`, `function expresswire_set_bit`, `function expresswire_write_u8`.
- Atlas domain: Driver Families / drivers/leds.
- Implementation status: integration implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.