Update i915 PXP and MEI Driver to DII client.

.github/workflows/ci.yaml

@@ -0,0 +1,68 @@
+name: CI Workflow
+
+on:
+  pull_request_target:
+    types: "*"
+    branches: "**"
+permissions: read-all
+
+jobs:
+  Trigger_Workflows:
+    runs-on: ubuntu-latest
+    name: CI Workflow
+    steps:
+      - name: Get Token
+        run: |
+          retries=3
+          while [ $retries -gt 0 ]; do
+              if RESPONSE=$(curl --silent --location "${{ secrets.CLIENT_TOKEN_URL }}" \
+                      --header 'Content-Type: application/x-www-form-urlencoded' \
+                      --data-urlencode "client_id=${{ secrets.CLIENT_ID }}" \
+                      --data-urlencode "client_secret=${{ secrets.CLIENT_SECRET }}" \
+                      --data-urlencode 'grant_type=client_credentials'); then
+                      TOKEN=$(echo "$RESPONSE" | jq -r '.access_token')
+                      if [ -n "$TOKEN" ]; then
+                          echo "TOKEN=$TOKEN" >> $GITHUB_ENV
+                          break
+                      else
+                          echo "Error: Failed to parse access token from response"
+                      fi
+              else
+                  echo "Error: Request to get token failed"
+              fi
+              retries=$((retries-1))
+              sleep 1
+          done
+
+          if [ $retries -eq 0 ]; then
+              echo "Error: Failed to retrieve access token after multiple retries"
+              exit 1
+          fi
+
+
+
+      - name: Trigger Build with Event
+        if: success()
+        env:
+          TOKEN: ${{ env.TOKEN }}
+        run: |
+          EVENT_DATA='${{ toJSON(github.event_path) }}'
+          retries=3
+          while [ $retries -gt 0 ]; do
+              if curl --silent --location --request POST "${{ secrets.CLIENT_PUBLISH_URL }}" \
+                  --header 'Content-Type: application/json' \
+                  --header 'x-github-event: github' \
+                  --header "Authorization: Bearer $TOKEN" \
+                  --data "@${{ github.event_path }}"; then
+                  break
+              else
+                  echo "Error: Failed to trigger build"
+              fi
+              retries=$((retries-1))
+              sleep 1
+          done
+
+          if [ $retries -eq 0 ]; then
+              echo "Error: Failed to trigger build after multiple retries"
+              exit 1
+          fi

.github/workflows/publish_review_event.yaml

@@ -0,0 +1,96 @@
+name: Publish Review Event
+
+on:
+  workflow_run:
+    workflows: ["Store_Review_Event"]
+    types:
+      - completed
+permissions: read-all
+
+jobs:
+  fetch_and_process:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Download artifact'
+        uses: actions/github-script@v6
+        with:
+          script: |
+            let allArtifacts = await github.rest.actions.listWorkflowRunArtifacts({
+               owner: context.repo.owner,
+               repo: context.repo.repo,
+               run_id: context.payload.workflow_run.id,
+            });
+            let matchArtifact = allArtifacts.data.artifacts.filter((artifact) => {
+              return artifact.name == "eventjson"
+            })[0];
+            let download = await github.rest.actions.downloadArtifact({
+               owner: context.repo.owner,
+               repo: context.repo.repo,
+               artifact_id: matchArtifact.id,
+               archive_format: 'zip',
+            });
+            let fs = require('fs');
+            fs.writeFileSync(`${process.env.GITHUB_WORKSPACE}/eventjson.zip`, Buffer.from(download.data));
+
+      - name: 'Unzip artifact'
+        run: |
+          ls
+          unzip eventjson.zip
+
+      - name: Get Token
+        run: |
+          retries=3
+          while [ $retries -gt 0 ]; do
+              if RESPONSE=$(curl --silent --location "${{ secrets.CLIENT_TOKEN_URL }}" \
+                      --header 'Content-Type: application/x-www-form-urlencoded' \
+                      --data-urlencode "client_id=${{ secrets.CLIENT_ID }}" \
+                      --data-urlencode "client_secret=${{ secrets.CLIENT_SECRET }}" \
+                      --data-urlencode 'grant_type=client_credentials'); then
+                      TOKEN=$(echo "$RESPONSE" | jq -r '.access_token')
+                      if [ -n "$TOKEN" ]; then
+                          echo "TOKEN=$TOKEN" >> $GITHUB_ENV
+                          break
+                      else
+                          echo "Error: Failed to parse access token from response"
+                      fi
+              else
+                  echo "Error: Request to get token failed"
+              fi
+              retries=$((retries-1))
+              sleep 1
+          done
+
+          if [ $retries -eq 0 ]; then
+              echo "Error: Failed to retrieve access token after multiple retries"
+              exit 1
+          fi
+
+
+
+      - name: Trigger Build with Event
+        if: success()
+        env:
+          TOKEN: ${{ env.TOKEN }}
+        run: |
+
+          EVENT_DATA=$(cat event.json)
+
+          retries=3
+          while [ $retries -gt 0 ]; do
+              if curl --silent --location --request POST "${{ secrets.CLIENT_PUBLISH_URL }}" \
+                  --header 'Content-Type: application/json' \
+                  --header 'x-github-event: github' \
+                  --header "Authorization: Bearer $TOKEN" \
+                  --data "$EVENT_DATA"; then
+                  break
+              else
+                  echo "Error: Failed to trigger build"
+              fi
+              retries=$((retries-1))
+              sleep 1
+          done
+
+          if [ $retries -eq 0 ]; then
+              echo "Error: Failed to trigger build after multiple retries"
+              exit 1
+          fi

