Home
last modified time | relevance | path

Searched full:actions (Results 1 – 25 of 163) sorted by relevance

1234567

/Documentation/devicetree/bindings/clock/
Dactions,owl-cmu.txt1 * Actions Semi Owl Clock Management Unit (CMU)
3 The Actions Semi Owl Clock Management Unit generates and supplies clock
10 "actions,s900-cmu"
11 "actions,s700-cmu"
12 "actions,s500-cmu"
23 dt-bindings/clock/actions,s900-cmu.h or actions,s700-cmu.h or
24 actions,s500-cmu.h header and can be used in device tree sources.
31 Actions Semi S900 CMU also requires one more clock:
37 compatible = "actions,s900-cmu";
48 compatible = "actions,s900-uart", "actions,owl-uart";
/Documentation/devicetree/bindings/arm/
Dactions.yaml4 $id: http://devicetree.org/schemas/arm/actions.yaml#
7 title: Actions Semi platforms
18 # The Actions Semi S500 is a quad-core ARM Cortex-A9 SoC.
24 - const: actions,s500
29 - const: actions,s500
34 - const: actions,s500
36 # The Actions Semi S700 is a quad-core ARM Cortex-A53 SoC.
41 - const: actions,s700
45 - const: actions,s700
47 # The Actions Semi S900 is a quad-core ARM Cortex-A53 SoC.
[all …]
/Documentation/devicetree/bindings/i2c/
Di2c-owl.yaml7 title: Actions Semi Owl I2C Controller
13 This I2C controller is found in the Actions Semi Owl SoCs:
22 - actions,s500-i2c # Actions Semi S500 compatible SoCs
23 - actions,s700-i2c # Actions Semi S700 compatible SoCs
24 - actions,s900-i2c # Actions Semi S900 compatible SoCs
52 #include <dt-bindings/clock/actions,s900-cmu.h>
55 compatible = "actions,s900-i2c";
/Documentation/devicetree/bindings/serial/
Dactions,owl-uart.yaml4 $id: http://devicetree.org/schemas/serial/actions,owl-uart.yaml#
7 title: Actions Semi Owl UART
19 - actions,s500-uart
20 - actions,s900-uart
21 - const: actions,owl-uart
41 #include <dt-bindings/clock/actions,s500-cmu.h>
44 compatible = "actions,s500-uart", "actions,owl-uart";
/Documentation/devicetree/bindings/net/
Dactions,owl-emac.yaml4 $id: http://devicetree.org/schemas/net/actions,owl-emac.yaml#
7 title: Actions Semi Owl SoCs Ethernet MAC Controller
13 This Ethernet MAC is used on the Owl family of SoCs from Actions Semi.
24 - const: actions,owl-emac
27 - actions,s500-emac
28 - const: actions,owl-emac
49 actions,ethcfg:
72 #include <dt-bindings/clock/actions,s500-cmu.h>
74 #include <dt-bindings/reset/actions,s500-reset.h>
77 compatible = "actions,s500-emac", "actions,owl-emac";
/Documentation/devicetree/bindings/timer/
Dactions,owl-timer.txt1 Actions Semi Owl Timer
4 - compatible : "actions,s500-timer" for S500
5 "actions,s700-timer" for S700
6 "actions,s900-timer" for S900
16 compatible = "actions,s500-timer";
/Documentation/devicetree/bindings/interrupt-controller/
Dactions,owl-sirq.yaml4 $id: http://devicetree.org/schemas/interrupt-controller/actions,owl-sirq.yaml#
7 title: Actions Semi Owl SoCs SIRQ interrupt controller
14 This interrupt controller is found in the Actions Semi Owl SoCs (S500, S700
20 - actions,s500-sirq
21 - actions,s700-sirq
22 - actions,s900-sirq
56 compatible = "actions,s500-sirq";
/Documentation/devicetree/bindings/power/
Dactions,owl-sps.txt1 Actions Semi Owl Smart Power System (SPS)
4 - compatible : "actions,s500-sps" for S500
5 "actions,s700-sps" for S700
6 "actions,s900-sps" for S900
18 compatible = "actions,s500-sps";
/Documentation/devicetree/bindings/mmc/
Dowl-mmc.yaml7 title: Actions Semi Owl SoCs SD/MMC/SDIO controller
18 - const: actions,owl-mmc
21 - actions,s500-mmc
22 - actions,s700-mmc
23 - const: actions,owl-mmc
57 compatible = "actions,owl-mmc";
/Documentation/devicetree/bindings/dma/
Dowl-dma.yaml7 title: Actions Semi Owl SoCs DMA controller
11 supporting 10 independent DMA channels for the Actions Semi S700 SoC and 12
23 - actions,s500-dma
24 - actions,s700-dma
25 - actions,s900-dma
68 compatible = "actions,s900-dma";
/Documentation/devicetree/bindings/mfd/
Dactions,atc260x.yaml4 $id: http://devicetree.org/schemas/mfd/actions,atc260x.yaml#
7 title: Actions Semi ATC260x Power Management IC
29 - actions,atc2603c
30 - actions,atc2609a
55 - actions,atc2603c-regulator
56 - actions,atc2609a-regulator
96 const: actions,atc2603c-regulator
108 const: actions,atc2609a-regulator
137 compatible = "actions,atc2603c";
145 compatible = "actions,atc2603c-regulator";
/Documentation/fault-injection/
Dnotifier-error-inject.rst18 /sys/kernel/debug/notifier-error-inject/pm/actions/<notifier event>/error
29 # echo -12 > actions/PM_SUSPEND_PREPARE/error
37 /sys/kernel/debug/notifier-error-inject/memory/actions/<notifier event>/error
47 # echo -12 > actions/MEM_GOING_OFFLINE/error
55 /sys/kernel/debug/notifier-error-inject/pSeries-reconfig/actions/<notifier event>/error
68 /sys/kernel/debug/notifier-error-inject/netdev/actions/<notifier event>/error
85 # echo -22 > actions/NETDEV_CHANGEMTU/error
/Documentation/networking/devlink/
Ddevlink-reload.rst11 Reload Actions
17 .. list-table:: Possible reload actions
46 command returns the list of actions which were actrually performed.
51 By default reload actions are not limited and driver implementation may
52 include reset or downtime as needed to perform the actions.
/Documentation/networking/
Dtc-actions-env-rules.rst4 TC Actions - Environmental Rules
8 The "environmental" rules for authors of any new tc actions are:
23 The "environmental" rules for callers of actions (qdiscs etc) are:
/Documentation/trace/
Dboottime-trace.rst14 filter and actions, histograms, kprobe-events and synthetic-events,
111 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.actions = ACTION[, ACTION2[...]]
112 Set ACTIONs to the GROUP:EVENT.
133 for the histogram actions. For the detail of the each parameter,
188 Note that this 'hist' option can conflict with the per-event 'actions'
189 option if the 'actions' option has a histogram action.
209 For example, to add filter and actions for each event, define kprobe
274 actions = "traceon"
278 actions = "traceoff"
/Documentation/watchdog/
Dmlx-wdt.rst43 There are several actions that can be defined in the watchdog:
45 The last 2 actions are performed without a system reset.
46 Actions without reset are provided for auxiliary watchdog device,
/Documentation/netlink/specs/
Dovs_flow.yaml278 - omit-actions
388 name: actions
392 Nested attributes specifying the actions to take for packets that
396 actions. To clear the actions, an OVS_FLOW_ATTR_ACTIONS without any
633 Probabilistically executes actions, as specified in the nested attributes.
709 Make a copy of the packet and execute a list of actions without
716 Check the packet length and execute a set of actions if greater than
717 the specified packet length, else execute another set of actions.
815 name: actions-if-greater
819 name: actions-if-less-equal
[all …]
/Documentation/driver-api/usb/
Dhotplug.rst22 be driver-specific actions.
24 This involves a mix of kernel mode and user mode actions. Making devices
25 be immediately usable means that any user mode actions can't wait for an
30 Those triggered actions must support a system's administrative policies;
34 Because some of those actions rely on information about drivers (metadata)
/Documentation/scsi/
Dscsi_eh.rst161 We'll talk about how SCSI EH takes actions to abort - make LLDD
168 LLDD's can implement SCSI EH actions in one of the following two
209 To achieve these goals, EH performs recovery actions with increasing
210 severity. Some actions are performed by issuing SCSI commands and
222 Higher-severity actions are taken only when lower-severity actions
229 - Recovery actions are performed on failed scmds on the to do list,
237 - Higher severity actions are taken iff eh_work_q is not empty after
238 lower severity actions are complete.
363 higher-severity actions.
/Documentation/devicetree/bindings/pinctrl/
Dactions,s500-pinctrl.yaml4 $id: http://devicetree.org/schemas/pinctrl/actions,s500-pinctrl.yaml#
7 title: Actions Semi S500 SoC pinmux & GPIO controller
20 const: actions,s500-pinctrl
207 compatible = "actions,s500-pinctrl";
/Documentation/driver-api/80211/
Dcfg80211.rst42 Actions and configuration
46 :doc: Actions and configuration
/Documentation/devicetree/bindings/regulator/
Dregulator.yaml141 damaged. Recovery actions should be initiated. Zero can be passed to
162 damaged. Recovery actions should be initiated. Zero can be passed to
184 it gets damaged. Recovery actions should be initiated. Zero can be passed
194 under-voltage event is needed, allowing for certain non-urgent actions to
212 gets damaged. Recovery actions should be initiated. Zero can be passed to
/Documentation/dev-tools/kunit/api/
Dresource.rst10 state on a per-test basis, register custom cleanup actions, and more.
/Documentation/ABI/testing/
Dgpio-cdev19 Initiate various actions.
/Documentation/livepatch/
Dcumulative-patches.rst80 In other words, the cumulative patch is responsible for doing any actions
88 fixes/features are added/removed and what special actions are necessary

1234567