Home
last modified time | relevance | path

Searched +full:mbi +full:- +full:alias (Results 1 – 4 of 4) sorted by relevance

/Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/
Darm,gic-v3.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/arm,gic-v3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marc Zyngier <maz@kernel.org>
15 Software Generated Interrupts (SGI), and Locality-specific Peripheral
19 - $ref: /schemas/interrupt-controller.yaml#
24 - items:
25 - enum:
26 - qcom,msm8996-gic-v3
[all …]
/Linux-v6.1/drivers/irqchip/
Dirq-gic-v3-mbi.c1 // SPDX-License-Identifier: GPL-2.0
19 #include <linux/irqchip/arm-gic-v3.h>
33 .name = "MBI",
50 * Using ACPI? There is no MBI support in the spec, you in mbi_irq_gic_domain_alloc()
53 if (!is_of_node(domain->parent->fwnode)) in mbi_irq_gic_domain_alloc()
54 return -EINVAL; in mbi_irq_gic_domain_alloc()
61 fwspec.fwnode = domain->parent->fwnode; in mbi_irq_gic_domain_alloc()
64 fwspec.param[1] = hwirq - 32; in mbi_irq_gic_domain_alloc()
71 d = irq_domain_get_irq_data(domain->parent, virq); in mbi_irq_gic_domain_alloc()
72 return d->chip->irq_set_type(d, IRQ_TYPE_EDGE_RISING); in mbi_irq_gic_domain_alloc()
[all …]
/Linux-v6.1/arch/arm64/boot/dts/rockchip/
Drk356x.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
6 #include <dt-bindings/clock/rk3568-cru.h>
7 #include <dt-bindings/interrupt-controller/arm-gic.h>
8 #include <dt-bindings/interrupt-controller/irq.h>
9 #include <dt-bindings/phy/phy.h>
10 #include <dt-bindings/pinctrl/rockchip.h>
11 #include <dt-bindings/power/rk3568-power.h>
12 #include <dt-bindings/soc/rockchip,boot-mode.h>
13 #include <dt-bindings/thermal/thermal.h>
16 interrupt-parent = <&gic>;
[all …]
/Linux-v6.1/include/uapi/linux/
Dnl80211.h6 * Copyright 2006-2010 Johannes Berg <johannes@sipsolutions.net>
13 * Copyright 2015-2017 Intel Deutschland GmbH
14 * Copyright (C) 2018-2022 Intel Corporation
32 * be careful not to break things - i.e. don't move anything around or so
74 * - a setup station entry is added, not yet authorized, without any rate
76 * - when the TDLS setup is done, a single NL80211_CMD_SET_STATION is valid
79 * - %NL80211_TDLS_ENABLE_LINK is then used
80 * - after this, the only valid operation is to remove it by tearing down
95 * Frame registration is done on a per-interface basis and registrations
137 * software, like the AP-VLAN type in mac80211 for example, there's
[all …]