openstick: add uf896-v1_1 support

.drone-checkpatch.txt

@@ -0,0 +1,2 @@
+ERROR:
+FROM_SIGN_OFF_MISMATCH

.drone.sh

@@ -0,0 +1,22 @@
+#!/bin/sh
+# SPDX-License-Identifier: GPL-2.0-only
+set -eux
+
+case "$1" in
+build)
+	nproc && grep Mem /proc/meminfo && df -hT .
+	apk add build-base bison findutils flex gmp-dev mpc1-dev mpfr-dev openssl-dev perl
+	make msm8916_defconfig
+	make KCFLAGS="-Wall -Werror" -j$(nproc)
+	;;
+check)
+	apk add git perl
+	git format-patch origin/$DRONE_TARGET_BRANCH
+	scripts/checkpatch.pl --strict --color=always *.patch || :
+	! scripts/checkpatch.pl --strict --color=always --terse --show-types *.patch \
+		| grep -Ff .drone-checkpatch.txt
+	;;
+*)
+	exit 1
+	;;
+esac

.drone.yml

@@ -0,0 +1,49 @@
+---
+kind: pipeline
+name: aarch64
+
+platform:
+  os: linux
+  arch: arm64
+
+clone:
+  depth: 16
+
+steps:
+  - name: build
+    image: arm64v8/alpine:3.12
+    commands: [./.drone.sh build]
+  - name: check
+    image: arm64v8/alpine:3.12
+    commands: [./.drone.sh check]
+    when:
+      event: pull_request
+
+trigger:
+  event: [push, pull_request, tag]
+
+---
+kind: pipeline
+name: armv7
+
+platform:
+  os: linux
+  arch: arm
+
+clone:
+  depth: 16
+
+steps:
+  - name: build
+    image: arm32v7/alpine:3.12
+    commands:
+      - cat arch/arm64/configs/msm8916_defconfig arch/arm/configs/msm8916_defconfig.part > arch/arm/configs/msm8916_defconfig
+      - ./.drone.sh build
+  - name: check
+    image: arm32v7/alpine:3.12
+    commands: [./.drone.sh check]
+    when:
+      event: pull_request
+
+trigger:
+  event: [push, pull_request, tag]

CONTRIBUTING.md

