From: Karunika Choo <karunika.choo@arm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: dri-devel@lists.freedesktop.org, nd@arm.com,
Boris Brezillon <boris.brezillon@collabora.com>,
Steven Price <steven.price@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
linux-kernel@vger.kernel.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 11/28] dt-bindings: gpu: panthor: Document AM system bindings
Date: Wed, 18 Nov 2026 10:35:05 +0000 [thread overview]
Message-ID: <90ddbc9b-c2ae-4132-9c89-57c877a79b72@arm.com> (raw)
In-Reply-To: <ede42635-1164-4190-b0bb-954125686108@arm.com>
On 13/11/2026 14:35, Karunika Choo wrote:
> On 12/11/2026 08:32, Krzysztof Kozlowski wrote:
>> On 11/11/2026 11:43, Karunika Choo wrote:
>>> On 11/11/2026 08:29, Krzysztof Kozlowski wrote:
>>>> On Tue, Nov 10, 2026 at 03:38:32PM +0000, Karunika Choo wrote:
>>>>> Mali 5th-Gen AM GPUs expose an AM_SYSTEM block for GPU-wide control and
>>>>> the AM_ASSIGN block for HW resource assignment outside the GPU
>>>>> job submission register window.
>>>>>
>>>>> Document the system node compatible, register and interrupt resources,
>>>>> GPU clock, and assignment properties for HW resource assignment.
>>>>>
>>>>> Signed-off-by: Karunika Choo <karunika.choo@arm.com>
>>>>> ---
>>>>> v2:
>>>>> - Add an optional AM_ASSIGN register range. Require this range when the
>>>>> assignments node is present.
>>>>> - Describe resource-group assignments for AXI buses, partitions, slices
>>>>> and access windows on partition-capable GPUs.
>>>>> - Allow gpu-arbitration child nodes and the #address-cells, #size-cells
>>>>> and ranges properties.
>>>>> - Remove the panthor-system node-name restriction.
>>>>> - Remove gpu-supply from the schema and example.
>>>>> - Add an example with assignments for partition-capable GPU with four
>>>>> resource groups.
>>>>> - Move the MAINTAINERS update to the GPU schema patch.
>>>>>
>>>>> .../bindings/gpu/arm,mali-gen5-am-system.yaml | 196 ++++++++++++++++++
>>>>> 1 file changed, 196 insertions(+)
>>>>> create mode 100644 Documentation/devicetree/bindings/gpu/arm,mali-gen5-am-system.yaml
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-gen5-am-system.yaml b/Documentation/devicetree/bindings/gpu/arm,mali-gen5-am-system.yaml
>>>>> new file mode 100644
>>>>> index 0000000000000..9e0477b8b723a
>>>>> --- /dev/null
>>>>> +++ b/Documentation/devicetree/bindings/gpu/arm,mali-gen5-am-system.yaml
>>>>> @@ -0,0 +1,196 @@
>>>>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>>>>> +# Copyright 2026 ARM Limited. All rights reserved.
>>>>> +%YAML 1.2
>>>>> +---
>>>>> +$id: http://devicetree.org/schemas/gpu/arm,mali-gen5-am-system.yaml#
>>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>>>> +
>>>>> +title: ARM Mali 5th-Gen GPU System Device
>>>>> +
>>>>> +maintainers:
>>>>> + - Liviu Dudau <liviu.dudau@arm.com>
>>>>> + - Boris Brezillon <boris.brezillon@collabora.com>
>>>>> +
>>>>> +properties:
>>>>> + compatible:
>>>>> + items:
>>>>> + - const: arm,mali-gen5-am-system
>>>>> +
>>>>> + reg:
>>>>> + minItems: 1
>>>>> + maxItems: 2
>>>>
>>>> Why is this flexible? There is no description in the binding which would
>>>> explain oddities in choices of hardware representation.
>>>
>>> I will restore the description that was previously asked to be dropped.
>>
>> Hm, let me open the cover letter to find lore link to previous
>> discussion and check... ah wait, no cover letter!
>>
>>>
>>>>> +
>>>>> + reg-names:
>>>>> + minItems: 1
>>>>> + items:
>>>>> + - const: system
>>>>> + - const: assign
>>>>> +
>>>>> + interrupts:
>>>>> + maxItems: 1
>>>>> +
>>>>> + clocks:
>>>>> + maxItems: 1
>>>>> +
>>>>> + dma-coherent: true
>>>>> +
>>>>> + "#address-cells": true
>>>>> +
>>>>> + "#size-cells": true
>>>>
>>>> Both need to be const or enum.
>>>>
>>>>> +
>>>>> + ranges: true
>>>>> +
>>>>> + assignments:
>>>>
>>>> Do not mix nodes with and without bus addressing. That's mess.
>>>
>>> Hi, I was asked to use a more generic DT such that should the
>>
>> By whom?
>>
>>> hardware registers change in the future we can still retain
>>> some compatibility. Is it necessarily a problem?
>>
>> Bindings are not generic, but specific.
>
> Apologies, this was discussed internally with a Panthor maintainer
> previously. Would the following example DT be more acceptable?
>
> --8<-------------------------------------------
> panthor_system: gpu-system@68000000 {
> compatible = "example-vendor,example-soc-mali-system", "arm,mali-gen5-am-system";
> reg = <0x68000000 0x10000>,
> <0x68010000 0x10000>;
> reg-names = "system", "assign";
> interrupts = <GIC_SPI 168 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&mali_gpu_clk>;
> dma-coherent;
> arm,am-resource-group-bus = <0x1100>;
> arm,am-partition-resource-group = <0x3210>;
> arm,am-slice-resource-group = <0x33221100>;
> arm,am-aw-resource-group = <0x33332222 0x11110000 0x0 0x0>;
>
> panthor_arbitration: gpu-arbitration@68040000 {
> ...
> };
> };
> -->8-------------------------------------------
>
Hello, thank you for your patience. Would the following layout address
your concern about mixing bus-addressed devices and non-addressed
configuration nodes?
The resource-group and partition configurations are moved into a separate
gpu-assignments node outside the MMIO hierarchy. This node would be
documented in a separate arm,mali-gen5-am-assignments.yaml.
Each entry in the assignment property contains a configuration-node
phandle followed by the hardware resource-group or partition index.
The example below illustrates the proposed structure.
--8<-------------------------------------------
/* Will be documented in a separate arm,mali-gen5-am-assignments.yaml */
gpu-assignments {
compatible = "arm,mali-gen5-am-assignments";
rg0: resource-group-0 {
arm,axi-bus = <0>;
arm,partition-mask = <0x1>;
arm,slice-mask = <0x3>;
arm,access-window-mask = <0x3>;
};
rg1: resource-group-1 {
arm,axi-bus = <0>;
arm,partition-mask = <0x2>;
arm,slice-mask = <0xc>;
arm,access-window-mask = <0x4>;
};
pc0: partition-0 {
arm,access-window-mask = <0x3>;
arm,slice-mask = <0x3>;
};
pc1: partition-1 {
arm,access-window-mask = <0x4>;
arm,slice-mask = <0x8>;
};
};
gpu-system@68000000 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "vendor,soc1-mali-system", "arm,mali-gen5-am-system";
reg = <0x68000000 0x10000>, <0x68010000 0x10000>;
reg-names = "system", "assign";
interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&mali_gpu_clk>;
arm,resource-assignments = <&rg0 0>, <&rg1 1>;
dma-coherent;
ranges;
gpu-arbitration@68040000 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "vendor,soc1-mali-arbitration", "arm,mali-gen5-am-arbitration";
reg = <0x68040000 0x10000>,
<0x68050000 0x10000>,
<0x680C0000 0x10000>,
<0x680D0000 0x10000>;
reg-names = "pc0", "pc1", "rg0", "rg1";
interrupts = <GIC_SPI 17 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 21 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 22 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "pc0", "pc1", "rg0", "rg1";
arm,partition-assignments = <&pc0 0>, <&pc1 1>;
ranges;
/* access-window 0 */
gpu@68100000 {
compatible = "vendor,soc1-mali", "arm,mali-gen5-am";
reg = <0x68100000 0x480000>;
interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "job", "mmu", "gpu";
iommus = <&smmu_700 0x0>, <&smmu_700 0x1>;
clocks = <&gpu_core_clk>;
};
/* access-window 1 */
gpu@68580000 {
compatible = "vendor,soc1-mali", "arm,mali-gen5-am";
reg = <0x68580000 0x480000>;
interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "job", "mmu", "gpu";
iommus = <&smmu_700 0x0>, <&smmu_700 0x1>;
clocks = <&gpu_core_clk>;
};
/* access-window 2 */
gpu@68a00000 {
compatible = "vendor,soc1-mali", "arm,mali-gen5-am";
reg = <0x68a00000 0x480000>;
interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "job", "mmu", "gpu";
iommus = <&smmu_700 0x0>, <&smmu_700 0x1>;
clocks = <&gpu_core_clk>;
};
};
};
-->8-------------------------------------------
Kind regards,
Karunika
>> ...
>>
>>>>> +patternProperties:
>>>>> + '^gpu-arbitration@[a-f0-9]+$':
>>>>> + $ref: arm,mali-gen5-am-arbitration.yaml#
>>>>
>>>> There is no such file. You did not really test it.
>>>
>>> Sorry, this was included from a later patch that
>>> introduces this file. I will move it there in v3.
>>>
>>>>
>>>>> +
>>>>> +required:
>>>>> + - compatible
>>>>> + - reg
>>>>> + - reg-names
>>>>> + - interrupts
>>>>> + - clocks
>>>>> +
>>>>> +additionalProperties: false
>>>>
>>>> This goes after allOf: block.
>>>>
>>>>> +
>>>>> +allOf:
>>>>> + - if:
>>>>> + required:
>>>>> + - assignments
>>>>> + then:
>>>>> + properties:
>>>>> + reg:
>>>>> + minItems: 2
>>>>> + reg-names:
>>>>> + minItems: 2
>>>>> +
>>>>> +examples:
>>>>> + - |
>>>>> + #include <dt-bindings/interrupt-controller/irq.h>
>>>>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>>>>> +
>>>>> + gpu-system@68000000 {
>>>>> + compatible = "arm,mali-gen5-am-system";
>>>>> + reg = <0x68000000 0x10000>;
>>>>> + reg-names = "system";
>>>>> + interrupts = <GIC_SPI 168 IRQ_TYPE_LEVEL_HIGH>;
>>>>> + clocks = <&mali_gpu_clk>;
>>>>> + };
>>>>> + - |
>>>>> + #include <dt-bindings/interrupt-controller/irq.h>
>>>>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>>>>> +
>>>>> + gpu-system@68000000 {
>>>>> + compatible = "arm,mali-gen5-am-system";
>>>>> + reg = <0x68000000 0x10000>, <0x68010000 0x10000>;
>>>>> + reg-names = "system", "assign";
>>>>> + interrupts = <GIC_SPI 168 IRQ_TYPE_LEVEL_HIGH>;
>>>>> + clocks = <&mali_gpu_clk>;
>>>>> +
>>>>> + assignments {
>>>>> + #address-cells = <1>;
>>>>> + #size-cells = <0>;
>>>>> +
>>>>> + resource-group@0 {
>>>>> + reg = <0>;
>>>>> + arm,axi-bus = <0>;
>>>>> + arm,partition-mask = <0x1>;
>>>>> + arm,slice-mask = <0x3>;
>>>>> + arm,access-window-mask = <0xf>;
>>>>> + };
>>>>> +
>>>>> + resource-group@1 {
>>>>> + reg = <1>;
>>>>> + arm,axi-bus = <0>;
>>>>> + arm,partition-mask = <0x2>;
>>>>> + arm,slice-mask = <0xc>;
>>>>> + arm,access-window-mask = <0xf0>;
>>>>> + };
>>>>> +
>>>>> + resource-group@2 {
>>>>> + reg = <2>;
>>>>> + arm,axi-bus = <1>;
>>>>> + arm,partition-mask = <0x4>;
>>>>> + arm,slice-mask = <0x30>;
>>>>> + arm,access-window-mask = <0xf00>;
>>>>> + };
>>>>> +
>>>>> + resource-group@3 {
>>>>> + reg = <3>;
>>>>> + arm,axi-bus = <1>;
>>>>> + arm,partition-mask = <0x8>;
>>>>> + arm,slice-mask = <0xc0>;
>>>>> + arm,access-window-mask = <0xf000>;
>>>>> + };
>>>>
>>>> Your example is incomplete.
>>>
>>> Could you clarify what specifically is missing?
>>
>> ll the properties you added in the binding.
>>
>> Best regards,
>> Krzysztof
> Thanks. I'll add that in v3.
>
> Kind regards,
> Karunika
next prev parent reply other threads:[~2026-11-18 10:35 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 20:44 [PATCH v1 00/27] drm/panthor: Add Mali v15 virtualization support Karunika Choo
2026-09-22 20:44 ` [PATCH v1 01/27] drm/panthor: Ignore -EOPNOTSUPP for shader-present nvmem lookup Karunika Choo
2026-10-28 15:51 ` Liviu Dudau
2026-09-22 20:44 ` [PATCH v1 02/27] drm/panthor: Move register access helpers out of panthor_device.h Karunika Choo
2026-10-28 15:52 ` Liviu Dudau
2026-09-22 20:44 ` [PATCH v1 03/27] drm/panthor: Parse and store GPU_ID fields Karunika Choo
2026-10-28 15:57 ` Liviu Dudau
2026-09-22 20:44 ` [PATCH v1 04/27] drm/panthor: Add 64-bit GPU_ID decoding for v15 GPUs Karunika Choo
2026-09-22 23:23 ` Deborah Brouwer
2026-10-28 15:58 ` Liviu Dudau
2026-09-22 20:44 ` [PATCH v1 05/27] drm/panthor: Move register base offsets to the HW description Karunika Choo
2026-10-28 16:03 ` Liviu Dudau
2026-09-22 20:45 ` [PATCH v1 06/27] drm/panthor: Derive MMU AS register addresses from base and stride Karunika Choo
2026-10-28 16:06 ` Liviu Dudau
2026-09-22 20:45 ` [PATCH v1 07/27] dt-bindings: gpu: mali-valhall-csf: Add Mali Gen5 AM compatible Karunika Choo
2026-09-28 10:02 ` Krzysztof Kozlowski
2026-09-22 20:45 ` [PATCH v1 08/27] drm/panthor: Add Mali v15 hardware support Karunika Choo
2026-10-28 13:21 ` Liviu Dudau
2026-10-28 16:20 ` Liviu Dudau
2026-09-22 20:45 ` [PATCH v1 09/27] drm/panthor: Skip devfreq when no OPP table is present Karunika Choo
2026-10-28 16:26 ` Liviu Dudau
2026-11-13 14:35 ` [PATCH v2 11/28] dt-bindings: gpu: panthor: Document AM system bindings Karunika Choo
2026-11-18 10:35 ` Karunika Choo [this message]
2026-09-22 20:45 ` [PATCH v1 10/27] dt-bindings: gpu: panthor: Document panthor-system bindings Karunika Choo
2026-09-28 10:05 ` Krzysztof Kozlowski
2026-09-22 20:45 ` [PATCH v1 11/27] drm/panthor: Add AM_SYSTEM platform driver Karunika Choo
2026-09-22 20:45 ` [PATCH v1 12/27] dt-bindings: gpu: panthor: Document panthor-arbitration bindings Karunika Choo
2026-09-28 10:06 ` Krzysztof Kozlowski
2026-09-22 20:45 ` [PATCH v1 13/27] drm/panthor: Add AM_PARTITION_CONTROL support Karunika Choo
2026-09-22 20:45 ` [PATCH v1 14/27] drm/panthor: Add AM message helpers Karunika Choo
2026-09-22 20:45 ` [PATCH v1 15/27] drm/panthor: Add AM_RESOURCE_GROUP support Karunika Choo
2026-09-22 20:45 ` [PATCH v1 16/27] drm/panthor: Add arbitration scheduler Karunika Choo
2026-09-22 20:45 ` [PATCH v1 17/27] drm/panthor: Route arbitration events Karunika Choo
2026-09-22 20:45 ` [PATCH v1 18/27] dt-bindings: gpu: panthor: Document AW assignment DT property Karunika Choo
2026-09-28 10:06 ` Krzysztof Kozlowski
2026-09-22 20:45 ` [PATCH v1 19/27] drm/panthor: Add AW assignment tracking Karunika Choo
2026-09-22 20:45 ` [PATCH v1 20/27] drm/panthor: Handle partition control INVALID_COMMAND interrupt Karunika Choo
2026-09-22 20:45 ` [PATCH v1 21/27] drm/panthor: Request AW to yield GPU access on idle Karunika Choo
2026-09-22 20:45 ` [PATCH v1 22/27] drm/panthor: Add access-window support Karunika Choo
2026-09-22 20:45 ` [PATCH v1 23/27] drm/panthor: Synchronize HW component PM transitions Karunika Choo
2026-09-22 20:45 ` [PATCH v1 24/27] drm/panthor: Route HW component PM through access windows Karunika Choo
2026-09-22 20:45 ` [PATCH v1 25/27] drm/panthor: Tolerate access-window loss during HW waits Karunika Choo
2026-09-22 20:45 ` [PATCH v1 26/27] drm/panthor: Prevent missed post-yield cleanup due to reset Karunika Choo
2026-09-22 20:45 ` [PATCH v1 27/27] drm/panthor: Release GPU access immediately for out-of-band grants Karunika Choo
2026-11-10 15:38 [PATCH v2 00/28] drm/panthor: Add Mali v15 virtualization support Karunika Choo
2026-11-10 15:38 ` [PATCH v2 01/28] drm/panthor: Ignore -EOPNOTSUPP for shader-present nvmem lookup Karunika Choo
2026-11-10 15:38 ` [PATCH v2 02/28] drm/panthor: Rename neural accelerator feature macro to NX Karunika Choo
2026-11-10 15:38 ` [PATCH v2 03/28] drm/panthor: Move register access helpers out of panthor_device.h Karunika Choo
2026-11-10 15:38 ` [PATCH v2 04/28] drm/panthor: Parse and store GPU_ID fields Karunika Choo
2026-11-10 15:38 ` [PATCH v2 05/28] drm/panthor: Add 64-bit GPU_ID decoding for v15 GPUs Karunika Choo
2026-11-10 15:38 ` [PATCH v2 06/28] drm/panthor: Move register base offsets to the HW description Karunika Choo
2026-11-10 15:38 ` [PATCH v2 07/28] drm/panthor: Derive MMU AS register addresses from base and stride Karunika Choo
2026-11-10 15:38 ` [PATCH v2 08/28] dt-bindings: gpu: mali-gen5-am: Add Mali 5th-Gen AM schema Karunika Choo
2026-11-11 8:33 ` Krzysztof Kozlowski
2026-11-11 10:32 ` Karunika Choo
2026-11-11 10:41 ` Krzysztof Kozlowski
2026-11-11 11:04 ` Karunika Choo
2026-11-12 8:36 ` Krzysztof Kozlowski
2026-11-10 15:38 ` [PATCH v2 09/28] drm/panthor: Add Mali v15 hardware support Karunika Choo
2026-11-10 15:38 ` [PATCH v2 10/28] drm/panthor: Skip devfreq when no OPP table is present Karunika Choo
2026-11-10 15:38 ` [PATCH v2 11/28] dt-bindings: gpu: panthor: Document AM system bindings Karunika Choo
2026-11-11 8:29 ` Krzysztof Kozlowski
2026-11-11 10:43 ` Karunika Choo
2026-11-12 8:32 ` Krzysztof Kozlowski
2026-11-10 15:38 ` [PATCH v2 12/28] drm/panthor: Add AM_SYSTEM platform driver Karunika Choo
2026-11-10 15:38 ` [PATCH v2 13/28] dt-bindings: gpu: panthor: Document panthor-arbitration bindings Karunika Choo
2026-11-10 15:38 ` [PATCH v2 14/28] drm/panthor: Add AM_PARTITION_CONTROL support Karunika Choo
2026-11-11 5:43 ` kernel test robot
2026-11-10 15:38 ` [PATCH v2 15/28] drm/panthor: Add AM message helpers Karunika Choo
2026-11-10 15:38 ` [PATCH v2 16/28] drm/panthor: Add AM_RESOURCE_GROUP support Karunika Choo
2026-11-11 8:30 ` kernel test robot
2026-11-10 15:38 ` [PATCH v2 17/28] drm/panthor: Add arbitration scheduler Karunika Choo
2026-11-11 0:43 ` kernel test robot
2026-11-10 15:38 ` [PATCH v2 18/28] drm/panthor: Route arbitration events Karunika Choo
2026-11-10 15:38 ` [PATCH v2 19/28] drm/panthor: Add AW assignment tracking Karunika Choo
2026-11-10 15:38 ` [PATCH v2 20/28] drm/panthor: Handle partition control INVALID_COMMAND interrupt Karunika Choo
2026-11-10 15:38 ` [PATCH v2 21/28] drm/panthor: Request AW to yield GPU access on idle Karunika Choo
2026-11-10 15:38 ` [PATCH v2 22/28] drm/panthor: Add access-window support Karunika Choo
2026-11-10 15:38 ` [PATCH v2 23/28] drm/panthor: Synchronize HW component PM transitions Karunika Choo
2026-11-10 15:38 ` [PATCH v2 24/28] drm/panthor: Quiesce scheduler tick during system suspend Karunika Choo
2026-11-10 15:38 ` [PATCH v2 25/28] drm/panthor: Route HW component PM through access windows Karunika Choo
2026-11-10 15:38 ` [PATCH v2 26/28] drm/panthor: Tolerate access-window loss during HW waits Karunika Choo
2026-11-10 15:38 ` [PATCH v2 27/28] drm/panthor: Prevent missed post-yield cleanup due to reset Karunika Choo
2026-11-10 15:38 ` [PATCH v2 28/28] drm/panthor: Reset partitions before starting arbitration Karunika Choo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90ddbc9b-c2ae-4132-9c89-57c877a79b72@arm.com \
--to=karunika.choo@arm.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®