arch/mips/bcm47xx/workarounds.c
Source file repositories/reference/linux-study-clean/arch/mips/bcm47xx/workarounds.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/bcm47xx/workarounds.c- Extension
.c- Size
- 823 bytes
- Lines
- 37
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
bcm47xx_private.hlinux/gpio.hbcm47xx_board.hbcm47xx.h
Detected Declarations
function bcm47xx_workarounds_enable_usb_powerfunction bcm47xx_workarounds
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include "bcm47xx_private.h"
#include <linux/gpio.h>
#include <bcm47xx_board.h>
#include <bcm47xx.h>
static void __init bcm47xx_workarounds_enable_usb_power(int usb_power)
{
int err;
err = gpio_request_one(usb_power, GPIOF_OUT_INIT_HIGH, "usb_power");
if (err)
pr_err("Failed to request USB power gpio: %d\n", err);
else
gpio_free(usb_power);
}
void __init bcm47xx_workarounds(void)
{
enum bcm47xx_board board = bcm47xx_board_get();
switch (board) {
case BCM47XX_BOARD_NETGEAR_WNR3500L:
case BCM47XX_BOARD_NETGEAR_WNR3500L_V2:
bcm47xx_workarounds_enable_usb_power(12);
break;
case BCM47XX_BOARD_NETGEAR_WNDR3400V2:
case BCM47XX_BOARD_NETGEAR_WNDR3400_V3:
bcm47xx_workarounds_enable_usb_power(21);
break;
default:
/* No workaround(s) needed */
break;
}
}
Annotation
- Immediate include surface: `bcm47xx_private.h`, `linux/gpio.h`, `bcm47xx_board.h`, `bcm47xx.h`.
- Detected declarations: `function bcm47xx_workarounds_enable_usb_power`, `function bcm47xx_workarounds`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.