drivers/regulator/dummy.c
Source file repositories/reference/linux-study-clean/drivers/regulator/dummy.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/regulator/dummy.c- Extension
.c- Size
- 1659 bytes
- Lines
- 73
- Domain
- Driver Families
- Bucket
- drivers/regulator
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/err.hlinux/export.hlinux/device/faux.hlinux/regulator/driver.hlinux/regulator/machine.hdummy.h
Detected Declarations
function dummy_regulator_probefunction regulator_dummy_init
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-or-later
/*
* dummy.c
*
* Copyright 2010 Wolfson Microelectronics PLC.
*
* Author: Mark Brown <broonie@opensource.wolfsonmicro.com>
*
* This is useful for systems with mixed controllable and
* non-controllable regulators, as well as for allowing testing on
* systems with no controllable regulators.
*/
#include <linux/err.h>
#include <linux/export.h>
#include <linux/device/faux.h>
#include <linux/regulator/driver.h>
#include <linux/regulator/machine.h>
#include "dummy.h"
struct regulator_dev *dummy_regulator_rdev;
static const struct regulator_init_data dummy_initdata = {
.constraints = {
.always_on = 1,
},
};
static const struct regulator_ops dummy_ops;
static const struct regulator_desc dummy_desc = {
.name = "regulator-dummy",
.id = -1,
.type = REGULATOR_VOLTAGE,
.owner = THIS_MODULE,
.ops = &dummy_ops,
};
static int dummy_regulator_probe(struct faux_device *fdev)
{
struct regulator_config config = { };
int ret;
config.dev = &fdev->dev;
config.init_data = &dummy_initdata;
dummy_regulator_rdev = devm_regulator_register(&fdev->dev, &dummy_desc,
&config);
if (IS_ERR(dummy_regulator_rdev)) {
ret = PTR_ERR(dummy_regulator_rdev);
pr_err("Failed to register regulator: %d\n", ret);
return ret;
}
return 0;
}
static struct faux_device_ops dummy_regulator_driver = {
.probe = dummy_regulator_probe,
};
static struct faux_device *dummy_fdev;
void __init regulator_dummy_init(void)
{
dummy_fdev = faux_device_create("reg-dummy", NULL, &dummy_regulator_driver);
if (!dummy_fdev) {
pr_err("Failed to allocate dummy regulator device\n");
return;
}
}
Annotation
- Immediate include surface: `linux/err.h`, `linux/export.h`, `linux/device/faux.h`, `linux/regulator/driver.h`, `linux/regulator/machine.h`, `dummy.h`.
- Detected declarations: `function dummy_regulator_probe`, `function regulator_dummy_init`.
- Atlas domain: Driver Families / drivers/regulator.
- 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.