arch/arm/boot/dts/broadcom/bcm47094-dlink-dir-890l.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/broadcom/bcm47094-dlink-dir-890l.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/broadcom/bcm47094-dlink-dir-890l.dts- Extension
.dts- Size
- 4211 bytes
- Lines
- 209
- Domain
- Architecture Layer
- Bucket
- arch/arm
- Inferred role
- Architecture Layer: configuration, schema, or hardware description
- Status
- atlas-only
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
bcm47094.dtsibcm5301x-nand-cs0-bch1.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
/*
* Device tree for D-Link DIR-890L
* D-Link calls this board "WRGAC36"
* this router has the same looks and form factor as D-Link DIR-885L.
*
* Some differences from DIR-885L include a separate USB2 port, separate LEDs
* for USB2 and USB3, a separate VCC supply for the USB2 slot and no
* router/extender switch is mounted (there is an empty mount point on the
* PCB) so this device is a pure router. Also the LAN ports are in the right
* order.
*
* Based on the device tree for DIR-885L
* Copyright (C) 2016 Rafał Miłecki <zajec5@gmail.com>
* Copyright (C) 2022 Linus Walleij
*/
/dts-v1/;
#include "bcm47094.dtsi"
#include "bcm5301x-nand-cs0-bch1.dtsi"
/ {
compatible = "dlink,dir-890l", "brcm,bcm47094", "brcm,bcm4708";
model = "D-Link DIR-890L";
chosen {
bootargs = "console=ttyS0,115200 earlycon";
};
memory@0 {
device_type = "memory";
reg = <0x00000000 0x08000000>,
<0x88000000 0x08000000>;
};
leds {
/*
* LED information is derived from the boot log which
* conveniently lists all the LEDs.
*/
compatible = "gpio-leds";
led-power-white {
label = "bcm53xx:white:power";
gpios = <&chipcommon 0 GPIO_ACTIVE_LOW>;
linux,default-trigger = "default-on";
};
led-wan-white {
label = "bcm53xx:white:wan";
gpios = <&chipcommon 1 GPIO_ACTIVE_LOW>;
};
led-power-amber {
label = "bcm53xx:amber:power";
gpios = <&chipcommon 2 GPIO_ACTIVE_LOW>;
};
led-wan-amber {
label = "bcm53xx:amber:wan";
gpios = <&chipcommon 3 GPIO_ACTIVE_LOW>;
};
led-usb3-white {
label = "bcm53xx:white:usb3";
gpios = <&chipcommon 8 GPIO_ACTIVE_LOW>;
trigger-sources = <&xhci_port1>;
linux,default-trigger = "usbport";
};
Annotation
- Immediate include surface: `bcm47094.dtsi`, `bcm5301x-nand-cs0-bch1.dtsi`.
- Atlas domain: Architecture Layer / arch/arm.
- Implementation status: atlas-only.
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.