On Mon, 03 Jun 2024 02:28:55 -0400, Alexandre Messier wrote:
> Add an initial device tree to support the HTC One (M8) smartphone,
> aka "htc,m8".
>
> Signed-off-by: Alexandre Messier
> ---
> Alexandre Messier (2):
> dt-bindings: arm: qcom: add HTC One (M8)
> ARM: dts: qcom: Add
On Tue, May 21, 2024 at 02:24:54PM +0200, Arnaud Pouliquen wrote:
> Add the "st,proc-id" property allowing to identify the remote processor.
> This ID is used to define an unique ID, common between Linux, U-boot and
> OP-TEE to identify a coprocessor.
> This ID will be used in request to OP-TEE
On Fri, 10 May 2024 14:27:07 +0200, Luca Weiss wrote:
> Validated on Fairphone 5 (QCM6490) smartphone by using DisplayPort over
> USB-C audio, connected to a TV, with a basic UCM to enable
> 'DISPLAY_PORT_RX Audio Mixer MultiMedia1':
>
c/qcom,smd-edge.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring (Arm)
,smp2p.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring (Arm)
On Wed, Apr 24, 2024 at 07:21:51PM +0200, Luca Weiss wrote:
> The qcom,ipc-N properties are essentially providing a reference to a
> mailbox, so allow using the mboxes property to do the same in a more
> structured way.
Can we mark qcom,ipc-N as deprecated then?
> Since multiple SMSM hosts are
On Wed, 24 Apr 2024 20:42:27 +0200, Duje Mihanović wrote:
> Hello,
>
> This series adds initial support for the Marvell PXA1908 SoC and
> "samsung,coreprimevelte", a smartphone using the SoC.
>
> USB works and the phone can boot a rootfs from an SD card, but there are
> some warnings in the
On Wed, 24 Apr 2024 14:06:09 -0500, Andrew Davis wrote:
> From: Hari Nagalla
>
> K3 AM64x SoC has a Cortex M4F subsystem in the MCU voltage domain.
> The remote processor's life cycle management and IPC mechanisms are
> similar across the R5F and M4F cores from remote processor driver
> point
ly is)
range for dimensions are global. So if there's not correct dimensions
for a property, the tools aren't going to decode it properly.
Rob
On Sun, 07 Apr 2024 11:05:10 +0200, Stanislav Jakubek wrote:
> Document the Motorola Moto G (2013), which is a smartphone based
> on the Qualcomm MSM8226 SoC.
>
> Acked-by: Krzysztof Kozlowski
> Signed-off-by: Stanislav Jakubek
> ---
> Changes in V3:
> - no changes
>
> Changes in V2:
> -
On Tue, 02 Apr 2024 22:55:36 +0200, Duje Mihanović wrote:
> Hello,
>
> This series adds initial support for the Marvell PXA1908 SoC and
> "samsung,coreprimevelte", a smartphone using the SoC.
>
> USB works and the phone can boot a rootfs from an SD card, but there are
> some warnings in the
e changed, 1 deletion(-)
>
Acked-by: Rob Herring
On Sun, 24 Mar 2024 15:03:59 +0100, Stanislav Jakubek wrote:
> Document the Motorola Moto G (2013), which is a smartphone based
> on the Qualcomm MSM8226 SoC.
>
> Signed-off-by: Stanislav Jakubek
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
On Thu, 14 Mar 2024 20:00:13 +0100, Luca Weiss wrote:
> Add the dts for "hlte" which is a phablet from 2013.
>
> Signed-off-by: Luca Weiss
> ---
> Changes in v2:
> - Correct property order (Konrad)
> - Pick up tags
> - Link to v1:
>
using memblock.
>
> Signed-off-by: Oreoluwa Babatunde
> ---
> arch/sh/kernel/setup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Rob Herring
On Sun, 10 Mar 2024 15:13:35 +0100, Luca Weiss wrote:
> Add the dts for "hlte" which is a phablet from 2013.
>
> Signed-off-by: Luca Weiss
> ---
> Adam Honse (1):
> ARM: dts: qcom: msm8974: Add Samsung Galaxy Note 3
>
> Luca Weiss (1):
> dt-bindings: arm: qcom: Add Samsung Galaxy
On Fri, Mar 01, 2024 at 04:42:25PM +, abdellatif.elkhl...@arm.com wrote:
> From: Abdellatif El Khlifi
>
> introduce remoteproc support for Arm remote processors
>
> The supported remote processors are those that come with a reset
> control register and a reset status register. The driver
e changed, 1 deletion(-)
>
Acked-by: Rob Herring
s enough, so
> drop the "unstable" remark and expect usual ABI rules.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> .../devicetree/bindings/remoteproc/ti,davinci-rproc.txt| 3 ---
> 1 file changed, 3 deletions(-)
>
Acked-by: Rob Herring
e/bindings/clock/ti/interface.txt| 2 --
> Documentation/devicetree/bindings/clock/ti/mux.txt | 2 --
> 12 files changed, 24 deletions(-)
>
Acked-by: Rob Herring
e/bindings/clock/keystone-pll.txt | 2 --
> 2 files changed, 4 deletions(-)
>
Acked-by: Rob Herring
On Fri, 23 Feb 2024 22:28:42 +0100, Pavel Machek wrote:
> Add binding for anx7688 usb type-c bridge. I don't have a datasheet,
> but I did best I could.
>
> Signed-off-by: Pavel Machek
>
> ---
>
> v2: implement review feedback
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m
ional branch, as the
> property is already part of the condition test.
> ---
> .../bindings/remoteproc/st,stm32-rproc.yaml | 51 ++++---
> 1 file changed, 43 insertions(+), 8 deletions(-)
>
Reviewed-by: Rob Herring
On Sun, Feb 11, 2024 at 10:35:54AM +0100, Karel Balej wrote:
> From: Karel Balej
>
> Marvell 88PM88X PMICs provide onkey functionality -- add the bindings.
>
> Signed-off-by: Karel Balej
> ---
>
> Notes:
> RFC v2:
> - Add wakeup-source property and reference onkey schema from MFD.
>
On Sun, Feb 11, 2024 at 10:35:51AM +0100, Karel Balej wrote:
> From: Karel Balej
>
> Marvell 88PM886 is a PMIC with several subdevices such as onkey,
> regulators or battery and charger. It comes in at least two revisions,
> A0 and A1 -- only A1 is described here at the moment.
>
>
On Tue, Feb 13, 2024 at 02:37:49PM -0600, Tanmay Shah wrote:
> Hello,
>
> Thanks for reviews please find my comments below.
>
> On 2/13/24 1:20 PM, Rob Herring wrote:
> > On Tue, 13 Feb 2024 09:54:48 -0800, Tanmay Shah wrote:
> > > From: Radhey Shyam Pandey
&
On Tue, 13 Feb 2024 09:54:48 -0800, Tanmay Shah wrote:
> From: Radhey Shyam Pandey
>
> Introduce bindings for TCM memory address space on AMD-xilinx Zynq
> UltraScale+ platform. It will help in defining TCM in device-tree
> and make it's access platform agnostic and data-driven.
>
>
On Mon, 05 Feb 2024 10:51:38 +0100, Luca Weiss wrote:
> Add the PBS (Programmable Boot Sequencer) to the list of devices.
>
> Signed-off-by: Luca Weiss
> ---
> Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml | 4
> 1 file changed, 4 insertions(+)
>
My bot found errors running
On Fri, Feb 02, 2024 at 11:55:34AM -0600, Hari Nagalla wrote:
> K3 AM64x SoC has a Cortex M4F subsystem in the MCU voltage domain.
> The remote processor's life cycle management and IPC mechanisms are
> similar across the R5F and M4F cores from remote processor driver
> point of view. However,
On Fri, 02 Feb 2024 11:55:34 -0600, Hari Nagalla wrote:
> K3 AM64x SoC has a Cortex M4F subsystem in the MCU voltage domain.
> The remote processor's life cycle management and IPC mechanisms are
> similar across the R5F and M4F cores from remote processor driver
> point of view. However, there
v4:
> * Reword commit description to mention how this IC differs from the
> already supported.
>
> .../devicetree/bindings/input/touchscreen/imagis,ist3038c.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring
On Thu, Jan 18, 2024 at 11:04:31AM +0100, Arnaud Pouliquen wrote:
> The "st,stm32mp1-m4-tee" compatible is utilized in a system configuration
> where the Cortex-M4 firmware is loaded by the Trusted execution Environment
> (TEE).
> For instance, this compatible is used in both the Linux and OP-TEE
;
> [1]
> https://elixir.bootlin.com/linux/v6.7.1/source/Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml#L54
>
> [2]
> https://elixir.bootlin.com/linux/v6.7.1/source/Documentation/devicetree/bindings/net/qcom,ipa.yaml#L129
> (that's a bit different)
>
> [3] https://lore.kernel.org/linux-devicetree/20240124103623.GJ4906@thinkpad/
>
> @Rob,
> Any general guidance for this and Qualcomm?
I think we have cases using compatible already as well. Either way is
fine with me.
Rob
On Mon, Jan 15, 2024 at 02:52:47PM +0100, Arnaud Pouliquen wrote:
> The "st,stm32mp1-m4-tee" compatible is utilized in a system configuration
> where the Cortex-M4 firmware is loaded by the Trusted execution Environment
> (TEE).
> This compatible is used in both the Linux and OP-TEE device-tree.
>
interrupt-controller;
> #interrupt-cells = <1>;
> +
> +onkey {
> + compatible = "marvell,88pm88x-onkey";
> +};
Why do you need this? You have no properties for it. The parent driver
can instantiate child drivers. You don't need a DT node for that.
Rob
On Sun, Dec 17, 2023 at 02:16:59PM +0100, Karel Balej wrote:
> From: Karel Balej
>
> Marvell 88PM880 and 88PM886 are two similar PMICs with mostly matching
> register mapping and subdevices such as onkey, regulators or battery and
> charger. Both seem to come in two revisions which seem to be
On Sun, 17 Dec 2023 14:17:01 +0100, Karel Balej wrote:
> From: Karel Balej
>
> Marvell 88PM88X PMICs provide onkey functionality. Document it.
>
> Signed-off-by: Karel Balej
> ---
> .../bindings/input/marvell,88pm88x-onkey.yaml | 30 +++
>
On Sun, 17 Dec 2023 14:16:59 +0100, Karel Balej wrote:
> From: Karel Balej
>
> Marvell 88PM880 and 88PM886 are two similar PMICs with mostly matching
> register mapping and subdevices such as onkey, regulators or battery and
> charger. Both seem to come in two revisions which seem to be
On Thu, Dec 14, 2023 at 9:45 AM Alexandru Elisei
wrote:
>
> Hi,
>
> On Wed, Dec 13, 2023 at 02:30:42PM -0600, Rob Herring wrote:
> > On Wed, Dec 13, 2023 at 11:44 AM Alexandru Elisei
> > wrote:
> > >
> > > On Wed, Dec 13, 2023 at 11:22:17AM -0600, Rob H
On Wed, Dec 13, 2023 at 11:44 AM Alexandru Elisei
wrote:
>
> On Wed, Dec 13, 2023 at 11:22:17AM -0600, Rob Herring wrote:
> > On Wed, Dec 13, 2023 at 8:51 AM Alexandru Elisei
> > wrote:
> > >
> > > Hi,
> > >
> > > On Wed, Dec 13, 2023 at 08
On Wed, Dec 13, 2023 at 8:51 AM Alexandru Elisei
wrote:
>
> Hi,
>
> On Wed, Dec 13, 2023 at 08:06:44AM -0600, Rob Herring wrote:
> > On Wed, Dec 13, 2023 at 7:05 AM Alexandru Elisei
> > wrote:
> > >
> > > Hi Rob,
> > >
> > >
On Wed, Dec 13, 2023 at 7:05 AM Alexandru Elisei
wrote:
>
> Hi Rob,
>
> On Tue, Dec 12, 2023 at 12:44:06PM -0600, Rob Herring wrote:
> > On Tue, Dec 12, 2023 at 10:38 AM Alexandru Elisei
> > wrote:
> > >
> > > Hi Rob,
> > >
> > &g
On Tue, Dec 12, 2023 at 10:38 AM Alexandru Elisei
wrote:
>
> Hi Rob,
>
> Thank you so much for the feedback, I'm not very familiar with device tree,
> and any comments are very useful.
>
> On Mon, Dec 11, 2023 at 11:29:40AM -0600, Rob Herring wrote:
> > On Sun, Nov 19,
gt; +
> + ret = tag_storage_of_flat_read_u32(node, "block-size",
> _size_bytes);
> + if (ret || block_size_bytes == 0) {
> + pr_err("Invalid or missing 'block-size' property");
> + return -EINVAL;
> + }
> + region->block_size = get_block_size_pages(block_size_bytes);
> + if (range_len(tag_range) % region->block_size != 0) {
> + pr_err("Tag storage region size 0x%llx is not a multiple of
> block size %u",
> + PFN_PHYS(range_len(tag_range)), region->block_size);
> + return -EINVAL;
> + }
> +
> + ret = tag_storage_of_flat_read_u32(mem_node, "numa-node-id", );
I was going to say we already have a way to associate memory nodes
other nodes using "numa-node-id", so the "memory" phandle property is
somewhat redundant. Maybe the tag node should have a numa-node-id.
With that, it looks like you don't even need to access the /memory
node. Avoiding that would be good for 2 reasons. It avoids parsing
memory nodes twice and it's not the kernel's job to validate the DT.
Really, if you want memory info, you should use memblock to get it
because all the special cases of memory layout are handled. For
example you can have memory nodes with multiple 'reg' entries or
multiple memory nodes or both, and then some of those could be
contiguous.
Rob
On Fri, 24 Nov 2023 10:21:21 +0100, Krzysztof Kozlowski wrote:
> Use only one and exactly one space around '=' in DTS example.
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
>
> Merging idea: Rob's DT.
> Should apply cleanly on Rob's for-next.
> ---
>
his in the data-lanes description.
>
> Signed-off-by: Luca Weiss
> ---
> Documentation/devicetree/bindings/usb/fcs,fsa4480.yaml | 18
> ++
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
Reviewed-by: Rob Herring
B-C
> Codec |-- AUX+ --| |-- SBU2 ---> connected
> |-- AUX- --| |
> __| |_|
>
> (thanks to Neil Armstrong for this ASCII art)
>
> Signed-off-by: Luca Weiss
> ---
> .../devicetree/bindings/usb/fcs,fsa4480.yaml | 29
> +-
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring
On Fri, 13 Oct 2023 15:08:49 -0500, Rob Herring wrote:
> The common reserved-memory bindings have recently been copied from the
> kernel tree into dtschema. The preference is to host common, stable
> bindings in dtschema. As reserved-memory is documented in the DT Spec,
> it meets
On Sat, 21 Oct 2023 09:16:19 +0200, David Wronek wrote:
> Add a compatible for the Qualcomm Kryo 465 found in SM7125.
>
> Signed-off-by: David Wronek
> ---
> Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Applied, thanks!
; };
> + { compatible = "qcom,kryo465"; };
> + { compatible = "qcom,kryo465"; };
> + { compatible = "qcom,kryo465"; };
> + { compatible = "qcom,kryo465"; };
This compatible is not documented. Please add it.
Rob
On Mon, Oct 16, 2023 at 04:32:55PM +0200, Neil Armstrong wrote:
> On 16/10/2023 16:22, Rob Herring wrote:
> > On Fri, Oct 13, 2023 at 01:38:05PM +0200, Luca Weiss wrote:
> > > Allow specifying data-lanes to reverse the SBU muxing orientation where
> > > neces
escription:
> + Specifies how the AUX+/- lines are connected to SBU1/2.
Doesn't this depend on the connector orientation? Or it is both that and
the lines can be swapped on the PCB?
Seems like an abuse of data-lanes which already has a definition which
is not about swapping + and - differential lanes.
Rob
-memory
schemas we depend on, so bump the minimum version to that. Otherwise,
references to these schemas will generate errors.
Signed-off-by: Rob Herring
---
Documentation/devicetree/bindings/Makefile| 2 +-
.../remoteproc/renesas,rcar-rproc.yaml| 2 +-
.../bindings/reserved-memory
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data. With this, adjust the includes to explicitly
include the correct headers.
Signed-off-by: Rob Herring
---
drivers/remoteproc/st_remoteproc.c | 14 --
1 file changed, 4 insertions(+), 10
it is not used, it
> > should be dropped, not changed...
>
> Okay, I will drop the label instead of updating it in v2.
Or just drop the patch and skip the trivial changes. If you want to fix
unused labels, fix it for the whole subsystem (mfd) or treewide.
Rob
On Thu, Sep 28, 2023 at 2:31 PM Mathieu Poirier
wrote:
>
> Hi Rob,
>
> On Tue, Sep 26, 2023 at 11:45:08AM -0500, Rob Herring wrote:
> > Just as unevaluatedProperties or additionalProperties are required at
> > the top level of schemas, they should (and will) also be req
Just as unevaluatedProperties or additionalProperties are required at
the top level of schemas, they should (and will) also be required for
child node schemas. That ensures only documented properties are
present for any node.
Signed-off-by: Rob Herring
---
Documentation/devicetree/bindings
additionalItems: true
> +
> + sram:
> +$ref: /schemas/types.yaml#/definitions/phandle-array
> +minItems: 1
> +maxItems: 4
> +items:
> + maxItems: 4
You are saying there are 1-4 entries and each entry is 4 cells. What's
in the 4 cells?
>From the description and example, looks like you only have 1 cell (a
phandle) so maxItems should be 1.
Your example should fail, but I'm not sure why it doesn't.
Rob
On Wed, 13 Sep 2023 06:16:41 -0500, Hari Nagalla wrote:
> K3 AM64x SoC has a Cortex M4F subsystem in the MCU voltage domain.
> The remote processor's life cycle management and IPC mechanisms are
> similar across the R5F and M4F cores from remote processor driver
> point of view. However, there
s a result, there's a pretty much random mix of those include
files used throughout the tree. In order to detangle these headers and
replace the implicit includes with struct declarations, users need to
explicitly include the correct includes.
Signed-off-by: Rob Herring
---
drivers/nvdimm/of_pmem.c |
On Mon, Apr 19, 2021 at 9:03 PM Leonardo Bras wrote:
>
> On Mon, 2021-04-19 at 20:39 -0500, Rob Herring wrote:
> > On Mon, Apr 19, 2021 at 7:35 PM Leonardo Bras wrote:
> > >
> > > On Mon, 2021-04-19 at 10:44 -0500, Rob Herring wrote:
> > > > On
On Tue, Apr 20, 2021 at 11:10 AM Ard Biesheuvel wrote:
>
> On Tue, 20 Apr 2021 at 17:54, Rob Herring wrote:
> >
> > On Tue, Apr 20, 2021 at 10:12 AM Alexandre TORGUE
> > wrote:
> > >
> > >
> > >
> > > On 4/20/21 4:45 PM, Rob Herr
0a000: clock-names: ['stmmaceth', 'mac-clk-tx', 'mac-clk-rx',
> 'eth-ck', 'ptp_ref', 'ethstp'] is too long
>
> Signed-off-by: Alexandre Torgue
>
Reviewed-by: Rob Herring
On Thu, 15 Apr 2021 12:10:28 +0200, Alexandre Torgue wrote:
> address-cells and size-cells can't be declared as "required" properties
> as they are not needed if subnodes don't have a "reg" entry.
>
> Signed-off-by: Alexandre Torgue
>
Acked-by: Rob Herring
On Thu, Apr 15, 2021 at 03:31:05PM +0800, Zhen Lei wrote:
> When there is more than one pl011 serial port present, the label property
> allows a custom name to be used for briefly describe the usage or position
> of each serial port.
>
> Without this "label" property, many dtbs_check warnings
t; 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring
the
device connector for a human to id. I can't really tell if that's the
case here. I don't see how 'gmacX' vs. 'ethX' maps to DSA master vs.
slave.
I don't think this should be handled within a specific driver either. If
we're going to have a way to name things, then fix it in
alloc_etherdev().
It can also be argued that device naming for userspace is a userspace
(udev) problem.
Rob
On Sun, Apr 18, 2021 at 07:49:51PM -0300, Lucas Stankus wrote:
> Add device tree binding documentation for AD7746 cdc in YAML format.
>
> Signed-off-by: Lucas Stankus
> ---
>
> A minor note about the adi,excitation-vdd-permille property. Jonathan
> suggested the name to be
tions(+), 2 deletions(-)
>
Acked-by: Rob Herring
sertions(+)
>
Acked-by: Rob Herring
changed, 7 insertions(+)
>
Acked-by: Rob Herring
On Sat, 17 Apr 2021 00:40:48 +0800, Hsin-Yi Wang wrote:
> Kappa is known as HP Chromebook 11a.
>
> Signed-off-by: Hsin-Yi Wang
> Reviewed-by: Enric Balletbo i Serra
> ---
> Documentation/devicetree/bindings/arm/mediatek.yaml | 4
> 1 file changed, 4 insertions(+)
>
Acked-by: Rob Herring
On Fri, Apr 16, 2021 at 05:32:16PM +0800, Po-Kai Chi wrote:
> MediaTek DRAM controller (DRAMC) driver provides cross-platform features
> as below:
>
> 1. provide APIs for low power feature queries
> 2. create sysfs to pass the DRAM information to user-space
I'm hesistant with having both DT and
Signed-off-by: Etienne Carriere
> Signed-off-by: Gabriel Fernandez
> ---
> .../devicetree/bindings/clock/st,stm32mp1-rcc.yaml | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
Acked-by: Rob Herring
s/display/mediatek/mediatek,hdmi-ddc.yaml | 1 +
> .../devicetree/bindings/display/mediatek/mediatek,hdmi.yaml | 1 +
> 3 files changed, 3 insertions(+)
>
Acked-by: Rob Herring
/mediatek,cec.yaml
> create mode 100644
> Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi-ddc.yaml
> delete mode 100644
> Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.txt
> create mode 100644
> Documentation/devicetree/bindings/displ
0644
> Documentation/devicetree/bindings/iio/accel/murata,sca3300.yaml
>
Reviewed-by: Rob Herring
On Tue, Apr 20, 2021 at 10:12 AM Alexandre TORGUE
wrote:
>
>
>
> On 4/20/21 4:45 PM, Rob Herring wrote:
> > On Tue, Apr 20, 2021 at 9:03 AM Alexandre TORGUE
> > wrote:
> >>
> >> Hi,
> >
> > Greg or Sasha won't know what to do with this. No
e Zhang
> Signed-off-by: Johan Jonker
> ---
> Note for rob+dt:
> A tag was not added on purpose, because:
> Add "rockchip," prefix to the qos compatible name
> in example.
> Changed maintainers.
> Size reg description is reduced.
> Little style ch
On Sun, 18 Apr 2021 14:29:08 +0200, Bartosz Dudziak wrote:
> Document the MSM8226 SoC device-tree binding.
>
> Signed-off-by: Bartosz Dudziak
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 6 ++
> 1 file changed, 6 insertions(+)
>
Acked-by: Rob Herring
ns(+), 2 deletions(-)
Acked-by: Rob Herring
On Tue, Apr 20, 2021 at 01:41:52PM +0530, Nava kishore Manne wrote:
> This patch adds the binding document for the zynqmp afi
> config driver.
Bindings are for h/w blocks, not drivers.
>
> Signed-off-by: Nava kishore Manne
> ---
> .../bindings/misc/xlnx,zynqmp-afi-fpga.yaml | 136
On Fri, Apr 16, 2021 at 09:26:03PM +0200, Michael Walle wrote:
> Hi Rob,
>
> Am 2021-04-16 20:44, schrieb Rob Herring:
> > On Fri, Apr 16, 2021 at 01:49:23PM +0200, Michael Walle wrote:
> > > The goal is to fetch a (base) MAC address from the OTP region of a
&
On Tue, 20 Apr 2021 13:41:52 +0530, Nava kishore Manne wrote:
> This patch adds the binding document for the zynqmp afi
> config driver.
>
> Signed-off-by: Nava kishore Manne
> ---
> .../bindings/misc/xlnx,zynqmp-afi-fpga.yaml | 136 ++
> 1 file changed, 136 insertions(+)
>
On Tue, Mar 30, 2021 at 4:29 AM Kishon Vijay Abraham I wrote:
>
> Hi Rob,
>
> On 26/03/21 5:08 am, Rob Herring wrote:
> > On Thu, Mar 25, 2021 at 02:30:21PM +0530, Kishon Vijay Abraham I wrote:
> >> Add PCIe host mode dt-bindings for TI's AM65 SoC.
> >>
> &
On Mon, Jan 25, 2021 at 7:18 PM Nicolas Boichat wrote:
>
> Define a compatible string for the Mali Bifrost GPU found in
> Mediatek's MT8183 SoCs.
>
> Signed-off-by: Nicolas Boichat
> ---
>
> Changes in v11:
> - binding: power-domain-names not power-domainS-names
>
> Changes in v10:
> - Fix the
On Fri, Feb 5, 2021 at 9:02 PM Nicolas Boichat wrote:
>
> On Sat, Feb 6, 2021 at 1:55 AM Rob Herring wrote:
> >
> > On Tue, 26 Jan 2021 09:17:56 +0800, Nicolas Boichat wrote:
> > > Define a compatible string for the Mali Bifrost GPU found in
> > > Mediatek's
From: Raphael Gault
Add documentation to describe the access to the pmu hardware counters from
userspace.
Signed-off-by: Raphael Gault
Signed-off-by: Rob Herring
---
v7:
- Merge into existing arm64 perf.rst
v6:
- Update the chained event section with attr.config1 details
v2:
- Update
Userspace counter access only works on heterogeneous systems with some
restrictions. The userspace process must be pinned to a homogeneous
subset of CPUs and must open the corresponding PMU for those CPUs. This
commit adds a test implementing these requirements.
Signed-off-by: Rob Herring
---
v6
Add arm64 specific tests for 32-bit and 64-bit counter user access. On
arm64, counters default to 32-bit unless attr.config1:0 is set to 1. In
order to enable user access for 64-bit counters, attr.config1 must be set
to 3.
Signed-off-by: Rob Herring
---
v6:
- New patch
---
tools/perf/arch
Add the arm64 variants for read_perf_counter() and read_timestamp().
Unfortunately the counter number is encoded into the instruction, so the
code is a bit verbose to enumerate all possible counters.
Signed-off-by: Rob Herring
---
v7:
- Move enabling of libperf user read test for arm64
disable access on each PMU.
Note that x86 also supports writing '2' to globally enable user access.
As there's not existing userspace support to worry about, this shouldn't
be necessary for Arm. It could be added later if the need arises.
Signed-off-by: Rob Herring
---
arch/arm64/kernel/perf_event.c
Gault
Signed-off-by: Rob Herring
---
Peter Z says (event->oncpu == smp_processor_id()) in the user page
update is always true, but my testing says otherwise[1].
v7:
- Clear disabled counters when user access is enabled for a task to
avoid leaking other tasks counter data.
- Rework context swi
The arm64 PMU driver needs to retrieve the struct arm_pmu pointer for
the current CPU. As the common code already maintains this with the
percpu cpu_armpmu, let's make it global.
Signed-off-by: Rob Herring
---
drivers/perf/arm_pmu.c | 2 +-
include/linux/perf/arm_pmu.h | 2 ++
2 files
is implemented and initialized by
the PMU implementation: if no callback is provided, the default
behaviour applies, returning 0 as index value.
Signed-off-by: Raphael Gault
Signed-off-by: Rob Herring
---
v7:
- Add define ARMV8_IDX_CYCLE_COUNTER_USER for userspace index
of cycle counter
---
arch/arm64
bug in that pmc_width was not set in the user page. The tests
now check for this.
The documentation has been converted to rST. I've added sections on
chained events and heterogeneous.
The tests have been expanded to test the cycle counter access.
Rob
[1] https://lore.kernel.org/r/20190822144220.2786
which made the pmu emulation inefficient.
Signed-off-by: Raphael Gault
Signed-off-by: Rob Herring
---
v7:
- Split off from Raphael's original undef hook patch as this change stands
on its own.
---
arch/arm64/kernel/cpufeature.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
On Mon, Apr 19, 2021 at 7:35 PM Leonardo Bras wrote:
>
> On Mon, 2021-04-19 at 10:44 -0500, Rob Herring wrote:
> > On Fri, Apr 16, 2021 at 3:58 PM Leonardo Bras wrote:
> > >
> > > Hello Rob, thanks for this feedback!
> > >
> > > On Thu, 2021-04-15
On Mon, Apr 19, 2021 at 11:14 AM Will Deacon wrote:
>
> On Thu, Apr 08, 2021 at 01:38:17PM -0500, Rob Herring wrote:
> > On Thu, Apr 8, 2021 at 6:08 AM Mark Rutland wrote:
> > > On Wed, Apr 07, 2021 at 01:44:37PM +0100, Will Deacon wrote:
> > > > On Thu, Apr
On Fri, Apr 16, 2021 at 3:58 PM Leonardo Bras wrote:
>
> Hello Rob, thanks for this feedback!
>
> On Thu, 2021-04-15 at 13:59 -0500, Rob Herring wrote:
> > +PPC and PCI lists
> >
> > On Thu, Apr 15, 2021 at 1:01 PM Leonardo Bras wrote:
> > >
> > &
1 - 100 of 29031 matches
Mail list logo