tmakin/ack-tegra
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge 3b80dee70e ("Merge tag 'sched-urgent-2020-12-27' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip") into android-mainline

Browse Source 
Steps on the way to 5.11-rc1

Resolves merge issues in:
	kernel/sched/sched.h

Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: If5b00273202785ed39c5f46dfb92dd7791499cda
This commit is contained in:
Greg Kroah-Hartman
2021-01-06 11:55:29 +01:00
parent 1bc25c60c1 3b80dee70e
commit 1e5e020b08
318 changed files with 4910 additions and 3464 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/admin-guide/sysctl/vm.rst
+1 -1
View File
@@ -444,7 +444,7 @@ While most applications need less than a thousand maps, certain
programs, particularly malloc debuggers, may consume lots of them,
e.g., up to one or two maps per allocation.
The default value is 65536.
The default value is 65530.
memory_failure_early_kill:
Documentation/devicetree/bindings/arm/idle-states.yaml
+1 -1
View File
@@ -313,7 +313,7 @@ patternProperties:
wakeup-latency-us by this duration.
idle-state-name:
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
description:
A string used as a descriptive name for the idle state.
Documentation/devicetree/bindings/bus/allwinner,sun50i-a64-de2.yaml
+1 -1
View File
@@ -34,7 +34,7 @@ properties:
description:
The SRAM that needs to be claimed to access the display engine
bus.
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
maxItems: 1
ranges: true
Documentation/devicetree/bindings/bus/baikal,bt1-axi.yaml
+1 -1
View File
@@ -46,7 +46,7 @@ properties:
const: 1
syscon:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description: Phandle to the Baikal-T1 System Controller DT node
interrupts:
Documentation/devicetree/bindings/clock/imx8qxp-lpcg.yaml
+10 -10
View File
@@ -29,18 +29,18 @@ properties:
- const: fsl,imx8qxp-lpcg
- items:
- enum:
- fsl,imx8qm-lpcg
- fsl,imx8qm-lpcg
- const: fsl,imx8qxp-lpcg
- enum:
- fsl,imx8qxp-lpcg-adma
- fsl,imx8qxp-lpcg-conn
- fsl,imx8qxp-lpcg-dc
- fsl,imx8qxp-lpcg-dsp
- fsl,imx8qxp-lpcg-gpu
- fsl,imx8qxp-lpcg-hsio
- fsl,imx8qxp-lpcg-img
- fsl,imx8qxp-lpcg-lsio
- fsl,imx8qxp-lpcg-vpu
- fsl,imx8qxp-lpcg-adma
- fsl,imx8qxp-lpcg-conn
- fsl,imx8qxp-lpcg-dc
- fsl,imx8qxp-lpcg-dsp
- fsl,imx8qxp-lpcg-gpu
- fsl,imx8qxp-lpcg-hsio
- fsl,imx8qxp-lpcg-img
- fsl,imx8qxp-lpcg-lsio
- fsl,imx8qxp-lpcg-vpu
deprecated: true
reg:
maxItems: 1
Documentation/devicetree/bindings/connector/usb-connector.yaml
+5 -5
View File
@@ -37,7 +37,7 @@ properties:
description: Size of the connector, should be specified in case of
non-fullsize 'usb-a-connector' or 'usb-b-connector' compatible
connectors.
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
enum:
- mini
@@ -67,7 +67,7 @@ properties:
power-role:
description: Determines the power role that the Type C connector will
support. "dual" refers to Dual Role Port (DRP).
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
enum:
- source
@@ -76,7 +76,7 @@ properties:
try-power-role:
description: Preferred power role.
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
enum:
- source
@@ -86,7 +86,7 @@ properties:
data-role:
description: Data role if Type C connector supports USB data. "dual" refers
Dual Role Device (DRD).
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
enum:
- host
@@ -105,7 +105,7 @@ properties:
Type-C Cable and Connector specification, when Power Delivery is not
supported.
allOf:
- $ref: /schemas/types.yaml#definitions/string
- $ref: /schemas/types.yaml#/definitions/string
enum:
- default
- 1.5A
Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml
+2 -2
View File
@@ -49,8 +49,8 @@ properties:
Video port for panel or connector.
required:
- port@0
- port@1
- port@0
- port@1
required:
- compatible
Documentation/devicetree/bindings/display/bridge/anx6345.yaml
-2
View File
@@ -26,11 +26,9 @@ properties:
description: GPIO connected to active low reset
dvdd12-supply:
maxItems: 1
description: Regulator for 1.2V digital core power.
dvdd25-supply:
maxItems: 1
description: Regulator for 2.5V digital core power.
ports:
Documentation/devicetree/bindings/display/bridge/intel,keembay-dsi.yaml
+2 -2
View File
@@ -39,10 +39,10 @@ properties:
properties:
'#address-cells':
const: 1
const: 1
'#size-cells':
const: 0
const: 0
port@0:
type: object
Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml
-2
View File
@@ -35,11 +35,9 @@ properties:
maxItems: 1
ovdd-supply:
maxItems: 1
description: I/O voltage
pwr18-supply:
maxItems: 1
description: core voltage
interrupts:
Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml
+1 -2
View File
@@ -79,8 +79,7 @@ properties:
The GPIO used to control the power down line of this device.
maxItems: 1
power-supply:
maxItems: 1
power-supply: true
required:
- compatible
Documentation/devicetree/bindings/display/bridge/ps8640.yaml
-2
View File
@@ -35,11 +35,9 @@ properties:
description: GPIO connected to active low reset.
vdd12-supply:
maxItems: 1
description: Regulator for 1.2V digital core power.
vdd33-supply:
maxItems: 1
description: Regulator for 3.3V digital core power.
ports:
Documentation/devicetree/bindings/display/bridge/simple-bridge.yaml
-1
View File
@@ -60,7 +60,6 @@ properties:
description: GPIO controlling bridge enable
vdd-supply:
maxItems: 1
description: Power supply for the bridge
required:
Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.yaml
-1
View File
@@ -74,7 +74,6 @@ properties:
description: Power down GPIO signal, pin name "/PDWN", active low.
vcc-supply:
maxItems: 1
description:
Power supply for the TTL output, TTL CLOCKOUT signal, LVDS input, PLL and
digital circuitry.
Documentation/devicetree/bindings/display/bridge/toshiba,tc358775.yaml
-2
View File
@@ -28,11 +28,9 @@ properties:
description: i2c address of the bridge, 0x0f
vdd-supply:
maxItems: 1
description: 1.2V LVDS Power Supply
vddio-supply:
maxItems: 1
description: 1.8V IO Power Supply
stby-gpios:
Documentation/devicetree/bindings/display/intel,keembay-msscam.yaml
+2 -2
View File
@@ -18,8 +18,8 @@ description: |
properties:
compatible:
items:
- const: intel,keembay-msscam
- const: syscon
- const: intel,keembay-msscam
- const: syscon
reg:
maxItems: 1
Documentation/devicetree/bindings/display/panel/abt,y030xx067a.yaml
+1 -1
View File
@@ -32,7 +32,7 @@ required:
- power-supply
- reset-gpios
additionalProperties: false
unevaluatedProperties: false
examples:
- |
Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml
+1 -1
View File
@@ -22,7 +22,7 @@ properties:
compatible:
items:
- enum:
- tianma,fhd-video
- tianma,fhd-video
- const: novatek,nt36672a
description: This indicates the panel manufacturer of the panel that is
in turn using the NT36672A panel driver. This compatible string
Documentation/devicetree/bindings/display/xlnx/xlnx,zynqmp-dpsub.yaml
-1
View File
@@ -98,7 +98,6 @@ properties:
maxItems: 1
dmas:
maxItems: 4
items:
- description: Video layer, plane 0 (RGB or luma)
- description: Video layer, plane 1 (U/V or U)
Documentation/devicetree/bindings/dma/dma-common.yaml
+2 -2
View File
@@ -38,12 +38,12 @@ properties:
maxItems: 255
dma-channels:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Number of DMA channels supported by the controller.
dma-requests:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Number of DMA request signals supported by the controller.
Documentation/devicetree/bindings/dma/dma-router.yaml
+1 -1
View File
@@ -23,7 +23,7 @@ properties:
pattern: "^dma-router(@.*)?$"
dma-masters:
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
description:
Array of phandles to the DMA controllers the router can direct
the signal to.
Documentation/devicetree/bindings/dma/ingenic,dma.yaml
+1 -1
View File
@@ -48,7 +48,7 @@ properties:
ingenic,reserved-channels property.
ingenic,reserved-channels:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: >
Bitmask of channels to reserve for devices that need a specific
channel. These channels will only be assigned when explicitely
Documentation/devicetree/bindings/dma/renesas,rcar-dmac.yaml
-1
View File
@@ -73,7 +73,6 @@ properties:
maxItems: 1
clock-names:
maxItems: 1
items:
- const: fck
Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml
+5 -5
View File
@@ -54,7 +54,7 @@ properties:
maximum: 16
dma-masters:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Number of DMA masters supported by the controller. In case if
not specified the driver will try to auto-detect this and
@@ -63,7 +63,7 @@ properties:
maximum: 4
chan_allocation_order:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
DMA channels allocation order specifier. Zero means ascending order
(first free allocated), while one - descending (last free allocated).
@@ -71,7 +71,7 @@ properties:
enum: [0, 1]
chan_priority:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
DMA channels priority order. Zero means ascending channels priority
so the very first channel has the highest priority. While 1 means
@@ -80,7 +80,7 @@ properties:
enum: [0, 1]
block_size:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: Maximum block size supported by the DMA controller.
enum: [3, 7, 15, 31, 63, 127, 255, 511, 1023, 2047, 4095]
@@ -139,7 +139,7 @@ properties:
default: 256
snps,dma-protection-control:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Bits one-to-one passed to the AHB HPROT[3:1] bus. Each bit setting
indicates the following features: bit 0 - privileged mode,
Documentation/devicetree/bindings/eeprom/at24.yaml
+2 -2
View File
@@ -131,7 +131,7 @@ properties:
default: 1
read-only:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Disables writes to the eeprom.
@@ -141,7 +141,7 @@ properties:
Total eeprom size in bytes.
no-read-rollover:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Indicates that the multi-address eeprom does not automatically roll
over reads to the next slave address. Please consult the manual of
Documentation/devicetree/bindings/eeprom/at25.yaml
+2 -2
View File
@@ -45,13 +45,13 @@ properties:
spi-max-frequency: true
pagesize:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [1, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072]
description:
Size of the eeprom page.
size:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Total eeprom size in bytes.
Documentation/devicetree/bindings/hwmon/moortec,mr75203.yaml
+1 -1
View File
@@ -32,7 +32,7 @@ properties:
PVT controller has 5 VM (voltage monitor) sensors.
vm-map defines CPU core to VM instance mapping. A
value of 0xff means that VM sensor is unused.
$ref: /schemas/types.yaml#definitions/uint8-array
$ref: /schemas/types.yaml#/definitions/uint8-array
maxItems: 5
clocks:
Documentation/devicetree/bindings/hwmon/sensirion,shtc1.yaml
+2 -2
View File
@@ -29,12 +29,12 @@ properties:
const: 0x70
sensirion,blocking-io:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
If set, the driver hold the i2c bus until measurement is finished.
sensirion,low-precision:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
If set, the sensor aquire data with low precision (not recommended).
The driver aquire data with high precision by default.
Documentation/devicetree/bindings/hwmon/ti,tmp513.yaml
+1 -1
View File
@@ -61,7 +61,7 @@ properties:
Array of three(TMP513) or two(TMP512) n-Factor value for each remote
temperature channel.
See datasheet Table 11 for n-Factor range list and value interpretation.
$ref: /schemas/types.yaml#definitions/uint32-array
$ref: /schemas/types.yaml#/definitions/uint32-array
minItems: 2
maxItems: 3
items:
Documentation/devicetree/bindings/iio/adc/lltc,ltc2496.yaml
+1 -2
View File
@@ -17,8 +17,7 @@ properties:
- lltc,ltc2496
vref-supply:
description: phandle to an external regulator providing the reference voltage
$ref: /schemas/types.yaml#/definitions/phandle
description: Power supply for the reference voltage
reg:
description: spi chipselect number according to the usual spi bindings
Documentation/devicetree/bindings/iio/humidity/ti,hdc2010.yaml
+1 -2
View File
@@ -22,8 +22,7 @@ properties:
- ti,hdc2010
- ti,hdc2080
vdd-supply:
maxItems: 1
vdd-supply: true
reg:
maxItems: 1
Documentation/devicetree/bindings/iio/light/upisemi,us5182.yaml
+1 -1
View File
@@ -45,7 +45,7 @@ properties:
default: 0x16
upisemi,continuous:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description: |
This chip has two power modes: one-shot (chip takes one measurement and
then shuts itself down) and continuous (chip takes continuous
Documentation/devicetree/bindings/iio/proximity/semtech,sx9310.yaml
+3 -3
View File
@@ -72,7 +72,7 @@ properties:
- finest
semtech,startup-sensor:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [0, 1, 2, 3]
default: 0
description:
@@ -81,7 +81,7 @@ properties:
compensation.
semtech,proxraw-strength:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [0, 2, 4, 8]
default: 2
description:
@@ -89,7 +89,7 @@ properties:
represent 1-1/N.
semtech,avg-pos-strength:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [0, 16, 64, 128, 256, 512, 1024, 4294967295]
default: 16
description:
Documentation/devicetree/bindings/input/fsl,mpr121-touchkey.yaml
+1 -2
View File
@@ -31,8 +31,7 @@ properties:
interrupts:
maxItems: 1
vdd-supply:
maxItems: 1
vdd-supply: true
linux,keycodes:
minItems: 1
Documentation/devicetree/bindings/input/gpio-keys.yaml
+6 -6
View File
@@ -34,13 +34,13 @@ patternProperties:
linux,code:
description: Key / Axis code to emit.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
linux,input-type:
description:
Specify event type this button/key generates. If not specified defaults to
<1> == EV_KEY.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
default: 1
@@ -56,12 +56,12 @@ patternProperties:
linux,input-value = <0xffffffff>; /* -1 */
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
debounce-interval:
description:
Debouncing interval time in milliseconds. If not specified defaults to 5.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
default: 5
@@ -79,7 +79,7 @@ patternProperties:
EV_ACT_ANY - both asserted and deasserted
EV_ACT_ASSERTED - asserted
EV_ACT_DEASSERTED - deasserted
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [0, 1, 2]
linux,can-disable:
@@ -118,7 +118,7 @@ then:
poll-interval:
description:
Poll interval time in milliseconds
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
required:
- poll-interval
Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml
+1 -2
View File
@@ -55,8 +55,7 @@ properties:
wakeup-source: true
vcc-supply:
maxItems: 1
vcc-supply: true
gain:
description: Allows setting the sensitivity in the range from 0 to 31.
Documentation/devicetree/bindings/interrupt-controller/mti,gic.yaml
+2 -2
View File
@@ -42,7 +42,7 @@ properties:
Specifies the list of CPU interrupt vectors to which the GIC may not
route interrupts. This property is ignored if the CPU is started in EIC
mode.
$ref: /schemas/types.yaml#definitions/uint32-array
$ref: /schemas/types.yaml#/definitions/uint32-array
minItems: 1
maxItems: 6
uniqueItems: true
@@ -56,7 +56,7 @@ properties:
It accepts two values: the 1st is the starting interrupt and the 2nd is
the size of the reserved range. If not specified, the driver will
allocate the last (2 * number of VPEs in the system).
$ref: /schemas/types.yaml#definitions/uint32-array
$ref: /schemas/types.yaml#/definitions/uint32-array
items:
- minimum: 0
maximum: 254
Documentation/devicetree/bindings/interrupt-controller/ti,pruss-intc.yaml
+1 -1
View File
@@ -80,7 +80,7 @@ properties:
mapping is provided.
ti,irqs-reserved:
$ref: /schemas/types.yaml#definitions/uint8
$ref: /schemas/types.yaml#/definitions/uint8
description: |
Bitmask of host interrupts between 0 and 7 (corresponding to PRUSS INTC
output interrupts 2 through 9) that are not connected to the Arm interrupt
Documentation/devicetree/bindings/interrupt-controller/ti,sci-inta.yaml
+1 -1
View File
@@ -76,7 +76,7 @@ properties:
"limit" specifies the limit for translation
ti,unmapped-event-sources:
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
description:
Array of phandles to DMA controllers where the unmapped events originate.
Documentation/devicetree/bindings/leds/backlight/common.yaml
+2 -2
View File
@@ -22,7 +22,7 @@ properties:
The default brightness that should be applied to the LED by the operating
system on start-up. The brightness should not exceed the brightness the
LED can provide.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
max-brightness:
description:
@@ -31,6 +31,6 @@ properties:
on the brightness apart from what the driver says, as it could happen
that a LED can be made so bright that it gets damaged or causes damage
due to restrictions in a specific system, such as mounting conditions.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
additionalProperties: true
Documentation/devicetree/bindings/leds/common.yaml
+8 -8
View File
@@ -27,21 +27,21 @@ properties:
List of device current outputs the LED is connected to. The outputs are
identified by the numbers that must be defined in the LED device binding
documentation.
$ref: /schemas/types.yaml#definitions/uint32-array
$ref: /schemas/types.yaml#/definitions/uint32-array
function:
description:
LED function. Use one of the LED_FUNCTION_* prefixed definitions
from the header include/dt-bindings/leds/common.h. If there is no
matching LED_FUNCTION available, add a new one.
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
color:
description:
Color of the LED. Use one of the LED_COLOR_ID_* prefixed definitions from
the header include/dt-bindings/leds/common.h. If there is no matching
LED_COLOR_ID available, add a new one.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
minimum: 0
maximum: 9
@@ -49,7 +49,7 @@ properties:
description:
Integer to be used when more than one instance of the same function is
needed, differing only with an ordinal number.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
label:
description:
@@ -66,7 +66,7 @@ properties:
produced where the LED momentarily turns off (or on). The "keep" setting
will keep the LED at whatever its current state is, without producing a
glitch.
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
enum:
- on
- off
@@ -77,7 +77,7 @@ properties:
description:
This parameter, if present, is a string defining the trigger assigned to
the LED.
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
enum:
# LED will act as a back-light, controlled by the framebuffer system
@@ -109,7 +109,7 @@ properties:
brightness and duration (in ms). The exact format is
described in:
Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt
$ref: /schemas/types.yaml#definitions/uint32-matrix
$ref: /schemas/types.yaml#/definitions/uint32-matrix
items:
minItems: 2
maxItems: 2
@@ -143,7 +143,7 @@ properties:
the device tree and be referenced by a phandle and a set of phandle
arguments. A length of arguments should be specified by the
#trigger-source-cells property in the source node.
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
# Required properties for flash LED child nodes:
flash-max-microamp:
Documentation/devicetree/bindings/leds/leds-lp55xx.yaml
+5 -5
View File
@@ -35,7 +35,7 @@ properties:
description: I2C slave address
clock-mode:
$ref: /schemas/types.yaml#definitions/uint8
$ref: /schemas/types.yaml#/definitions/uint8
description: |
Input clock mode
enum:
@@ -49,7 +49,7 @@ properties:
GPIO attached to the chip's enable pin
pwr-sel:
$ref: /schemas/types.yaml#definitions/uint8
$ref: /schemas/types.yaml#/definitions/uint8
description: |
LP8501 specific property. Power selection for output channels.
enum:
@@ -70,14 +70,14 @@ patternProperties:
$ref: common.yaml#
properties:
led-cur:
$ref: /schemas/types.yaml#definitions/uint8
$ref: /schemas/types.yaml#/definitions/uint8
description: |
Current setting at each LED channel (mA x10, 0 if LED is not connected)
minimum: 0
maximum: 255
max-cur:
$ref: /schemas/types.yaml#definitions/uint8
$ref: /schemas/types.yaml#/definitions/uint8
description: Maximun current at each LED channel.
reg:
@@ -97,7 +97,7 @@ patternProperties:
- 8 # LED output D9
chan-name:
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
description: name of channel
required:
Documentation/devicetree/bindings/mailbox/arm,mhu.yaml
-1
View File
@@ -61,7 +61,6 @@ properties:
- description: low-priority non-secure
- description: high-priority non-secure
- description: Secure
maxItems: 3
clocks:
maxItems: 1
Documentation/devicetree/bindings/media/coda.yaml
+21 -21
View File
@@ -44,6 +44,21 @@ properties:
- const: per
- const: ahb
interrupts:
minItems: 1
items:
- description: BIT processor interrupt
- description: JPEG unit interrupt
interrupt-names:
minItems: 1
items:
- const: bit
- const: jpeg
power-domains:
maxItems: 1
resets:
maxItems: 1
@@ -59,6 +74,8 @@ required:
- clocks
- clock-names
additionalProperties: false
allOf:
- if:
properties:
@@ -68,34 +85,17 @@ allOf:
then:
properties:
interrupts:
items:
- description: BIT processor interrupt
- description: JPEG unit interrupt
minItems: 2
interrupt-names:
items:
- const: bit
- const: jpeg
minItems: 2
else:
properties:
interrupts:
items:
- description: BIT processor interrupt
- if:
properties:
compatible:
contains:
enum:
- fsl,imx6dl-vpu
- fsl,imx6q-vpu
then:
properties:
power-domains:
$ref: /schemas/types.yaml#/definitions/phandle
description: phandle pointing to the PU power domain
maxItems: 1
power-domains: false
examples:
- |
vpu: video-codec@63ff4000 {
Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
-1
View File
@@ -40,7 +40,6 @@ properties:
poc-supply:
description: Regulator providing Power over Coax to the cameras
maxItems: 1
enable-gpios:
description: GPIO connected to the \#PWDN pin with inverted polarity
Documentation/devicetree/bindings/media/i2c/mipi-ccs.yaml
+6 -8
View File
@@ -1,6 +1,7 @@
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
# Copyright (C) 2014--2020 Intel Corporation
%YAML 1.2
---
$id: http://devicetree.org/schemas/media/i2c/mipi-ccs.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
@@ -26,11 +27,11 @@ properties:
compatible:
oneOf:
- items:
- const: mipi-ccs-1.1
- const: mipi-ccs
- const: mipi-ccs-1.1
- const: mipi-ccs
- items:
- const: mipi-ccs-1.0
- const: mipi-ccs
- const: mipi-ccs-1.0
- const: mipi-ccs
- const: nokia,smia
reg:
@@ -38,15 +39,12 @@ properties:
vana-supply:
description: Analogue voltage supply (VANA), sensor dependent.
maxItems: 1
vcore-supply:
description: Core voltage supply (VCore), sensor dependent.
maxItems: 1
vio-supply:
description: I/O voltage supply (VIO), sensor dependent.
maxItems: 1
clocks:
description: External clock to the sensor.
Documentation/devicetree/bindings/media/i2c/sony,imx214.yaml
-3
View File
@@ -37,15 +37,12 @@ properties:
vdddo-supply:
description: Chip digital IO regulator (1.8V).
maxItems: 1
vdda-supply:
description: Chip analog regulator (2.7V).
maxItems: 1
vddd-supply:
description: Chip digital core regulator (1.12V).
maxItems: 1
flash-leds:
description: See ../video-interfaces.txt
Documentation/devicetree/bindings/media/i2c/sony,imx274.yaml
-3
View File
@@ -33,15 +33,12 @@ properties:
vana-supply:
description: Sensor 2.8 V analog supply.
maxItems: 1
vdig-supply:
description: Sensor 1.8 V digital core supply.
maxItems: 1
vddl-supply:
description: Sensor digital IO 1.2 V supply.
maxItems: 1
port:
type: object
Documentation/devicetree/bindings/mfd/st,stmfx.yaml
+1 -2
View File
@@ -26,8 +26,7 @@ properties:
drive-open-drain: true
vdd-supply:
maxItems: 1
vdd-supply: true
pinctrl:
type: object
Documentation/devicetree/bindings/net/allwinner,sun8i-a83t-emac.yaml
+3 -3
View File
@@ -38,7 +38,7 @@ properties:
const: stmmaceth
syscon:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Phandle to the device containing the EMAC or GMAC clock
register
@@ -114,7 +114,7 @@ allOf:
then:
properties:
allwinner,leds-active-low:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
EPHY LEDs are active low.
@@ -126,7 +126,7 @@ allOf:
const: allwinner,sun8i-h3-mdio-mux
mdio-parent-bus:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Phandle to EMAC MDIO.
Documentation/devicetree/bindings/net/amlogic,meson-dwmac.yaml
+1 -1
View File
@@ -60,7 +60,7 @@ allOf:
- const: timing-adjustment
amlogic,tx-delay-ns:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
The internal RGMII TX clock delay (provided by this driver) in
nanoseconds. Allowed values are 0ns, 2ns, 4ns, 6ns.
Documentation/devicetree/bindings/net/dsa/dsa.yaml
+3 -3
View File
@@ -54,7 +54,7 @@ patternProperties:
description:
Describes the label associated with this port, which will become
the netdev name
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
link:
description:
@@ -62,13 +62,13 @@ patternProperties:
port is used as the outgoing port towards the phandle ports. The
full routing information must be given, not just the one hop
routes to neighbouring switches
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
ethernet:
description:
Should be a phandle to a valid Ethernet device node. This host
device is what the switch port is connected to
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
phy-handle: true
Documentation/devicetree/bindings/net/ethernet-controller.yaml
+12 -12
View File
@@ -16,7 +16,7 @@ properties:
local-mac-address:
description:
Specifies the MAC address that was assigned to the network device.
$ref: /schemas/types.yaml#definitions/uint8-array
$ref: /schemas/types.yaml#/definitions/uint8-array
items:
- minItems: 6
maxItems: 6
@@ -27,20 +27,20 @@ properties:
program; should be used in cases where the MAC address assigned
to the device by the boot program is different from the
local-mac-address property.
$ref: /schemas/types.yaml#definitions/uint8-array
$ref: /schemas/types.yaml#/definitions/uint8-array
items:
- minItems: 6
maxItems: 6
max-frame-size:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Maximum transfer unit (IEEE defined MTU), rather than the
maximum frame size (there\'s contradiction in the Devicetree
Specification).
max-speed:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Specifies maximum speed in Mbit/s supported by the device.
@@ -101,7 +101,7 @@ properties:
$ref: "#/properties/phy-connection-type"
phy-handle:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Specifies a reference to a node representing a PHY device.
@@ -114,7 +114,7 @@ properties:
deprecated: true
rx-fifo-depth:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
The size of the controller\'s receive fifo in bytes. This is used
for components that can have configurable receive fifo sizes,
@@ -129,12 +129,12 @@ properties:
If this property is present then the MAC applies the RX delay.
sfp:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Specifies a reference to a node representing a SFP cage.
tx-fifo-depth:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
The size of the controller\'s transmit fifo in bytes. This
is used for components that can have configurable fifo sizes.
@@ -150,7 +150,7 @@ properties:
description:
Specifies the PHY management type. If auto is set and fixed-link
is not specified, it uses MDIO for management.
$ref: /schemas/types.yaml#definitions/string
$ref: /schemas/types.yaml#/definitions/string
default: auto
enum:
- auto
@@ -198,17 +198,17 @@ properties:
speed:
description:
Link speed.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [10, 100, 1000]
full-duplex:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Indicates that full-duplex is used. When absent, half
duplex is assumed.
asym-pause:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Indicates that asym_pause should be enabled.
Documentation/devicetree/bindings/net/ethernet-phy.yaml
+10 -10
View File
@@ -78,57 +78,57 @@ properties:
Maximum PHY supported speed in Mbits / seconds.
broken-turn-around:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
If set, indicates the PHY device does not correctly release
the turn around line low at end of the control phase of the
MDIO transaction.
enet-phy-lane-swap:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
If set, indicates the PHY will swap the TX/RX lanes to
compensate for the board being designed with the lanes
swapped.
eee-broken-100tx:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Mark the corresponding energy efficient ethernet mode as
broken and request the ethernet to stop advertising it.
eee-broken-1000t:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Mark the corresponding energy efficient ethernet mode as
broken and request the ethernet to stop advertising it.
eee-broken-10gt:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Mark the corresponding energy efficient ethernet mode as
broken and request the ethernet to stop advertising it.
eee-broken-1000kx:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Mark the corresponding energy efficient ethernet mode as
broken and request the ethernet to stop advertising it.
eee-broken-10gkx4:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Mark the corresponding energy efficient ethernet mode as
broken and request the ethernet to stop advertising it.
eee-broken-10gkr:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Mark the corresponding energy efficient ethernet mode as
broken and request the ethernet to stop advertising it.
phy-is-integrated:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
If set, indicates that the PHY is integrated into the same
physical package as the Ethernet MAC. If needed, muxers
@@ -158,7 +158,7 @@ properties:
this property is missing the delay will be skipped.
sfp:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Specifies a reference to a node representing a SFP cage.
Documentation/devicetree/bindings/net/fsl,qoriq-mc-dpmac.yaml
+1 -1
View File
@@ -31,7 +31,7 @@ properties:
phy-mode: true
pcs-handle:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
A reference to a node representing a PCS PHY device found on
the internal MDIO bus.
Documentation/devicetree/bindings/net/mdio.yaml
+1 -1
View File
@@ -70,7 +70,7 @@ patternProperties:
The ID number for the device.
broken-turn-around:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
If set, indicates the MDIO device does not correctly release
the turn around line low at end of the control phase of the
Documentation/devicetree/bindings/net/mediatek,star-emac.yaml
+1 -1
View File
@@ -42,7 +42,7 @@ properties:
- const: trans
mediatek,pericfg:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Phandle to the device containing the PERICFG register range. This is used
to control the MII mode.
Documentation/devicetree/bindings/net/qcom,ipa.yaml
+1 -2
View File
@@ -114,14 +114,13 @@ properties:
validating firwmare used by the GSI.
modem-remoteproc:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
This defines the phandle to the remoteproc node representing
the modem subsystem. This is requied so the IPA driver can
receive and act on notifications of modem up/down events.
memory-region:
$ref: /schemas/types.yaml#/definitions/phandle-array
maxItems: 1
description:
If present, a phandle for a reserved memory area that holds
Documentation/devicetree/bindings/net/snps,dwmac.yaml
+19 -19
View File
@@ -126,7 +126,7 @@ properties:
in a different mode than the PHY in order to function.
snps,axi-config:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
AXI BUS Mode parameters. Phandle to a node that can contain the
following properties
@@ -141,7 +141,7 @@ properties:
* snps,rb, rebuild INCRx Burst
snps,mtl-rx-config:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Multiple RX Queues parameters. Phandle to a node that can
contain the following properties
@@ -164,7 +164,7 @@ properties:
* snps,priority, RX queue priority (Range 0x0 to 0xF)
snps,mtl-tx-config:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Multiple TX Queues parameters. Phandle to a node that can
contain the following properties
@@ -198,7 +198,7 @@ properties:
snps,reset-active-low:
deprecated: true
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Indicates that the PHY Reset is active low
@@ -208,55 +208,55 @@ properties:
Triplet of delays. The 1st cell is reset pre-delay in micro
seconds. The 2nd cell is reset pulse in micro seconds. The 3rd
cell is reset post-delay in micro seconds.
$ref: /schemas/types.yaml#definitions/uint32-array
$ref: /schemas/types.yaml#/definitions/uint32-array
minItems: 3
maxItems: 3
snps,aal:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Use Address-Aligned Beats
snps,fixed-burst:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Program the DMA to use the fixed burst mode
snps,mixed-burst:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Program the DMA to use the mixed burst mode
snps,force_thresh_dma_mode:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Force DMA to use the threshold mode for both tx and rx
snps,force_sf_dma_mode:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Force DMA to use the Store and Forward mode for both tx and
rx. This flag is ignored if force_thresh_dma_mode is set.
snps,en-tx-lpi-clockgating:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Enable gating of the MAC TX clock during TX low-power mode
snps,multicast-filter-bins:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Number of multicast filter hash bins supported by this device
instance
snps,perfect-filter-entries:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Number of perfect filter entries supported by this device
instance
snps,ps-speed:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description:
Port selection speed that can be passed to the core when PCS
is supported. For example, this is used in case of SGMII and
@@ -307,25 +307,25 @@ allOf:
snps,pbl:
description:
Programmable Burst Length (tx and rx)
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [2, 4, 8]
snps,txpbl:
description:
Tx Programmable Burst Length. If set, DMA tx will use this
value rather than snps,pbl.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [2, 4, 8]
snps,rxpbl:
description:
Rx Programmable Burst Length. If set, DMA rx will use this
value rather than snps,pbl.
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
enum: [2, 4, 8]
snps,no-pbl-x8:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Don\'t multiply the pbl/txpbl/rxpbl values by 8. For core
rev < 3.50, don\'t multiply the values by 4.
@@ -351,7 +351,7 @@ allOf:
then:
properties:
snps,tso:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Enables the TSO feature otherwise it will be managed by
MAC HW capability register.
Documentation/devicetree/bindings/net/socionext,uniphier-ave4.yaml
+1 -1
View File
@@ -64,7 +64,7 @@ properties:
- const: ether # for others
socionext,syscon-phy-mode:
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
description:
A phandle to syscon with one argument that configures phy mode.
The argument is the ID of MAC instance.
Documentation/devicetree/bindings/net/ti,cpsw-switch.yaml
+1 -1
View File
@@ -70,7 +70,7 @@ properties:
pinctrl-names: true
syscon:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
Phandle to the system control device node which provides access to
efuse IO range with MAC addresses
Documentation/devicetree/bindings/net/ti,dp83867.yaml
+6 -6
View File
@@ -47,31 +47,31 @@ properties:
takes precedence.
tx-fifo-depth:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Transmitt FIFO depth see dt-bindings/net/ti-dp83867.h for values
rx-fifo-depth:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Receive FIFO depth see dt-bindings/net/ti-dp83867.h for values
ti,clk-output-sel:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Muxing option for CLK_OUT pin. See dt-bindings/net/ti-dp83867.h
for applicable values. The CLK_OUT pin can also be disabled by this
property. When omitted, the PHY's default will be left as is.
ti,rx-internal-delay:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
RGMII Receive Clock Delay - see dt-bindings/net/ti-dp83867.h
for applicable values. Required only if interface type is
PHY_INTERFACE_MODE_RGMII_ID or PHY_INTERFACE_MODE_RGMII_RXID.
ti,tx-internal-delay:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
RGMII Transmit Clock Delay - see dt-bindings/net/ti-dp83867.h
for applicable values. Required only if interface type is
@@ -101,7 +101,7 @@ properties:
ti,fifo-depth:
deprecated: true
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Transmitt FIFO depth- see dt-bindings/net/ti-dp83867.h for applicable
values.
Documentation/devicetree/bindings/net/ti,dp83869.yaml
+4 -4
View File
@@ -44,22 +44,22 @@ properties:
to a maximum value (70 ohms).
tx-fifo-depth:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Transmitt FIFO depth see dt-bindings/net/ti-dp83869.h for values
rx-fifo-depth:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Receive FIFO depth see dt-bindings/net/ti-dp83869.h for values
ti,clk-output-sel:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Muxing option for CLK_OUT pin see dt-bindings/net/ti-dp83869.h for values.
ti,op-mode:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Operational mode for the PHY. If this is not set then the operational
mode is set by the straps. see dt-bindings/net/ti-dp83869.h for values
Documentation/devicetree/bindings/net/ti,k3-am654-cpsw-nuss.yaml
+2 -2
View File
@@ -119,12 +119,12 @@ properties:
description: label associated with this port
ti,mac-only:
$ref: /schemas/types.yaml#definitions/flag
$ref: /schemas/types.yaml#/definitions/flag
description:
Specifies the port works in mac-only mode.
ti,syscon-efuse:
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
description:
Phandle to the system control device node which provides access
to efuse IO range with MAC addresses
Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
+1 -1
View File
@@ -136,7 +136,7 @@ properties:
- const: tcl2host-status-ring
qcom,rproc:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
DT entry of q6v5-wcss remoteproc driver.
Phandle to a node that can contain the following properties
Documentation/devicetree/bindings/phy/ti,omap-usb2.yaml
+2 -2
View File
@@ -44,13 +44,13 @@ properties:
- const: refclk
syscon-phy-power:
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
description:
phandle/offset pair. Phandle to the system control module and
register offset to power on/off the PHY.
ctrl-module:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description:
(deprecated) phandle of the control module used by PHY driver
to power on the PHY. Use syscon-phy-power instead.
Documentation/devicetree/bindings/power/mediatek,power-controller.yaml
+6 -6
View File
@@ -83,11 +83,11 @@ patternProperties:
SUSBSYS clocks.
mediatek,infracfg:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description: phandle to the device containing the INFRACFG register range.
mediatek,smi:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description: phandle to the device containing the SMI register range.
patternProperties:
@@ -131,11 +131,11 @@ patternProperties:
SUSBSYS clocks.
mediatek,infracfg:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description: phandle to the device containing the INFRACFG register range.
mediatek,smi:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description: phandle to the device containing the SMI register range.
patternProperties:
@@ -179,11 +179,11 @@ patternProperties:
SUSBSYS clocks.
mediatek,infracfg:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description: phandle to the device containing the INFRACFG register range.
mediatek,smi:
$ref: /schemas/types.yaml#definitions/phandle
$ref: /schemas/types.yaml#/definitions/phandle
description: phandle to the device containing the SMI register range.
required:
Documentation/devicetree/bindings/power/supply/cw2015_battery.yaml
+1 -1
View File
@@ -27,7 +27,7 @@ properties:
of this binary blob is kept secret by CellWise. The only way to obtain
it is to mail two batteries to a test facility of CellWise and receive
back a test report with the binary blob.
$ref: /schemas/types.yaml#definitions/uint8-array
$ref: /schemas/types.yaml#/definitions/uint8-array
minItems: 64
maxItems: 64
Documentation/devicetree/bindings/powerpc/sleep.yaml
+1 -1
View File
@@ -42,6 +42,6 @@ select: true
properties:
sleep:
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
additionalProperties: true
Documentation/devicetree/bindings/regulator/anatop-regulator.yaml
-1
View File
@@ -59,7 +59,6 @@ properties:
description: u32 value representing regulator enable bit offset.
vin-supply:
$ref: '/schemas/types.yaml#/definitions/phandle'
description: input supply phandle.
required:
Documentation/devicetree/bindings/serial/8250.yaml
+3 -3
View File
@@ -126,7 +126,7 @@ properties:
maxItems: 1
current-speed:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: The current active speed of the UART.
reg-offset:
@@ -154,7 +154,7 @@ properties:
Set to indicate that the port does not implement loopback test mode.
fifo-size:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: The fifo size of the UART.
auto-flow-control:
@@ -165,7 +165,7 @@ properties:
property.
tx-threshold:
$ref: /schemas/types.yaml#definitions/uint32
$ref: /schemas/types.yaml#/definitions/uint32
description: |
Specify the TX FIFO low water indication for parts with programmable
TX FIFO thresholds.
Documentation/devicetree/bindings/serial/litex,liteuart.yaml
+2
View File
@@ -29,6 +29,8 @@ required:
- compatible
- reg
additionalProperties: false
examples:
- |
uart0: serial@e0001800 {
Documentation/devicetree/bindings/soc/litex/litex,soc-controller.yaml
+2
View File
@@ -28,6 +28,8 @@ required:
- compatible
- reg
additionalProperties: false
examples:
- |
soc_ctrl0: soc-controller@f0000000 {
Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
+2
View File
@@ -44,6 +44,8 @@ required:
- clocks
- clock-names
additionalProperties: false
examples:
- |
#include <dt-bindings/interrupt-controller/arm-gic.h>
Documentation/devicetree/bindings/soc/ti/k3-ringacc.yaml
+1 -1
View File
@@ -55,7 +55,7 @@ properties:
description: TI-SCI RM subtype for GP ring range
ti,sci:
$ref: /schemas/types.yaml#definitions/phandle-array
$ref: /schemas/types.yaml#/definitions/phandle-array
description: phandle on TI-SCI compatible System controller node
ti,sci-dev-id:
Documentation/devicetree/bindings/soc/xilinx/xlnx,vcu-settings.yaml
+12 -3
View File
@@ -26,9 +26,18 @@ required:
- compatible
- reg
additionalProperties: false
examples:
- |
xlnx_vcu: vcu@a0041000 {
compatible = "xlnx,vcu-settings", "syscon";
reg = <0x0 0xa0041000 0x0 0x1000>;
fpga {
#address-cells = <2>;
#size-cells = <2>;
xlnx_vcu: vcu@a0041000 {
compatible = "xlnx,vcu-settings", "syscon";
reg = <0x0 0xa0041000 0x0 0x1000>;
};
};
...
Documentation/devicetree/bindings/sound/allwinner,sun4i-a10-codec.yaml
+1 -1
View File
@@ -57,7 +57,7 @@ properties:
A list of the connections between audio components. Each entry
is a pair of strings, the first being the connection's sink, the
second being the connection's source.
$ref: /schemas/types.yaml#definitions/non-unique-string-array
$ref: /schemas/types.yaml#/definitions/non-unique-string-array
minItems: 2
maxItems: 18
items:
Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml
-2
View File
@@ -44,7 +44,6 @@ properties:
maxItems: 3
clock-names:
maxItems: 3
items:
- const: hda
- const: hda2hdmi
@@ -54,7 +53,6 @@ properties:
maxItems: 3
reset-names:
maxItems: 3
items:
- const: hda
- const: hda2hdmi
Documentation/devicetree/bindings/sound/st,stm32-sai.yaml
+2 -2
View File
@@ -106,7 +106,7 @@ patternProperties:
Must contain the phandle and index of the SAI sub-block providing
the synchronization.
allOf:
- $ref: /schemas/types.yaml#definitions/phandle-array
- $ref: /schemas/types.yaml#/definitions/phandle-array
- maxItems: 1
st,iec60958:
@@ -117,7 +117,7 @@ patternProperties:
configured according to protocol defined in related DAI link node,
such as i2s, left justified, right justified, dsp and pdm protocols.
allOf:
- $ref: /schemas/types.yaml#definitions/flag
- $ref: /schemas/types.yaml#/definitions/flag
"#clock-cells":
description: Configure the SAI device as master clock provider.
Documentation/devicetree/bindings/usb/renesas,usb-xhci.yaml
-1
View File
@@ -51,7 +51,6 @@ properties:
maxItems: 1
phy-names:
maxItems: 1
items:
- const: usb
Documentation/devicetree/bindings/usb/renesas,usbhs.yaml
-3
View File
@@ -74,11 +74,8 @@ properties:
phys:
maxItems: 1
items:
- description: phandle + phy specifier pair.
phy-names:
maxItems: 1
items:
- const: usb
Documentation/devicetree/bindings/watchdog/allwinner,sun4i-a10-wdt.yaml
+3
View File
@@ -21,6 +21,9 @@ properties:
- items:
- const: allwinner,sun50i-a64-wdt
- const: allwinner,sun6i-a31-wdt
- items:
- const: allwinner,sun50i-a100-wdt
- const: allwinner,sun6i-a31-wdt
- items:
- const: allwinner,sun50i-h6-wdt
- const: allwinner,sun6i-a31-wdt
Documentation/devicetree/bindings/watchdog/snps,dw-wdt.yaml
+9 -1
View File
@@ -14,7 +14,15 @@ maintainers:
properties:
compatible:
const: snps,dw-wdt
oneOf:
- const: snps,dw-wdt
- items:
- enum:
- rockchip,rk3066-wdt
- rockchip,rk3188-wdt
- rockchip,rk3288-wdt
- rockchip,rk3368-wdt
- const: snps,dw-wdt
reg:
maxItems: 1
Documentation/filesystems/ext4/journal.rst
+50
View File
@@ -681,3 +681,53 @@ Here is the list of supported tags and their meanings:
- Stores the TID of the commit, CRC of the fast commit of which this tag
represents the end of
Fast Commit Replay Idempotence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Fast commits tags are idempotent in nature provided the recovery code follows
certain rules. The guiding principle that the commit path follows while
committing is that it stores the result of a particular operation instead of
storing the procedure.
Let's consider this rename operation: 'mv /a /b'. Let's assume dirent '/a'
was associated with inode 10. During fast commit, instead of storing this
operation as a procedure "rename a to b", we store the resulting file system
state as a "series" of outcomes:
- Link dirent b to inode 10
- Unlink dirent a
- Inode 10 with valid refcount
Now when recovery code runs, it needs "enforce" this state on the file
system. This is what guarantees idempotence of fast commit replay.
Let's take an example of a procedure that is not idempotent and see how fast
commits make it idempotent. Consider following sequence of operations:
1) rm A
2) mv B A
3) read A
If we store this sequence of operations as is then the replay is not idempotent.
Let's say while in replay, we crash after (2). During the second replay,
file A (which was actually created as a result of "mv B A" operation) would get
deleted. Thus, file named A would be absent when we try to read A. So, this
sequence of operations is not idempotent. However, as mentioned above, instead
of storing the procedure fast commits store the outcome of each procedure. Thus
the fast commit log for above procedure would be as follows:
(Let's assume dirent A was linked to inode 10 and dirent B was linked to
inode 11 before the replay)
1) Unlink A
2) Link A to inode 11
3) Unlink B
4) Inode 11
If we crash after (3) we will have file A linked to inode 11. During the second
replay, we will remove file A (inode 11). But we will create it back and make
it point to inode 11. We won't find B, so we'll just skip that step. At this
point, the refcount for inode 11 is not reliable, but that gets fixed by the
replay of last inode 11 tag. Thus, by converting a non-idempotent procedure
into a series of idempotent outcomes, fast commits ensured idempotence during
the replay.
Documentation/process/submit-checklist.rst
+12 -12
View File
@@ -75,44 +75,44 @@ and elsewhere regarding submitting Linux kernel patches.
13) Has been build- and runtime tested with and without ``CONFIG_SMP`` and
``CONFIG_PREEMPT.``
16) All codepaths have been exercised with all lockdep features enabled.
14) All codepaths have been exercised with all lockdep features enabled.
17) All new ``/proc`` entries are documented under ``Documentation/``
15) All new ``/proc`` entries are documented under ``Documentation/``
18) All new kernel boot parameters are documented in
16) All new kernel boot parameters are documented in
``Documentation/admin-guide/kernel-parameters.rst``.
19) All new module parameters are documented with ``MODULE_PARM_DESC()``
17) All new module parameters are documented with ``MODULE_PARM_DESC()``
20) All new userspace interfaces are documented in ``Documentation/ABI/``.
18) All new userspace interfaces are documented in ``Documentation/ABI/``.
See ``Documentation/ABI/README`` for more information.
Patches that change userspace interfaces should be CCed to
linux-api@vger.kernel.org.
21) Check that it all passes ``make headers_check``.
19) Check that it all passes ``make headers_check``.
22) Has been checked with injection of at least slab and page-allocation
20) Has been checked with injection of at least slab and page-allocation
failures. See ``Documentation/fault-injection/``.
If the new code is substantial, addition of subsystem-specific fault
injection might be appropriate.
23) Newly-added code has been compiled with ``gcc -W`` (use
21) Newly-added code has been compiled with ``gcc -W`` (use
``make EXTRA_CFLAGS=-W``). This will generate lots of noise, but is good
for finding bugs like "warning: comparison between signed and unsigned".
24) Tested after it has been merged into the -mm patchset to make sure
22) Tested after it has been merged into the -mm patchset to make sure
that it still works with all of the other queued patches and various
changes in the VM, VFS, and other subsystems.
25) All memory barriers {e.g., ``barrier()``, ``rmb()``, ``wmb()``} need a
23) All memory barriers {e.g., ``barrier()``, ``rmb()``, ``wmb()``} need a
comment in the source code that explains the logic of what they are doing
and why.
26) If any ioctl's are added by the patch, then also update
24) If any ioctl's are added by the patch, then also update
``Documentation/userspace-api/ioctl/ioctl-number.rst``.
27) If your modified source code depends on or uses any of the kernel
25) If your modified source code depends on or uses any of the kernel
APIs or features that are related to the following ``Kconfig`` symbols,
then test multiple builds with the related ``Kconfig`` symbols disabled
and/or ``=m`` (if that option is available) [not all of these at the
Documentation/process/submitting-patches.rst
+7 -1
View File
@@ -411,6 +411,12 @@ Some people also put extra tags at the end. They'll just be ignored for
now, but you can do this to mark internal company procedures or just
point out some special detail about the sign-off.
Any further SoBs (Signed-off-by:'s) following the author's SoB are from
people handling and transporting the patch, but were not involved in its
development. SoB chains should reflect the **real** route a patch took
as it was propagated to the maintainers and ultimately to Linus, with
the first SoB entry signalling primary authorship of a single author.
When to use Acked-by:, Cc:, and Co-developed-by:
------------------------------------------------
@@ -446,7 +452,7 @@ patch. This tag documents that potentially interested parties
have been included in the discussion.
Co-developed-by: states that the patch was co-created by multiple developers;
it is a used to give attribution to co-authors (in addition to the author
it is used to give attribution to co-authors (in addition to the author
attributed by the From: tag) when several people work on a single patch. Since
Co-developed-by: denotes authorship, every Co-developed-by: must be immediately
followed by a Signed-off-by: of the associated co-author. Standard sign-off
MAINTAINERS
+3 -2
View File
@@ -3199,6 +3199,7 @@ S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
F: block/
F: drivers/block/
F: fs/block_dev.c
F: include/linux/blk*
F: kernel/trace/blktrace.c
F: lib/sbitmap.c
@@ -4354,8 +4355,8 @@ T: git git://linuxtv.org/media_tree.git
F: drivers/media/pci/cobalt/
COCCINELLE/Semantic Patches (SmPL)
M: Julia Lawall <Julia.Lawall@lip6.fr>
M: Gilles Muller <Gilles.Muller@lip6.fr>
M: Julia Lawall <Julia.Lawall@inria.fr>
M: Gilles Muller <Gilles.Muller@inria.fr>
M: Nicolas Palix <nicolas.palix@imag.fr>
M: Michal Marek <michal.lkml@markovi.net>
L: cocci@systeme.lip6.fr (moderated for non-subscribers)
arch/alpha/kernel/sys_jensen.c
+1 -1
View File
@@ -7,7 +7,7 @@
*
* Code supporting the Jensen.
*/
#include <linux/interrupt.h>
#include <linux/kernel.h>
#include <linux/types.h>
#include <linux/mm.h>
arch/arm/include/asm/efi.h
+11 -13
View File
@@ -66,24 +66,17 @@ static inline void efifb_setup_from_dmi(struct screen_info *si, const char *opt)
#define MAX_UNCOMP_KERNEL_SIZE SZ_32M
/*
* phys-to-virt patching requires that the physical to virtual offset fits
* into the immediate field of an add/sub instruction, which comes down to the
* 24 least significant bits being zero, and so the offset should be a multiple
* of 16 MB. Since PAGE_OFFSET itself is a multiple of 16 MB, the physical
* base should be aligned to 16 MB as well.
* phys-to-virt patching requires that the physical to virtual offset is a
* multiple of 2 MiB. However, using an alignment smaller than TEXT_OFFSET
* here throws off the memory allocation logic, so let's use the lowest power
* of two greater than 2 MiB and greater than TEXT_OFFSET.
*/
#define EFI_PHYS_ALIGN SZ_16M
/* on ARM, the FDT should be located in a lowmem region */
static inline unsigned long efi_get_max_fdt_addr(unsigned long image_addr)
{
return round_down(image_addr, EFI_PHYS_ALIGN) + SZ_512M;
}
#define EFI_PHYS_ALIGN max(UL(SZ_2M), roundup_pow_of_two(TEXT_OFFSET))
/* on ARM, the initrd should be loaded in a lowmem region */
static inline unsigned long efi_get_max_initrd_addr(unsigned long image_addr)
{
return round_down(image_addr, EFI_PHYS_ALIGN) + SZ_512M;
return round_down(image_addr, SZ_4M) + SZ_512M;
}
struct efi_arm_entry_state {
@@ -93,4 +86,9 @@ struct efi_arm_entry_state {
u32 sctlr_after_ebs;
};
static inline void efi_capsule_flush_cache_range(void *addr, int size)
{
__cpuc_flush_dcache_area(addr, size);
}
#endif /* _ASM_ARM_EFI_H */
arch/arm/kernel/smp.c
+1 -1
View File
@@ -553,7 +553,7 @@ void show_ipi_list(struct seq_file *p, int prec)
seq_printf(p, "%*s%u: ", prec - 1, "IPI", i);
for_each_online_cpu(cpu)
seq_printf(p, "%10u ", kstat_irqs_cpu(irq, cpu));
seq_printf(p, "%10u ", irq_desc_kstat_cpu(ipi_desc[i], cpu));
seq_printf(p, " %s\n", ipi_types[i]);
}
arch/arm64/Kconfig
+1
View File
@@ -1876,6 +1876,7 @@ config EFI
select EFI_RUNTIME_WRAPPERS
select EFI_STUB
select EFI_GENERIC_STUB
imply IMA_SECURE_AND_OR_TRUSTED_BOOT
default y
help
This option provides support for runtime services provided
arch/arm64/include/asm/efi.h
+5 -6
View File
@@ -64,12 +64,6 @@ efi_status_t __efi_rt_asm_wrapper(void *, const char *, ...);
#define EFI_KIMG_ALIGN \
(SEGMENT_ALIGN > THREAD_ALIGN ? SEGMENT_ALIGN : THREAD_ALIGN)
/* on arm64, the FDT may be located anywhere in system RAM */
static inline unsigned long efi_get_max_fdt_addr(unsigned long image_addr)
{
return ULONG_MAX;
}
/*
* On arm64, we have to ensure that the initrd ends up in the linear region,
* which is a 1 GB aligned region of size '1UL << (VA_BITS_MIN - 1)' that is
@@ -141,4 +135,9 @@ static inline void efi_set_pgd(struct mm_struct *mm)
void efi_virtmap_load(void);
void efi_virtmap_unload(void);
static inline void efi_capsule_flush_cache_range(void *addr, int size)
{
__flush_dcache_area(addr, size);
}
#endif /* _ASM_EFI_H */
arch/arm64/kernel/smp.c
+1 -1
View File
@@ -868,7 +868,7 @@ int arch_show_interrupts(struct seq_file *p, int prec)
seq_printf(p, "%*s%u:%s", prec - 1, "IPI", i,
prec >= 4 ? " " : "");
for_each_online_cpu(cpu)
seq_printf(p, "%10u ", kstat_irqs_cpu(irq, cpu));
seq_printf(p, "%10u ", irq_desc_kstat_cpu(ipi_desc[i], cpu));
seq_printf(p, " %s\n", ipi_types[i]);
}
arch/parisc/kernel/irq.c
+2 -5
View File
@@ -216,12 +216,9 @@ int show_interrupts(struct seq_file *p, void *v)
if (!action)
goto skip;
seq_printf(p, "%3d: ", i);
#ifdef CONFIG_SMP
for_each_online_cpu(j)
seq_printf(p, "%10u ", kstat_irqs_cpu(i, j));
#else
seq_printf(p, "%10u ", kstat_irqs(i));
#endif
seq_printf(p, "%10u ", irq_desc_kstat_cpu(desc, j));
seq_printf(p, " %14s", irq_desc_get_chip(desc)->name);
#ifndef PARISC_IRQ_CR16_COUNTS
arch/powerpc/boot/Makefile
+2
View File
@@ -373,6 +373,8 @@ initrd-y := $(filter-out $(image-y), $(initrd-y))
targets += $(image-y) $(initrd-y)
targets += $(foreach x, dtbImage uImage cuImage simpleImage treeImage, \
$(patsubst $(x).%, dts/%.dtb, $(filter $(x).%, $(image-y))))
targets += $(foreach x, dtbImage uImage cuImage simpleImage treeImage, \
$(patsubst $(x).%, dts/fsl/%.dtb, $(filter $(x).%, $(image-y))))
$(addprefix $(obj)/, $(initrd-y)): $(obj)/ramdisk.image.gz
arch/powerpc/include/asm/ppc_asm.h
+6 -1
View File
@@ -180,7 +180,12 @@ END_FW_FTR_SECTION_IFSET(FW_FEATURE_SPLPAR)
#define VCPU_GPR(n) __VCPU_GPR(__REG_##n)
#ifdef __KERNEL__
#ifdef CONFIG_PPC64
/*
* We use __powerpc64__ here because we want the compat VDSO to use the 32-bit
* version below in the else case of the ifdef.
*/
#ifdef __powerpc64__
#define STACKFRAMESIZE 256
#define __STK_REG(i) (112 + ((i)-14)*8)
arch/powerpc/include/asm/vdso/timebase.h
+1 -1
View File
@@ -49,7 +49,7 @@ static inline unsigned long get_tbl(void)
return mftb();
}
static inline u64 get_tb(void)
static __always_inline u64 get_tb(void)
{
unsigned int tbhi, tblo, tbhi2;
arch/powerpc/kernel/head_32.h
+17 -10
View File
@@ -121,18 +121,28 @@
#ifdef CONFIG_VMAP_STACK
mfspr r11, SPRN_SRR0
mtctr r11
#endif
andi. r11, r9, MSR_PR
mr r11, r1
lwz r1,TASK_STACK-THREAD(r12)
beq- 99f
addi r1, r1, THREAD_SIZE - INT_FRAME_SIZE
li r10, MSR_KERNEL & ~(MSR_IR | MSR_RI) /* can take DTLB miss */
mtmsr r10
isync
tovirt(r12, r12)
stw r11,GPR1(r1)
stw r11,0(r1)
mr r11, r1
#else
andi. r11, r9, MSR_PR
lwz r11,TASK_STACK-THREAD(r12)
beq- 99f
addi r11, r11, THREAD_SIZE - INT_FRAME_SIZE
#ifdef CONFIG_VMAP_STACK
li r10, MSR_KERNEL & ~(MSR_IR | MSR_RI) /* can take DTLB miss */
mtmsr r10
isync
tophys(r11, r11)
stw r1,GPR1(r11)
stw r1,0(r11)
tovirt(r1, r11) /* set new kernel sp */
#endif
tovirt_vmstack r12, r12
tophys_novmstack r11, r11
mflr r10
stw r10, _LINK(r11)
#ifdef CONFIG_VMAP_STACK
@@ -140,9 +150,6 @@
#else
mfspr r10,SPRN_SRR0
#endif
stw r1,GPR1(r11)
stw r1,0(r11)
tovirt_novmstack r1, r11 /* set new kernel sp */
stw r10,_NIP(r11)
mfcr r10
rlwinm r10,r10,0,4,2 /* Clear SO bit in CR */
arch/powerpc/kernel/smp.c
+1 -1
View File
@@ -990,7 +990,7 @@ static struct sched_domain_topology_level powerpc_topology[] = {
{ NULL, },
};
static int init_big_cores(void)
static int __init init_big_cores(void)
{
int cpu;
arch/powerpc/kernel/vdso32/Makefile
+2 -2
View File
@@ -2,7 +2,7 @@
# List of files in the vdso, has to be asm only for now
ARCH_REL_TYPE_ABS := R_PPC_JUMP_SLOT|R_PPC_GLOB_DAT|R_PPC_ADDR32|R_PPC_ADDR24|R_PPC_ADDR16|R_PPC_ADDR16_LO|R_PPC_ADDR16_HI|R_PPC_ADDR16_HA|R_PPC_ADDR14|R_PPC_ADDR14_BRTAKEN|R_PPC_ADDR14_BRNTAKEN
ARCH_REL_TYPE_ABS := R_PPC_JUMP_SLOT|R_PPC_GLOB_DAT|R_PPC_ADDR32|R_PPC_ADDR24|R_PPC_ADDR16|R_PPC_ADDR16_LO|R_PPC_ADDR16_HI|R_PPC_ADDR16_HA|R_PPC_ADDR14|R_PPC_ADDR14_BRTAKEN|R_PPC_ADDR14_BRNTAKEN|R_PPC_REL24
include $(srctree)/lib/vdso/Makefile
obj-vdso32 = sigtramp.o gettimeofday.o datapage.o cacheflush.o note.o getcpu.o
@@ -27,7 +27,7 @@ endif
CC32FLAGS :=
ifdef CONFIG_PPC64
CC32FLAGS += -m32
KBUILD_CFLAGS := $(filter-out -mcmodel=medium,$(KBUILD_CFLAGS))
KBUILD_CFLAGS := $(filter-out -mcmodel=medium -mabi=elfv1 -mabi=elfv2 -mcall-aixdesc,$(KBUILD_CFLAGS))
endif
targets := $(obj-vdso32) vdso32.so.dbg

Some files were not shown because too many files have changed in this diff Show More