@@ -0,0 +1,101 @@
+# Contributing to msm8916-mainline/linux
+Thanks for your interest in contributing to msm8916-mainline/linux! :tada:
+
+## About
+[msm8916-mainline/linux] is a fork of the [mainline Linux kernel](https://kernel.org)
+(released by Linus Torvalds). Goal of the repository is to **temporarily** host
+**work-in-progress** changes for various devices based on the
+Qualcomm Snapdragon 410/412 (MSM8916) SoC.
+
+Once ready, changes should be [submitted upstream](https://www.kernel.org/doc/html/latest/process/submitting-patches.html)
+through the appropriate mailing lists.  
+**Changes submitted in this repository will not automatically land upstream!**
+
+**Note:** This fork is **unofficial** and not (directly) affiliated to the mainline
+Linux project. As such, it is entirely **optional** to submit your changes as
+pull request to this repository. You can also immediately send your changes
+upstream to the appropriate mailing lists. Submitting your changes here (before
+sending them upstream) has the following advantages:
+
+  - **Preliminary review:** You get early feedback on your patches which may
+    speed up submission of your patch upstream later.
+    **Note:** Acceptance of your patch in this repository does not mean that
+    the upstream maintainers will accept it!
+
+  - **Kept up-to-date:** All patches in this repository will be rebased to newer
+    upstream Linux releases, so your device will be always up-to-date even with
+    some work-in-progress changes.
+
+  - **Packaged in [postmarketOS]:** This fork is the source of the
+    `linux-postmarketos-qcom-msm8916` package in postmarketOS, which is used by
+    all MSM8916 devices based on the mainline kernel. Your changes will be
+    included in the next release and therefore show up in postmarketOS.
+
+## Patch Requirements
+Goal for all patches in this repository is to upstream them eventually. Therefore,
+the formal requirements are similar to upstream, e.g.:
+
+  - No compile warnings/errors
+  - Clean code style
+  - Changes separated into clean commits (one per logical change/subsystem)
+  - Appropriate commit message that explains the motivation for the change
+
+If you want to contribute to this repository, you should be willing to bring your
+patches into suitable shape for upstreaming. Most of this is documented upstream
+in [Submitting patches]. Don't worry if you don't get it exactly right the first time. :)
+
+### Sign off your patches - the Developer's Certificate of Origin
+Upstream contributions to the Linux kernel are required to have the following
+tag in the commit message:
+
+```
+Signed-off-by: FirstName LastName <your-email@example.com>
+```
+
+These tags are also required when contributing to this repository. Reason for
+this is that you might become busy at some point, or your interests change. Then
+it is important that someone else can pick up your work and finish it up.
+
+Please read [Sign your work - the Developer’s Certificate of Origin](https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin)
+**carefully** to understand the meaning of the `Signed-off-by:`.
+It also explains how to add it easily when creating new commits.
+
+## Upstreaming
+Upstreaming changes takes time. And sometimes, changes cannot be submitted
+upstream yet because they are work-in-progress or because there are fundamental
+open problems that cannot be solved immediately, e.g.:
+
+  - Weird issues where the actual cause cannot be determined at the moment ("hacks").
+  - New drivers with problems in some edge cases.
+  - Panel drivers that are mostly auto-generated and that are hard to document
+    properly because of lack of documentation.
+  - Battery/charging drivers that are hard to validate without expert knowledge.
+
+If you have something (mostly) working and the [formal patch requirements](#patch-requirements)
+are met, then it's good to share it with others in this repository.
+
+However, keep in mind that maintaining a large amount of patches in this
+repository consumes a significant amount of time, especially when breaking
+changes are made upstream. This means less time to review new patches
+or to work on improvements everyone can benefit from.
+
+**Please help to keep maintenance time at an acceptable level by submitting your
+patches upstream when they are ready.** If you are not sure if your patches are
+ready, just ask and we can discuss it.
+
+### Patches that touch upstream files
+Patches that touch upstream files which are frequently updated
+(e.g. existing, shared drivers instead of files specific to your device)
+should be submitted upstream before they are merged into this repository.
+This is because those tend to cause conflicts much more frequently when updating
+to newer kernel versions.
+
+This is just a guideline to reduce maintenance, exceptions can be made if necessary.
+
+## Questions
+If you have any questions, feel free to ask in the [postmarketOS mainline channel
+on Matrix or IRC](https://wiki.postmarketos.org/wiki/Matrix_and_IRC).
+
+[msm8916-mainline/linux]: https://github.com/msm8916-mainline/linux
+[postmarketOS]: https://postmarketos.org
+[Submitting patches]: https://www.kernel.org/doc/html/latest/process/submitting-patches.html

Documentation/admin-guide/kernel-parameters.txt

@@ -1690,6 +1690,8 @@
 			architectures force reset to be always executed
 	i8042.unlock	[HW] Unlock (ignore) the keylock
 	i8042.kbdreset	[HW] Reset device connected to KBD port
+	i8042.probe_defer
+			[HW] Allow deferred probing upon i8042 probe errors
 
 	i810=		[HW,DRM]
 
@@ -2403,8 +2405,12 @@
 			Default is 1 (enabled)
 
 	kvm-intel.emulate_invalid_guest_state=
-			[KVM,Intel] Enable emulation of invalid guest states
-			Default is 0 (disabled)
+			[KVM,Intel] Disable emulation of invalid guest state.
+			Ignored if kvm-intel.enable_unrestricted_guest=1, as
+			guest state is never invalid for unrestricted guests.
+			This param doesn't apply to nested guests (L2), as KVM
+			never emulates invalid L2 guest state.
+			Default is 1 (enabled)
 
 	kvm-intel.flexpriority=
 			[KVM,Intel] Disable FlexPriority feature (TPR shadow).
@@ -6349,6 +6355,13 @@
 			improve timer resolution at the expense of processing
 			more timer interrupts.
 
+	xen.balloon_boot_timeout= [XEN]
+			The time (in seconds) to wait before giving up to boot
+			in case initial ballooning fails to free enough memory.
+			Applies only when running as HVM or PVH guest and
+			started with less memory configured than allowed at
+			max. Default is 180.
+
 	xen.event_eoi_delay=	[XEN]
 			How long to delay EOI handling in case of event
 			storms (jiffies). Default is 10.

Documentation/admin-guide/sysctl/kernel.rst

@@ -1099,7 +1099,7 @@ task_delayacct
 ===============
 
 Enables/disables task delay accounting (see
-:doc:`accounting/delay-accounting.rst`). Enabling this feature incurs
+Documentation/accounting/delay-accounting.rst. Enabling this feature incurs
 a small amount of overhead in the scheduler but is useful for debugging
 and performance tuning. It is required by some tools such as iotop.
 

Documentation/dev-tools/kfence.rst

@@ -231,10 +231,14 @@ Guarded allocations are set up based on the sample interval. After expiration
 of the sample interval, the next allocation through the main allocator (SLAB or
 SLUB) returns a guarded allocation from the KFENCE object pool (allocation
 sizes up to PAGE_SIZE are supported). At this point, the timer is reset, and
-the next allocation is set up after the expiration of the interval. To "gate" a
-KFENCE allocation through the main allocator's fast-path without overhead,
-KFENCE relies on static branches via the static keys infrastructure. The static
-branch is toggled to redirect the allocation to KFENCE.
+the next allocation is set up after the expiration of the interval.
+
+When using ``CONFIG_KFENCE_STATIC_KEYS=y``, KFENCE allocations are "gated"
+through the main allocator's fast-path by relying on static branches via the
+static keys infrastructure. The static branch is toggled to redirect the
+allocation to KFENCE. Depending on sample interval, target workloads, and
+system architecture, this may perform better than the simple dynamic branch.
+Careful benchmarking is recommended.
 
 KFENCE objects each reside on a dedicated page, at either the left or right
 page boundaries selected at random. The pages to the left and right of the

Documentation/devicetree/bindings/iio/dac/adi,ad5766.yaml

@@ -54,7 +54,7 @@ examples:
 
           ad5766@0 {
               compatible = "adi,ad5766";
-              output-range-microvolts = <(-5000) 5000>;
+              output-range-microvolts = <(-5000000) 5000000>;
               reg = <0>;
               spi-cpol;
               spi-max-frequency = <1000000>;

Documentation/devicetree/bindings/media/nxp,imx7-mipi-csi2.yaml

@@ -79,6 +79,8 @@ properties:
 
             properties:
               data-lanes:
+                description:
+                  Note that 'fsl,imx7-mipi-csi2' only supports up to 2 data lines.
                 items:
                   minItems: 1
                   maxItems: 4
@@ -91,18 +93,6 @@ properties:
             required:
               - data-lanes
 
-            allOf:
-              - if:
-                  properties:
-                    compatible:
-                      contains:
-                        const: fsl,imx7-mipi-csi2
-                then:
-                  properties:
-                    data-lanes:
-                      items:
-                        maxItems: 2
-
       port@1:
         $ref: /schemas/graph.yaml#/properties/port
         description:

Documentation/devicetree/bindings/net/ethernet-phy.yaml

@@ -91,6 +91,14 @@ properties:
       compensate for the board being designed with the lanes
       swapped.
 
+  enet-phy-lane-no-swap:
+    $ref: /schemas/types.yaml#/definitions/flag
+    description:
+      If set, indicates that PHY will disable swap of the
+      TX/RX lanes. This property allows the PHY to work correcly after
+      e.g. wrong bootstrap configuration caused by issues in PCB
+      layout design.
+
   eee-broken-100tx:
     $ref: /schemas/types.yaml#/definitions/flag
     description: