Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • Librem5/linux
  • angus.ainslie/linux
  • eric.kuzmenko/linux-next
  • guido.gunther/linux-next
  • martin.kepplinger/linux-next
  • sebastian.krzyszkowiak/linux-next
  • DanielAbrecht/linux-next
  • fuzzy7k/linux-next
  • dlandau/linux-next
  • craftyguy/linux-next
  • elias/linux-next
  • evangelos.tzaras/linux
  • lefo/linux
  • rusty-shackleford/linux-next
  • evangelos.tzaras/linux-next
  • ChriChri/linux
  • dorota.czaplejewicz/linux-next
  • primalmotion/linux
  • alistair23/linux
19 results
Show changes
Commits on Source (1192)
Showing
with 205 additions and 23 deletions
......@@ -73,7 +73,8 @@ modules.order
#
# Debian directory (make deb-pkg)
#
/debian/
/debian/*tmp/
/debian/files
#
# Snap directory (make snap-pkg)
......
variables:
GIT_DEPTH: 10
DEPS: >
build-essential gcc-aarch64-linux-gnu gcc-arm-linux-gnueabihf make device-tree-compiler
bison flex bc libssl-dev
WORKING_DIR: $CI_PROJECT_DIR/debian/output
before_script:
- echo "man-db man-db/auto-update boolean false" | debconf-set-selections
- export DEBIAN_FRONTEND=noninteractive
- apt-get -y update
- apt-get -y build-dep .
- apt-get -y install build-essential devscripts
.tags: &tags
tags:
- librem5
build:aarch64:
<<: *tags
stage: build
allow_failure: true
variables:
CROSS_BUILD: "ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-"
script:
- make ${CROSS_BUILD} librem5_defconfig
- KCFLAGS="-Werror" make -j 4 ${CROSS_BUILD} Image dtbs modules
- make -j 4 ${CROSS_BUILD} INSTALL_MOD_PATH=modules/ modules_install
artifacts:
paths:
- arch/arm64/boot/Image
- arch/arm64/boot/dts/freescale/imx8mq-librem5*.dtb
- modules/
expire_in: 1 week
build:deb:
tags:
- librem5:arm64
stage: build
script:
- git clean -dfx
- git checkout -f
- rm -f ../* || true
- rm -rf "${WORKING_DIR}"; mkdir -p "${WORKING_DIR}"
- debian/rules debian/control
- dch -l +gitlabci "Gitlab ci build of ${CI_COMMIT_SHA}"
- dpkg-buildpackage -j4 -uc -us -B --host-arch=arm64
- cp -l ../*.deb ../*.changes ../*.buildinfo "${WORKING_DIR}/"
artifacts:
paths:
- "${WORKING_DIR}"
expire_in: 1 week
......@@ -17,7 +17,7 @@ PMU events
----------
The PMU driver registers a single PMU device for the whole interconnect,
see /sys/bus/event_source/devices/arm_cmn. Multi-chip systems may link
see /sys/bus/event_source/devices/arm_cmn_0. Multi-chip systems may link
more than one CMN together via external CCIX links - in this situation,
each mesh counts its own events entirely independently, and additional
PMU devices will be named arm_cmn_{1..n}.
......
......@@ -983,11 +983,11 @@ that benefit from having their data cached, zone_reclaim_mode should be
left disabled as the caching effect is likely to be more important than
data locality.
zone_reclaim may be enabled if it's known that the workload is partitioned
such that each partition fits within a NUMA node and that accessing remote
memory would cause a measurable performance reduction. The page allocator
will then reclaim easily reusable pages (those page cache pages that are
currently not used) before allocating off node pages.
Consider enabling one or more zone_reclaim mode bits if it's known that the
workload is partitioned such that each partition fits within a NUMA node
and that accessing remote memory would cause a measurable performance
reduction. The page allocator will take additional actions before
allocating off node pages.
Allowing zone reclaim to write out pages stops processes that are
writing large amounts of data from dirtying pages on other nodes. Zone
......
......@@ -724,6 +724,7 @@ properties:
- enum:
- purism,librem5r2 # Purism Librem5 phone "Chestnut"
- purism,librem5r3 # Purism Librem5 phone "Dogwood"
- purism,librem5r4 # Purism Librem5 phone "Evergreen"
- const: purism,librem5
- const: fsl,imx8mq
......
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause))
%YAML 1.2
---
$id: http://devicetree.org/schemas/display/bridge/cdns,mhdp.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Cadence MHDP TX Encoder
maintainers:
- Sandor Yu <Sandoryu@nxp.com>
description: |
Cadence MHDP Controller supports one or more of the protocols,
such as HDMI and DisplayPort.
Each protocol requires a different FW binaries.
This document defines device tree properties for the Cadence MHDP Encoder
(CDNS MHDP TX). It doesn't constitue a device tree binding
specification by itself but is meant to be referenced by platform-specific
device tree bindings.
When referenced from platform device tree bindings the properties defined in
this document are defined as follows. The platform device tree bindings are
responsible for defining whether each property is required or optional.
properties:
reg:
maxItems: 1
description: Memory mapped base address and length of the MHDP TX registers.
interrupts:
maxItems: 2
interrupt-names:
- const: plug_in
description: Hotplug detect interrupter for cable plugin event.
- const: plug_out
description: Hotplug detect interrupter for cable plugout event.
port:
type: object
description: |
The connectivity of the MHDP TX with the rest of the system is
expressed in using ports as specified in the device graph bindings defined
in Documentation/devicetree/bindings/graph.txt. The numbering of the ports
is platform-specific.
......@@ -44,6 +44,8 @@ properties:
- description: TX_ESC clock (used in escape mode)
- description: PHY_REF clock
- description: LCDIF clock
- description: VIDEO_PLL clock (used to set the the PLL clock feeding both
phy_ref and DC pixel clock to a convenient rate)
clock-names:
items:
......@@ -52,6 +54,7 @@ properties:
- const: tx_esc
- const: phy_ref
- const: lcdif
- const: video_pll
mux-controls:
description:
......
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/display/bridge/mhdp.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Cadence MHDP Encoder
maintainers:
- Sandor Yu <Sandoryu@nxp.com>
description: |
The MHDP transmitter is a Cadence HD Display TX controller IP
with a companion PHY IP.
The MHDP supports one or more of the protocols,
such as HDMI(1.4 & 2.0), DisplayPort(1.2).
switching between the two modes (HDMI and DisplayPort)
requires reloading the appropriate FW
These DT bindings follow the Cadence MHDP TX bindings defined in
Documentation/devicetree/bindings/display/bridge/cdns,mhdp.yaml with the
following device-specific properties.
Properties:
compatible:
enum:
- nxp,imx8mq-cdns-hdmi
- nxp,imx8mq-cdns-dp
reg: See cdns,mhdp.yaml.
interrupts: See cdns,mhdp.yaml.
interrupt-names: See cdns,mhdp.yaml.
ports: See cdns,mhdp.yaml.
Required:
- compatible
- reg
- interrupts
- interrupt-names
- ports
Example:
- |
mhdp: mhdp@32c00000 {
compatible = "nxp,imx8mq-cdns-hdmi";
reg = <0x32c00000 0x100000>;
interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "plug_in", "plug_out";
ports {
mhdp_in: endpoint {
remote-endpoint = <&dcss_out>;
};
};
};
......@@ -15,6 +15,12 @@ Required properties:
- "pix" for the LCDIF block clock
- (MX6SX-only) "axi", "disp_axi" for the bus interface clock
Optional properties:
- interconnects : interconnect path specifier for LCDIF according to
Documentation/devicetree/bindings/interconnect/interconnect.txt.
- interconnect-names: the name describing the interconnect path.
Should be "dram" for i.MX8MQ.
Required sub-nodes:
- port: The connection to an encoder chip.
......
......@@ -20,6 +20,7 @@ properties:
compatible:
enum:
- mantix,mlaf057we51-x
- ys,ys57pss36bh5gq
port: true
reg:
......
......@@ -18,6 +18,8 @@ Required properties:
Optional properties:
- enable-gpios : gpio pin to enable/disable the device.
- vled-supply : LED supply
- ti,brightness-mapping-exponential: Whether to use exponential
brightness mapping
- ti,ovp-microvolt: Overvoltage protection in
micro-volt, can be 17000000, 21000000, 25000000 or
29000000. If ti,ovp-microvolt is not specified it
......@@ -51,6 +53,7 @@ led-controller@36 {
enable-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>;
vled-supply = <&vbatt>;
ti,ovp-microvolt = <29000000>;
ti,brightness-mapping-exponential;
led@0 {
reg = <0>;
......
......@@ -38,7 +38,7 @@ Following example uses irq pin number 3 of gpio0 for out of band wake-on-bt:
compatible = "usb1286,204e";
reg = <1>;
interrupt-parent = <&gpio0>;
interrupt-name = "wakeup";
interrupt-names = "wakeup";
interrupts = <3 IRQ_TYPE_LEVEL_LOW>;
};
};
......@@ -205,6 +205,11 @@ properties:
Indicates that full-duplex is used. When absent, half
duplex is assumed.
pause:
$ref: /schemas/types.yaml#definitions/flag
description:
Indicates that pause should be enabled.
asym-pause:
$ref: /schemas/types.yaml#/definitions/flag
description:
......
......@@ -1254,6 +1254,8 @@ patternProperties:
description: Xylon
"^yes-optoelectronics,.*":
description: Yes Optoelectronics Co.,Ltd.
"^ys,.*":
description: Shenzhen Yashi Changhua Intelligent Technology Co., Ltd.
"^ylm,.*":
description: Shenzhen Yangliming Electronic Technology Co., Ltd.
"^yna,.*":
......
......@@ -217,6 +217,12 @@ between the calls to start() and stop(), so holding a lock during that time
is a reasonable thing to do. The seq_file code will also avoid taking any
other locks while the iterator is active.
The iterater value returned by start() or next() is guaranteed to be
passed to a subsequent next() or stop() call. This allows resources
such as locks that were taken to be reliably released. There is *no*
guarantee that the iterator will be passed to show(), though in practice
it often will be.
Formatted output
================
......
......@@ -630,16 +630,15 @@ tcp_rmem - vector of 3 INTEGERs: min, default, max
default: initial size of receive buffer used by TCP sockets.
This value overrides net.core.rmem_default used by other protocols.
Default: 87380 bytes. This value results in window of 65535 with
default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
less for default tcp_app_win. See below about these variables.
Default: 131072 bytes.
This value results in initial window of 65535.
max: maximal size of receive buffer allowed for automatically
selected receiver buffers for TCP socket. This value does not override
net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
automatic tuning of that socket's receive buffer size, in which
case this value is ignored.
Default: between 87380B and 6MB, depending on RAM size.
Default: between 131072 and 6MB, depending on RAM size.
tcp_sack - BOOLEAN
Enable select acknowledgments (SACKS).
......
......@@ -190,12 +190,10 @@ The event interface::
/* LLDD calls these to notify the class of an event. */
void (*notify_ha_event)(struct sas_ha_struct *, enum ha_event);
void (*notify_port_event)(struct sas_phy *, enum port_event);
void (*notify_phy_event)(struct sas_phy *, enum phy_event);
When sas_register_ha() returns, those are set and can be
called by the LLDD to notify the SAS layer of such events
the SAS layer.
void sas_notify_port_event(struct sas_phy *, enum port_event);
void sas_notify_phy_event(struct sas_phy *, enum phy_event);
void sas_notify_port_event_gfp(struct sas_phy *, enum port_event, gfp_t);
void sas_notify_phy_event_gfp(struct sas_phy *, enum phy_event, gfp_t);
The port notification::
......
......@@ -1040,8 +1040,8 @@ The keyctl syscall functions are:
"key" is the ID of the key to be watched.
"queue_fd" is a file descriptor referring to an open "/dev/watch_queue"
which manages the buffer into which notifications will be delivered.
"queue_fd" is a file descriptor referring to an open pipe which
manages the buffer into which notifications will be delivered.
"filter" is either NULL to remove a watch or a filter specification to
indicate what events are required from the key.
......
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 11
SUBLEVEL = 0
SUBLEVEL = 4
EXTRAVERSION =
NAME = 💕 Valentine's Day Edition 💕
......
......@@ -1164,9 +1164,9 @@ __armv4_mmu_cache_off:
__armv7_mmu_cache_off:
mrc p15, 0, r0, c1, c0
#ifdef CONFIG_MMU
bic r0, r0, #0x000d
bic r0, r0, #0x0005
#else
bic r0, r0, #0x000c
bic r0, r0, #0x0004
#endif
mcr p15, 0, r0, c1, c0 @ turn MMU and cache off
mov r0, #0
......