Linux kernel drivers and userspace services for piBrick PocketCM5, a Raspberry Pi Compute Module 5 based handheld computer.
This repository contains the hardware support required by piBrick, including the AMOLED display driver, battery and charger drivers, touchscreen driver, GPIO button service, and piBrick keyboard integration.
piBrick – A building block for handheld computing.
The recommended installation method is:
cd pibrick-drivers/scripts
bash ./install.shThe piBrick CM5 Drivers project provides the Linux-side integration for the piBrick PocketCM5 handheld platform.
The project is designed around the Raspberry Pi Compute Module 5 and integrates several independent hardware components into a single piBrick-specific driver stack.
The main components are:
- AMOLED display support
- Display backlight control
- Display color profiles
- STC3115 primary fuel-gauge support
- MAX17048 fallback fuel-gauge support
- BQ25895 charger support and final voltage-estimation fallback
- Hynitron touchscreen support
- FT5x06 touchscreen support
- GPIO power/user button handling
- piBrick keyboard HIDRAW integration
- Device Tree configuration
- DKMS kernel module installation
- Userspace helper scripts and services
- 3.92" AMOLED support
- 5.48" AMOLED support
- Automatic panel detection
- MIPI DSI interface
- 4-lane DSI
- RGB888 pixel format
- 90 Hz and 60 Hz modes for the 3.92" panel
- 60 Hz mode for the 5.48" panel
- Different backlight ranges for each panel
- Color profile support for the 3.92" Visionox panel
- Panel-specific initialization sequences
- STC3115 fuel gauge as the preferred primary SOC source
- MAX17048 as the fallback fuel gauge when STC3115 is unavailable
- BQ25895 charger and voltage-based SOC fallback when neither fuel gauge is available
- Configurable battery capacity
- Configurable charging current
- Configurable battery nominal voltage for energy reporting (default 3.70 V)
- Configurable maximum charging voltage (4.20 V default; optional 4.30 V or 4.40 V)
- Unified battery-provider selection with priority-based registration
- Hynitron touchscreen driver
- FT5x06 touchscreen support
- Up to 5 touch points
- Panel-linked touchscreen configuration
- Independent touch-coordinate rotation configuration
- GPIO-based power button
- GPIO-based user button
- Short press events
- Long press events
- Power/user button interaction handling
- Configurable long-press timing
- Userspace action scripts
The piBrick keyboard is controlled through its Raw HID interface.
pibrick-kbd.sh provides userspace access to:
- Keyboard backlight
- Keyboard backlight timeout
- Keyboard RGB
- Trackpad rotation
- Read and write operations for supported keyboard settings
.
├── Kconfig
├── LICENSE
├── Makefile
├── README.md
│
├── app
│ ├── pibrick-button-service
│ │ ├── Makefile
│ │ ├── pibrick-button-service.c
│ │ ├── pibrick-button-service.service
│ │ └── etc
│ │ └── pibrick
│ │ ├── actions
│ │ │ ├── brightness.sh
│ │ │ ├── display-on-off.sh
│ │ │ └── on-off-display-wlroot.sh
│ │ ├── power-short.sh
│ │ ├── user-long.sh
│ │ └── user-short.sh
│ │
│ └── pibrick-kbd
│ ├── Makefile
│ └── pibrick-kbd.sh
│
├── dkms
│ ├── dkms-install.sh
│ └── dkms.conf
│
├── dts
│ └── pibrick.dts
│
├── examples
│ └── config.txt
│
├── panel
│ └── panel-pibrick.c
│
├── power
│ ├── pibrick-battery.c
│ ├── pibrick-charger.c
│ ├── pibrick-stc3115.c
│ └── pibrick_battery_provider.h
│
├── scripts
│ ├── get.sh
│ ├── install.sh
│ └── uninstall.sh
│
└── touch
└── hyn_ts
├── Kconfig
├── Makefile
└── ...
The repository builds the following kernel modules (the exact module set depends on the enabled components):
| Module | Source | Purpose |
|---|---|---|
panel-pibrick |
panel/panel-pibrick.c |
piBrick AMOLED display |
pibrick-battery |
power/pibrick-battery.c |
MAX17048 fallback fuel gauge |
pibrick-charger |
power/pibrick-charger.c |
BQ25895 charger and final SOC fallback |
pibrick-stc3115 |
power/pibrick-stc3115.c |
STC3115 primary fuel gauge |
hyn_ts |
touch/hyn_ts/ |
Hynitron touchscreen |
The power drivers are kept under the power/ directory because the charger and battery gauge form the piBrick power subsystem.
The main display driver is:
panel/panel-pibrick.c
The driver supports two piBrick AMOLED panel variants.
The 3.92" panel uses:
| Property | Value |
|---|---|
| Size | 3.92" |
| Resolution | 1080 × 1240 |
| Refresh rate | 90 Hz / 60 Hz |
| Pixel format | RGB888 |
| Interface | MIPI DSI |
| DSI lanes | 4 |
| Backlight | 0–1023 |
| Touch | Hynitron |
The 3.92" panel supports both 90 Hz and 60 Hz display modes.
The preferred mode is 90 Hz.
Resolution: 1080 × 1240
Refresh: 90 Hz
Resolution: 1080 × 1240
Refresh: 60 Hz
The 5.48" panel uses:
| Property | Value |
|---|---|
| Size | 5.48" |
| Resolution | 1080 × 1920 |
| Refresh rate | 60 Hz |
| Pixel format | RGB888 |
| Interface | MIPI DSI |
| DSI lanes | 4 |
| Backlight | 0–65535 |
| Touch | FT5x06 |
The 5.48" panel has a different physical mounting orientation from the 3.92" panel. The driver and Device Tree configuration account for this physical difference.
The panel driver detects which AMOLED panel is installed by checking I²C0 address 0x38.
The detection logic is:
I²C address 0x38 responds
│
└──> 5.48" panel
I²C address 0x38 absent
│
└──> 3.92" panel
This allows the same Device Tree overlay and kernel driver to support both display variants.
The panel detection does not require changing the Device Tree overlay between the two display configurations.
The current display modes are:
Clock: 133292 kHz
HDisplay: 1080
HSync Start: 1120
HSync End: 1128
HTotal: 1168
VDisplay: 1240
VSync Start: 1250
VSync End: 1258
VTotal: 1268
Clock: 133292 kHz
HDisplay: 1080
HSync Start: 1412
HSync End: 1420
HTotal: 1752
VDisplay: 1240
VSync Start: 1250
VSync End: 1258
VTotal: 1268
Clock: 137460 kHz
HDisplay: 1080
HSync Start: 1088
HSync End: 1120
HTotal: 1160
VDisplay: 1920
VSync Start: 1961
VSync End: 1969
VTotal: 1975
The two panel variants use different brightness ranges.
Minimum: 1
Maximum: 1023
Minimum: 256
Maximum: 65535
The panel driver exposes the appropriate range through the Linux backlight subsystem depending on the detected panel.
The 3.92" Visionox AMOLED panel provides multiple color profiles.
The driver defines the following profiles:
natural
vivid
srgb
warm
cold
night
soft
The default profile is:
natural
The color profile support is implemented through the panel's MIPI DSI command interface.
The driver keeps the selected profile as part of the panel state and applies the corresponding panel commands when the profile is changed.
The available profile names are also useful when interacting with the panel's sysfs color-profile interface.
For example, the panel driver exposes color-profile functionality that can be inspected using:
find /sys -name color_profileand, where available, changed with:
echo natural > <color_profile>
echo vivid > <color_profile>
echo srgb > <color_profile>
echo warm > <color_profile>
echo cold > <color_profile>
echo night > <color_profile>
echo soft > <color_profile>The exact sysfs path depends on the kernel device hierarchy.
Display rotation is treated separately from touchscreen coordinate rotation.
The Device Tree provides a base rotation property:
rotation = <0>;
The display driver uses this property when determining the panel orientation.
The 5.48" panel is physically mounted 180 degrees opposite to the common logical orientation, so its effective panel orientation is adjusted by the driver.
Display orientation at the desktop/compositor level can then be handled independently by the Wayland environment.
This separation is important because rotating the display and rotating touchscreen coordinates are two different operations.
The piBrick power subsystem consists of:
power/
├── pibrick-battery.c
├── pibrick-charger.c
└── pibrick_battery_provider.h
The power subsystem uses one charger and up to two dedicated fuel gauges:
STC3115 (priority 200)
└── Primary battery SOC provider
│
MAX17048 (priority 100)
└── Fallback battery SOC provider
│
BQ25895
├── Charger control and charging status
└── Voltage-based SOC estimator if neither fuel gauge is active
The active fuel-gauge provider is selected by registration priority. When STC3115 is detected and registers successfully, it replaces MAX17048 as the active provider. MAX17048 and the BQ voltage estimator do not supply the battery SOC while STC3115 is active.
STC3115 uses the board's fixed 5 mΩ current-sense resistor. This value is a hardware design constant, not a user-configurable setting. Its charge-counter configuration is calculated from the configured battery capacity.
If STC3115 is absent, MAX17048 can provide SOC. If both fuel gauges are unavailable, the charger driver can provide an approximate voltage-based SOC estimate.
The pibrick-battery driver provides the MAX17048 fallback fuel-gauge provider.
It registers with priority 100. The STC3115 provider has priority 200, so STC3115 takes precedence whenever it is detected and successfully registered.
Battery capacity is configurable through Device Tree:
pibrick,battery-capacity-mah = <5000>;
The driver is designed to integrate with the Linux power-supply subsystem.
The pibrick-charger driver provides charger support using the BQ25895.
It also supplies the final voltage-based SOC fallback when neither STC3115 nor MAX17048 is registered.
The charger configuration includes:
- Battery capacity
- Charge current
- Battery regulation voltage
- Termination current
- Precharge current
- Minimum system voltage
- Boost voltage
- Boost current
- Thermal regulation threshold
- Charger interrupt
The default piBrick configuration uses:
Battery capacity: 5000 mAh
Charge current: 4000 mA
Battery regulation: 4200000 uV (4.20 V)
piBrick does not include a battery. The battery capacity, nominal voltage, and maximum charging voltage must be configured to match the cell installed by the user. These are independent settings:
- Nominal voltage is used for battery energy reporting, including
energy_full_designand related energy values exposed to UPower. - Maximum charging voltage configures the BQ25895 charge-voltage regulation target. It must match the battery manufacturer's specification.
- Battery capacity is the cell's rated capacity and is used by the fuel-gauge and energy calculations.
The generic defaults are:
config.txt parameter |
Unit | Default | Purpose |
|---|---|---|---|
battery_capacity |
mAh | 5000 |
Nominal battery capacity |
battery_nominal_voltage_uv |
µV | 3700000 (3.70 V) |
Nominal cell voltage for energy reporting |
battery_max_voltage_uv |
µV | 4200000 (4.20 V) |
Maximum charging/regulation voltage |
charge_current_ma |
mA | 4000 |
Configured charging current |
battery_max_voltage_uv accepts these targets:
| Requested target | BQ25895 regulation setting |
|---|---|
4200000 (4.20 V) |
4.208 V |
4300000 (4.30 V) |
4.304 V |
4400000 (4.40 V) |
4.400 V |
The BQ25895 uses 16 mV regulation steps, so the actual programmed voltage can differ slightly from a requested target where it does not land exactly on a hardware step. The driver reads the actual charger regulation voltage for full-charge synchronization.
Conventional battery rated at 3.70 V nominal and 4.20 V maximum charging:
dtoverlay=pibrick,battery_capacity=5000,battery_nominal_voltage_uv=3700000,battery_max_voltage_uv=4200000Battery rated at 3.85 V nominal and 4.40 V maximum charging:
dtoverlay=pibrick,battery_capacity=5000,battery_nominal_voltage_uv=3850000,battery_max_voltage_uv=4400000You can also configure the charging current:
dtoverlay=pibrick,battery_capacity=5000,charge_current_ma=4000,battery_nominal_voltage_uv=3850000,battery_max_voltage_uv=4400000The equivalent generic-default configuration is:
dtoverlay=pibrickBattery safety: Use the maximum charging voltage specified by the manufacturer for the exact battery cell. A nominal voltage such as 3.85 V does not, by itself, establish whether the cell supports 4.20 V, 4.30 V, or 4.40 V charging. Never select a higher charging voltage based only on the battery's nominal voltage or chemistry label.
The Device Tree supports two touchscreen configurations.
The touchscreen controllers are connected through I²C0.
The 3.92" AMOLED uses the Hynitron touchscreen controller.
The Device Tree node uses:
compatible = "hyn,66xx";
reg = <0x5a>;
The touchscreen configuration includes:
I²C address: 0x5A
Interrupt GPIO: GPIO4
Reset GPIO: GPIO17
Maximum touches: 5
Display: 1080 × 1240
The Hynitron driver source is located under:
touch/hyn_ts/
It contains the Hynitron core, I²C/SPI support, gesture support, proximity support, filesystem/tool support, and supported controller implementations.
The 5.48" AMOLED uses an FT5x06-compatible touchscreen controller.
The Device Tree node uses:
compatible = "edt,edt-ft5406";
reg = <0x38>;
The configuration includes:
I²C address: 0x38
Reset GPIO: GPIO17
Maximum touches: 5
Touch X: 1080
Touch Y: 1920
The touchscreen configuration also enables:
touchscreen-inverted-x;
touchscreen-inverted-y;
to account for the physical mounting orientation of the 5.48" display.
Touchscreen rotation is configured independently from display rotation.
This is intentional because the touchscreen is an independent I²C input device.
For the 3.92" Hynitron touchscreen, coordinate transformation is configured using the Hynitron-specific properties.
For the 5.48" FT5x06 touchscreen:
touchscreen-inverted-x;
touchscreen-inverted-y;
provide the required 180-degree coordinate transformation.
The userspace button service is:
pibrick-button-service
Source:
app/pibrick-button-service/
The service executable is installed as:
/usr/sbin/pibrick-button-service
The systemd service is installed as:
/etc/systemd/system/pibrick-button-service.service
The piBrick button service handles the GPIO-based power and user buttons.
The current button logic uses:
GPIO23 = User button
GPIO20 = Power button
The button handling is designed to account for the electrical interaction between these two inputs.
The button logic distinguishes between:
- User button press
- Power button press
- User button release
- Power button release
- Combined power/user states
- Short press
- Long press
An important part of the logic is that the user button takes precedence when both buttons are active.
For example:
GPIO23 active
→ User button pressed
When both inputs are active:
GPIO20 active
GPIO23 active
the state is treated as:
User pressed
Power not pressed
This prevents a power-button event from being generated when the physical state represents a user-button action.
If the user button remains pressed while the power button is released, the power-release transition is treated as the corresponding user-release transition.
The installed piBrick action scripts are:
/etc/pibrick/
├── actions/
│ ├── brightness.sh
│ ├── display-on-off.sh
│ └── on-off-display-wlroot.sh
├── power-short.sh
├── user-long.sh
└── user-short.sh
These scripts provide the userspace actions associated with the button events.
Long-press handling does not need to wait until the physical button is released.
The long-press event is generated once the configured long-press duration has elapsed.
The long-press timing is configurable in the button-service implementation.
This allows an action such as user-long.sh to execute while the button is still being held.
The piBrick keyboard integration is located at:
app/pibrick-kbd/
The main userspace utility is:
pibrick-kbd.sh
The script communicates with the piBrick keyboard firmware using the Raw HID interface.
The keyboard uses:
VID = F10C
PID = 0001
The script searches for the appropriate Raw HID interface rather than assuming a fixed /dev/hidrawN device number.
The relevant HID interface is:
Interface 01
The script searches the Linux HID device tree and resolves the corresponding:
/dev/hidraw*
device automatically.
This avoids depending on whether the keyboard happens to appear as hidraw1, hidraw2, hidraw3, etc.
The piBrick keyboard protocol uses:
PIBRICK_CMD = 0xFF
The currently supported commands are:
| Command | Value | Function |
|---|---|---|
| Timeout | 0x01 |
Keyboard backlight timeout |
| Backlight | 0x02 |
Keyboard backlight level |
| RGB | 0x03 |
Keyboard RGB control |
| Trackpad rotation | 0x05 |
Trackpad orientation |
The script supports both reading and setting values where supported.
Read the current timeout:
./pibrick-kbd.sh timeoutSet the timeout:
./pibrick-kbd.sh timeout 30The valid range is:
0–255 seconds
The timeout is returned by the keyboard firmware as a single byte.
For scripting, use:
./pibrick-kbd.sh --quiet timeoutwhich outputs only the numeric value.
Read the current keyboard backlight:
./pibrick-kbd.sh backlightSet the keyboard backlight:
./pibrick-kbd.sh backlight 8The valid range is:
0–8
For example:
./pibrick-kbd.sh backlight 0
./pibrick-kbd.sh backlight 4
./pibrick-kbd.sh backlight 8The current firmware backlight levels therefore use nine states:
0 1 2 3 4 5 6 7 8
Read only the numeric value:
./pibrick-kbd.sh --quiet backlightThe keyboard RGB LEDs can be controlled using an RGB hexadecimal value.
Set a color:
./pibrick-kbd.sh rgb FF0000Examples:
./pibrick-kbd.sh rgb FF0000
./pibrick-kbd.sh rgb 00FF00
./pibrick-kbd.sh rgb 0000FFRGB can also be turned off:
./pibrick-kbd.sh rgb 0which is equivalent to:
#000000
An optional duration can be supplied in milliseconds:
./pibrick-kbd.sh rgb FF0000 1000The supported duration range is:
0–65535 ms
For example, the above command requests red for 1000 ms.
The keyboard trackpad supports four rotation states:
| Value | Rotation |
|---|---|
0 |
0° |
1 |
90° |
2 |
180° |
3 |
270° |
Read the current rotation:
./pibrick-kbd.sh rotationor:
./pibrick-kbd.sh trackpad-rotationSet the rotation:
./pibrick-kbd.sh rotation 0
./pibrick-kbd.sh rotation 1
./pibrick-kbd.sh rotation 2
./pibrick-kbd.sh rotation 3The long command name is also accepted:
./pibrick-kbd.sh trackpad-rotation 1This functionality is useful when the display orientation changes and the trackpad coordinate orientation needs to follow it.
The keyboard script supports:
-qor:
--quietFor example:
./pibrick-kbd.sh --quiet backlightreturns only the value.
This makes the script convenient for other shell scripts and automatic orientation/backlight handling.
The piBrick Device Tree overlay is:
dts/pibrick.dts
It is compiled into:
pibrick.dtbo
The overlay is compatible with:
brcm,bcm2712
raspberrypi,5-compute-module
raspberrypi,5-model-b
The standard configuration uses the generic defaults:
dtoverlay=pibrickThe defaults are:
battery_capacity = 5000 mAh
battery_nominal_voltage_uv = 3700000 uV (3.70 V)
battery_max_voltage_uv = 4200000 uV (4.20 V)
charge_current_ma = 4000 mA
To customize the battery, specify the values in config.txt. For example,
a 5000 mAh cell rated at 3.85 V nominal and 4.40 V maximum charging:
dtoverlay=pibrick,battery_capacity=5000,battery_nominal_voltage_uv=3850000,battery_max_voltage_uv=4400000The overlay enables DSI1:
target = <&dsi1>;
The panel is configured as:
compatible = "pibrick,amoled";
The display reset GPIO is:
GPIO20
The display TE GPIO is:
GPIO47
The base rotation property is:
rotation = <0>;
The touchscreen devices are placed on:
I²C0
The Hynitron controller uses:
Address: 0x5A
IRQ: GPIO4
Reset: GPIO17
The FT5x06 controller uses:
Address: 0x38
Reset: GPIO17
The two touchscreen nodes allow the same overlay to support the two piBrick display configurations.
The power devices are connected to I²C1:
| Device | Address | Role |
|---|---|---|
| BQ25895 | 0x6A |
Charger |
| MAX17048 | 0x36 |
Fallback fuel gauge |
| STC3115 | 0x70 |
Primary fuel gauge |
The charger, MAX17048, and STC3115 nodes receive the shared battery capacity and nominal-voltage configuration. The nominal voltage is used for energy reporting; it is independent of the BQ25895 maximum charging-voltage setting.
The STC3115 uses a fixed 5 mΩ sense resistor. The driver calculates CC_CNF
from that fixed value and the configured capacity; there is no
battery_sense_resistor overlay parameter.
The overlay exposes these battery and charger settings:
battery_capacity
battery_nominal_voltage_uv
battery_max_voltage_uv
charge_current_ma
Examples:
dtoverlay=pibrick,battery_capacity=5000
dtoverlay=pibrick,battery_nominal_voltage_uv=3850000
dtoverlay=pibrick,battery_max_voltage_uv=4400000
dtoverlay=pibrick,battery_capacity=5000,charge_current_ma=4000,battery_nominal_voltage_uv=3850000,battery_max_voltage_uv=4400000Use battery_nominal_voltage_uv for the battery's nominal voltage and
battery_max_voltage_uv for its manufacturer-specified maximum charging
voltage. Do not use one as a substitute for the other.
The project can be built directly on the Raspberry Pi or using an appropriate cross-compilation environment.
A matching Linux kernel build directory is required.
Check the running kernel:
uname -rThe default kernel build directory is:
/lib/modules/$(uname -r)/build
A different kernel directory can be specified using:
KDIR=/path/to/kernel/buildFrom the repository root:
makeor:
make modulesThe root Makefile builds:
panel/panel-pibrick.o
power/pibrick-battery.o
power/pibrick-charger.o
power/pibrick-stc3115.o
and separately builds the Hynitron touchscreen module under:
touch/hyn_ts/
The Hynitron driver has its own Makefile.
Build it directly:
make -C touch/hyn_tsor through the root build:
make modulesThe Hynitron module is built from multiple source files, including the Hynitron core, library components, gesture/proximity support, and supported controller implementations.
Build the Device Tree overlay with:
make dtboThe compiler uses:
dtc
with the overlay option enabled.
The result is:
pibrick.dtbo
Build the button service:
make -C app/pibrick-button-serviceBuild the keyboard utility:
make -C app/pibrick-kbdThe keyboard component produces:
pibrick-kbd.sh
The project includes DKMS support under:
dkms/
The configuration is:
dkms/dkms.conf
DKMS builds the following modules:
panel-pibrick
pibrick-battery
pibrick-charger
pibrick-stc3115
hyn_ts
DKMS allows the modules to be automatically rebuilt when a compatible kernel is installed or updated.
Check DKMS status with:
dkms statusThe recommended installation method is:
cd pibrick-drivers/scripts
bash ./install.shThe installer performs the complete piBrick setup.
It installs:
- Kernel modules through DKMS
- Device Tree overlay
dtoverlay=pibrick- Button service
- Button action scripts
pibrick-kbd.sh- Required userspace components
The Device Tree configuration is added to:
/boot/firmware/config.txt
using:
# piBrick CM5 drivers
dtoverlay=pibrickThe button service is enabled and started during installation.
After installation, reboot:
sudo rebootRemove the piBrick driver stack with:
cd pibrick-drivers/scripts
sudo ./uninstall.shThe uninstaller removes:
- DKMS modules
- piBrick Device Tree overlay
dtoverlay=pibrick- piBrick button service
- Button action scripts
- piBrick keyboard userspace component
The piBrick overlay configuration is removed from:
/boot/firmware/config.txt
Check the button service:
systemctl status pibrick-button-serviceView the installed unit:
systemctl cat pibrick-button-serviceView recent logs:
journalctl -u pibrick-button-serviceFollow logs continuously:
journalctl -u pibrick-button-service -fRestart the service:
sudo systemctl restart pibrick-button-serviceStop the service:
sudo systemctl stop pibrick-button-serviceStart it again:
sudo systemctl start pibrick-button-servicedkms statusLook for the piBrick driver modules:
panel-pibrick
pibrick-battery
pibrick-charger
pibrick-stc3115
hyn_ts
lsmod | grep -E 'panel_pibrick|pibrick_battery|pibrick_charger|hyn_ts'grep -E '^[[:space:]]*dtoverlay=pibrick' \
/boot/firmware/config.txtsystemctl status pibrick-button-serviceFor piBrick-specific messages:
dmesg | grep -i pibrickFor display, DSI, power, and touchscreen messages:
dmesg | grep -iE 'stc3115|max17048|battery provider|charger|battery'The DRM display devices can be inspected with:
ls -l /sys/class/drm/The available display modes can be inspected through the DRM sysfs interface.
Inspect the Linux power-supply devices and current SOC:
ls -l /sys/class/power_supply/
cat /sys/class/power_supply/battery/capacity
upower -dCheck which gauge was selected:
dmesg | grep -iE 'stc3115|max17048|battery provider'Expected selection behavior:
- STC3115 detected:
STC3115 selected as primary fuel gauge; its SOC is used directly. - STC3115 absent and MAX17048 available: MAX17048 provides SOC.
- Both gauges absent: BQ25895 voltage-based SOC estimation is used.
The MAX17048 may briefly register during boot before STC3115 probes. If STC3115 later logs that it was selected as the primary fuel gauge, it has replaced MAX17048 as the active provider.
In UPower, percentage is the current battery SOC. capacity is battery health/full-charge capacity relative to design capacity; it is not the current SOC.
Inspect I²C devices:
i2cdetect -y 0The expected touchscreen addresses are:
0x5A
for Hynitron, and:
0x38
for FT5x06.
The 0x38 device is also used by the panel-detection mechanism to distinguish the 5.48" display configuration.
The piBrick keyboard script can automatically locate the correct HIDRAW device.
Check the HID devices:
ls -l /dev/hidraw*Then test:
./pibrick-kbd.sh backlightor:
./pibrick-kbd.sh timeoutFor a script-friendly response:
./pibrick-kbd.sh --quiet backlightIf the keyboard is not detected, the script reports:
Error: piBrick Vial Raw HID device not found.
This project is licensed under the:
GNU General Public License v3.0 or later
SPDX identifier:
GPL-3.0-or-later
See LICENSE for the complete license text.
This repository contains the Linux kernel drivers and userspace integration for the piBrick PocketCM5 platform.
The driver stack currently covers:
- Display
- Display backlight
- Display color profiles
- Battery
- Charger
- Touchscreen
- Physical buttons
- Keyboard HID integration
- Device Tree
- DKMS
Additional piBrick hardware revisions and features may be integrated into the repository as the platform evolves.
piBrick – A building block for handheld computing.