drivers/mfd/bq257xx.c
Source file repositories/reference/linux-study-clean/drivers/mfd/bq257xx.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mfd/bq257xx.c- Extension
.c- Size
- 4160 bytes
- Lines
- 148
- Domain
- Driver Families
- Bucket
- drivers/mfd
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/device.hlinux/i2c.hlinux/mfd/bq257xx.hlinux/mfd/core.hlinux/regmap.h
Detected Declarations
function bq257xx_probe
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* BQ257XX Core Driver
* Copyright (C) 2025 Chris Morgan <macromorgan@hotmail.com>
*/
#include <linux/device.h>
#include <linux/i2c.h>
#include <linux/mfd/bq257xx.h>
#include <linux/mfd/core.h>
#include <linux/regmap.h>
static const struct regmap_range bq25703_readonly_reg_ranges[] = {
regmap_reg_range(BQ25703_CHARGER_STATUS, BQ25703_MANUFACT_DEV_ID),
};
static const struct regmap_access_table bq25703_writeable_regs = {
.no_ranges = bq25703_readonly_reg_ranges,
.n_no_ranges = ARRAY_SIZE(bq25703_readonly_reg_ranges),
};
static const struct regmap_range bq25703_volatile_reg_ranges[] = {
regmap_reg_range(BQ25703_CHARGE_OPTION_0, BQ25703_IIN_HOST),
regmap_reg_range(BQ25703_CHARGER_STATUS, BQ25703_ADC_OPTION),
};
static const struct regmap_access_table bq25703_volatile_regs = {
.yes_ranges = bq25703_volatile_reg_ranges,
.n_yes_ranges = ARRAY_SIZE(bq25703_volatile_reg_ranges),
};
static const struct regmap_config bq25703_regmap_config = {
.reg_bits = 8,
.val_bits = 16,
.max_register = BQ25703_ADC_OPTION,
.cache_type = REGCACHE_MAPLE,
.wr_table = &bq25703_writeable_regs,
.volatile_table = &bq25703_volatile_regs,
.val_format_endian = REGMAP_ENDIAN_LITTLE,
};
static const struct regmap_range bq25792_writeable_reg_ranges[] = {
regmap_reg_range(BQ25792_REG00_MIN_SYS_VOLTAGE,
BQ25792_REG18_NTC_CONTROL_1),
regmap_reg_range(BQ25792_REG28_CHARGER_MASK_0,
BQ25792_REG30_ADC_FUNCTION_DISABLE_1),
};
static const struct regmap_access_table bq25792_writeable_regs = {
.yes_ranges = bq25792_writeable_reg_ranges,
.n_yes_ranges = ARRAY_SIZE(bq25792_writeable_reg_ranges),
};
static const struct regmap_range bq25792_volatile_reg_ranges[] = {
regmap_reg_range(BQ25792_REG19_ICO_CURRENT_LIMIT,
BQ25792_REG27_FAULT_FLAG_1),
regmap_reg_range(BQ25792_REG31_IBUS_ADC,
BQ25792_REG47_DPDM_DRIVER),
};
static const struct regmap_access_table bq25792_volatile_regs = {
.yes_ranges = bq25792_volatile_reg_ranges,
.n_yes_ranges = ARRAY_SIZE(bq25792_volatile_reg_ranges),
};
static const struct regmap_config bq25792_regmap_config = {
.reg_bits = 8,
.val_bits = 8,
.max_register = BQ25792_REG48_PART_INFORMATION,
.cache_type = REGCACHE_MAPLE,
.wr_table = &bq25792_writeable_regs,
.volatile_table = &bq25792_volatile_regs,
};
static const struct mfd_cell cells[] = {
MFD_CELL_NAME("bq257xx-regulator"),
MFD_CELL_NAME("bq257xx-charger"),
};
static int bq257xx_probe(struct i2c_client *client)
{
const struct regmap_config *rcfg;
struct bq257xx_device *ddata;
int ret;
ddata = devm_kzalloc(&client->dev, sizeof(*ddata), GFP_KERNEL);
if (!ddata)
return -ENOMEM;
ddata->type = (uintptr_t)i2c_get_match_data(client);
Annotation
- Immediate include surface: `linux/device.h`, `linux/i2c.h`, `linux/mfd/bq257xx.h`, `linux/mfd/core.h`, `linux/regmap.h`.
- Detected declarations: `function bq257xx_probe`.
- Atlas domain: Driver Families / drivers/mfd.
- Implementation status: source 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.