arm64: dts: qcom: msm8939-longcheer-l9100: Add sound

.ci-check.sh

@@ -0,0 +1,8 @@
+#!/bin/sh
+# SPDX-License-Identifier: GPL-2.0-only
+set -eux
+
+git format-patch "$1"
+scripts/checkpatch.pl --strict --color=always *.patch || :
+! scripts/checkpatch.pl --strict --color=always --terse --show-types *.patch \
+	| grep -Ff .ci-checkpatch.txt

.ci-checkpatch.txt

@@ -0,0 +1,7 @@
+ERROR:
+BAD_SIGN_OFF:
+FROM_SIGN_OFF_MISMATCH:
+LEADING_SPACE:
+MISSING_EOF_NEWLINE:
+SPACE_BEFORE_TAB:
+SPDX_LICENSE_TAG:

.ci-prepare.sh

@@ -0,0 +1,46 @@
+#!/bin/sh
+# SPDX-License-Identifier: GPL-2.0-only
+set -eux
+
+# Show information about CI runner environment
+nproc && grep Mem /proc/meminfo && df -hT .
+
+# Install Linux build dependencies
+apk add build-base bison findutils flex gmp-dev mpc1-dev mpfr-dev openssl-dev perl python3
+
+if [ -n "${DRONE-}" ]; then
+	# Workaround problem with faccessat2() on Drone CI
+	wget https://gist.githubusercontent.com/TravMurav/36c83efbc188115aa9b0fc7f4afba63e/raw/faccessat.c -P /opt
+	gcc -O2 -shared -o /opt/faccessat.so /opt/faccessat.c
+	export LD_PRELOAD=/opt/faccessat.so
+fi
+
+# Setup compiler
+case "$1" in
+gcc)
+	case "$ARCH" in
+		arm64)	gcc_toolchain=aarch64-none-elf ;;
+		arm)	gcc_toolchain=arm-none-eabi ;;
+	esac
+	apk add "gcc-$gcc_toolchain"
+	MAKE_OPTS="CROSS_COMPILE=$gcc_toolchain-"
+	;;
+clang)
+	apk add clang lld llvm
+	MAKE_OPTS="LLVM=1"
+	;;
+esac
+MAKE_OPTS="-j$(nproc) $MAKE_OPTS"
+
+# Write build script
+cat > .ci-build.sh <<EOF
+#!/bin/sh
+# SPDX-License-Identifier: GPL-2.0-only
+set -eux
+
+cat arch/arm64/configs/msm8916_defconfig arch/arm/configs/msm8916_defconfig.part > arch/arm/configs/msm8916_defconfig
+make $MAKE_OPTS msm8916_defconfig
+echo CONFIG_WERROR=y >> .config
+make $MAKE_OPTS
+EOF
+chmod +x .ci-build.sh

.drone.yml

@@ -0,0 +1,73 @@
+---
+kind: pipeline
+type: docker
+name: arm64
+
+platform:
+  os: linux
+  arch: amd64
+
+clone:
+  depth: 1
+
+environment:
+  ARCH: arm64
+
+steps:
+  - name: build (gcc)
+    image: alpine:latest
+    commands:
+      - . .ci-prepare.sh gcc
+      - ./.ci-build.sh
+      - apk add git && git clean -dxfq
+
+  - name: build (clang)
+    image: alpine:latest
+    commands:
+      - . .ci-prepare.sh clang
+      - ./.ci-build.sh
+
+  - name: check
+    image: alpine:latest
+    commands:
+      - apk add git perl
+      - ./.ci-check.sh origin/$DRONE_TARGET_BRANCH
+    when:
+      event: pull_request
+
+---
+kind: pipeline
+type: docker
+name: arm
+
+platform:
+  os: linux
+  arch: amd64
+
+clone:
+  depth: 1
+
+environment:
+  ARCH: arm
+
+steps:
+  - name: build (gcc)
+    image: alpine:latest
+    commands:
+      - . .ci-prepare.sh gcc
+      - ./.ci-build.sh
+      - apk add git && git clean -dxfq
+
+  - name: build (clang)
+    image: alpine:latest
+    commands:
+      - . .ci-prepare.sh clang
+      - ./.ci-build.sh
+
+  - name: check
+    image: alpine:latest
+    commands:
+      - apk add git perl
+      - ./.ci-check.sh origin/$DRONE_TARGET_BRANCH
+    when:
+      event: pull_request

.github/workflows/build.yml

@@ -0,0 +1,21 @@
+name: Build
+on: [push, pull_request]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        arch: [arm64, arm]
+        compiler: [gcc, clang]
+    env:
+      ARCH: ${{ matrix.arch }}
+    steps:
+    - uses: actions/checkout@v3
+    - uses: jirutka/setup-alpine@v1
+    - name: Prepare build environment
+      run: ./.ci-prepare.sh ${{ matrix.compiler }}
+      shell: alpine.sh --root {0}
+    - name: Build
+      run: ./.ci-build.sh
+      shell: alpine.sh {0}

.github/workflows/check.yml

@@ -0,0 +1,11 @@
+name: Check
+on: [pull_request]
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+      with:
+        fetch-depth: 64
+    - name: Run checkpatch.pl
+      run: ./.ci-check.sh HEAD~1

.mailmap

@@ -384,6 +384,7 @@ Li Yang <[email protected]> <[email protected]>
 Li Yang <[email protected]> <[email protected]>
 Lior David <[email protected]> <[email protected]>
 Lorenzo Pieralisi <[email protected]> <[email protected]>
+Lorenzo Stoakes <[email protected]> <[email protected]>
 Luca Ceresoli <[email protected]> <[email protected]>
 Lukasz Luba <[email protected]> <[email protected]>
 Luo Jie <[email protected]> <[email protected]>

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 <[email protected]>
+```
+
+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

CREDITS

@@ -1214,6 +1214,10 @@ D: UDF filesystem
 S: (ask for current address)
 S: USA
 
+N: Larry Finger
+E: [email protected]
+D: Maintainer of wireless drivers, too many to list here
+
 N: Jürgen Fischer
 E: [email protected]
 D: Author of Adaptec AHA-152x SCSI driver
@@ -3146,9 +3150,11 @@ S: Triftstra=DFe 55
 S: 13353 Berlin
 S: Germany
 
-N: Gustavo Pimental
+N: Gustavo Pimentel
 E: [email protected]
 D: PCI driver for Synopsys DesignWare
+D: Synopsys DesignWare eDMA driver
+D: Synopsys DesignWare xData traffic generator
 
 N: Emanuel Pirker
 E: [email protected]

Documentation/admin-guide/cifs/usage.rst

@@ -723,40 +723,26 @@ Configuration pseudo-files:
 ======================= =======================================================
 SecurityFlags		Flags which control security negotiation and
 			also packet signing. Authentication (may/must)
-			flags (e.g. for NTLM and/or NTLMv2) may be combined with
+			flags (e.g. for NTLMv2) may be combined with
 			the signing flags.  Specifying two different password
 			hashing mechanisms (as "must use") on the other hand
 			does not make much sense. Default flags are::
 
-				0x07007
-
-			(NTLM, NTLMv2 and packet signing allowed).  The maximum
-			allowable flags if you want to allow mounts to servers
-			using weaker password hashes is 0x37037 (lanman,
-			plaintext, ntlm, ntlmv2, signing allowed).  Some
-			SecurityFlags require the corresponding menuconfig
-			options to be enabled.  Enabling plaintext
-			authentication currently requires also enabling
-			lanman authentication in the security flags
-			because the cifs module only supports sending
-			laintext passwords using the older lanman dialect
-			form of the session setup SMB.  (e.g. for authentication
-			using plain text passwords, set the SecurityFlags
-			to 0x30030)::
+				0x00C5
+
+			(NTLMv2 and packet signing allowed).  Some SecurityFlags
+			may require enabling a corresponding menuconfig option.
 
 			  may use packet signing			0x00001
 			  must use packet signing			0x01001
-			  may use NTLM (most common password hash)	0x00002
-			  must use NTLM					0x02002
 			  may use NTLMv2				0x00004
 			  must use NTLMv2				0x04004
-			  may use Kerberos security			0x00008
-			  must use Kerberos				0x08008
-			  may use lanman (weak) password hash		0x00010
-			  must use lanman password hash			0x10010
-			  may use plaintext passwords			0x00020
-			  must use plaintext passwords			0x20020
-			  (reserved for future packet encryption)	0x00040
+			  may use Kerberos security (krb5)		0x00008
+			  must use Kerberos                             0x08008
+			  may use NTLMSSP               		0x00080
+			  must use NTLMSSP           			0x80080
+			  seal (packet encryption)			0x00040
+			  must seal (not implemented yet)               0x40040
 
 cifsFYI			If set to non-zero value, additional debug information
 			will be logged to the system error log.  This field

Documentation/admin-guide/kernel-parameters.txt

@@ -788,25 +788,6 @@
 			Documentation/networking/netconsole.rst for an
 			alternative.
 
-		<DEVNAME>:<n>.<n>[,options]
-			Use the specified serial port on the serial core bus.
-			The addressing uses DEVNAME of the physical serial port
-			device, followed by the serial core controller instance,
-			and the serial port instance. The options are the same
-			as documented for the ttyS addressing above.
-
-			The mapping of the serial ports to the tty instances
-			can be viewed with:
-
-			$ ls -d /sys/bus/serial-base/devices/*:*.*/tty/*
-			/sys/bus/serial-base/devices/00:04:0.0/tty/ttyS0
-
-			In the above example, the console can be addressed with
-			console=00:04:0.0. Note that a console addressed this
-			way will only get added when the related device driver
-			is ready. The use of an earlycon parameter in addition to
-			the console may be desired for console output early on.
-
 		uart[8250],io,<addr>[,options]
 		uart[8250],mmio,<addr>[,options]
 		uart[8250],mmio16,<addr>[,options]

Documentation/arch/riscv/cmodx.rst

@@ -62,10 +62,10 @@ cmodx.c::
 		printf("Value before cmodx: %d\n", value);
 
 		// Call prctl before first fence.i is called inside modify_instruction
-		prctl(PR_RISCV_SET_ICACHE_FLUSH_CTX_ON, PR_RISCV_CTX_SW_FENCEI, PR_RISCV_SCOPE_PER_PROCESS);
+		prctl(PR_RISCV_SET_ICACHE_FLUSH_CTX, PR_RISCV_CTX_SW_FENCEI_ON, PR_RISCV_SCOPE_PER_PROCESS);
 		modify_instruction();
 		// Call prctl after final fence.i is called in process
-		prctl(PR_RISCV_SET_ICACHE_FLUSH_CTX_OFF, PR_RISCV_CTX_SW_FENCEI, PR_RISCV_SCOPE_PER_PROCESS);
+		prctl(PR_RISCV_SET_ICACHE_FLUSH_CTX, PR_RISCV_CTX_SW_FENCEI_OFF, PR_RISCV_SCOPE_PER_PROCESS);
 
 		value = get_value();
 		printf("Value after cmodx: %d\n", value);