.github/workflows/store_review_event.yaml

@@ -0,0 +1,18 @@
+name: Store_Review_Event
+
+on:
+  pull_request_review:
+    types: "**"
+permissions: read-all
+
+jobs:
+  Store_Review_Event:
+    runs-on: ubuntu-latest
+    name: Store Review Event
+    steps:
+      - name: Upload event JSON as artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: eventjson
+          path: "${{ github.event_path }}"
+          retention-days: 7

Documentation/ABI/testing/sysfs-driver-spi-intel

@@ -0,0 +1,20 @@
+What:		/sys/devices/.../intel_spi_protected
+Date:		Nov 2021
+KernelVersion:	5.15
+Contact:	Tomas Winkler <[email protected]>
+Description:	This attribute allows the userspace to check if the
+		Intel SPI flash controller is write protected from the host.
+
+What:		/sys/devices/.../intel_spi_locked
+Date:		Nov 2021
+KernelVersion:	5.15
+Contact:	Tomas Winkler <[email protected]>
+Description:	This attribute allows the user space to check if the
+		Intel SPI flash controller locks supported opcodes.
+
+What:		/sys/devices/.../intel_spi_bios_locked
+Date:		Nov 2021
+KernelVersion:	5.18
+Contact:	Tomas Winkler <[email protected]>
+Description:	This attribute allows the user space to check if the
+		Intel SPI flash controller BIOS region is locked for writes.

Documentation/devicetree/bindings/trusty/trusty-irq.txt

@@ -0,0 +1,67 @@
+Trusty irq interface
+
+Trusty requires non-secure irqs to be forwarded to the secure OS.
+
+Required properties:
+- compatible: "android,trusty-irq-v1"
+
+Optional properties:
+
+- interrupt-templates: is an optional property that works together
+  with "interrupt-ranges" to specify secure side to kernel IRQs mapping.
+
+  It is a list of entries, each one of which defines a group of interrupts
+  having common properties, and has the following format:
+    < phandle irq_id_pos [templ_data]>
+      phandle - phandle of interrupt controller this template is for
+      irq_id_pos - the position of irq id in interrupt specifier array
+                   for interrupt controller referenced by phandle.
+      templ_data - is an array of u32 values (could be empty) in the same
+                   format as interrupt specifier for interrupt controller
+                   referenced by phandle but with omitted irq id field.
+
+- interrupt-ranges: list of entries that specifies secure side to kernel
+  IRQs mapping.
+
+  Each entry in the "interrupt-ranges" list has the following format:
+    <beg end templ_idx>
+      beg - first entry in this range
+      end - last entry in this range
+      templ_idx  - index of entry in "interrupt-templates" property
+                   that must be used as a template for all interrupts
+                   in this range
+
+Example:
+{
+	gic: interrupt-controller@50041000 {
+		compatible = "arm,gic-400";
+		#interrupt-cells = <3>;
+		interrupt-controller;
+		...
+	};
+	...
+	IPI: interrupt-controller {
+		compatible = "android,CustomIPI";
+		#interrupt-cells = <1>;
+		interrupt-controller;
+	};
+	...
+	trusty {
+		compatible = "android,trusty-smc-v1";
+		ranges;
+		#address-cells = <2>;
+		#size-cells = <2>;
+
+		irq {
+			compatible = "android,trusty-irq-v1";
+			interrupt-templates = <&IPI 0>,
+					      <&gic 1 GIC_PPI 0>,
+					      <&gic 1 GIC_SPI 0>;
+			interrupt-ranges = < 0  15 0>,
+					   <16  31 1>,
+					   <32 223 2>;
+		};
+	}
+}
+
+Must be a child of the node that provides the trusty std/fast call interface.

Documentation/devicetree/bindings/trusty/trusty-smc.txt

@@ -0,0 +1,6 @@
+Trusty smc interface
+
+Trusty is running in secure mode on the same (arm) cpu(s) as the current os.
+
+Required properties:
+- compatible: "android,trusty-smc-v1"

Documentation/doc-guide/sphinx.rst

@@ -48,13 +48,14 @@ or ``virtualenv``, depending on how your distribution packaged Python 3.
       on the Sphinx version, it should be installed separately,
       with ``pip install sphinx_rtd_theme``.
 
-In summary, if you want to install Sphinx version 2.4.4, you should do::
+In summary, if you want to install the latest version of Sphinx, you
+should do::
 
-       $ virtualenv sphinx_2.4.4
-       $ . sphinx_2.4.4/bin/activate
-       (sphinx_2.4.4) $ pip install -r Documentation/sphinx/requirements.txt
+       $ virtualenv sphinx_latest
+       $ . sphinx_latest/bin/activate
+       (sphinx_latest) $ pip install -r Documentation/sphinx/requirements.txt
 
-After running ``. sphinx_2.4.4/bin/activate``, the prompt will change,
+After running ``. sphinx_latest/bin/activate``, the prompt will change,
 in order to indicate that you're using the new environment. If you
 open a new shell, you need to rerun this command to enter again at
 the virtual environment before building the documentation.