lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a640435f-e840-48a8-9cf5-c796c7422070@ti.com>
Date: Mon, 29 Jul 2024 11:11:35 +0530
From: Siddharth Vadapalli <s-vadapalli@...com>
To: Lee Jones <lee@...nel.org>
CC: <robh@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        <lpieralisi@...nel.org>, <kw@...ux.com>, <bhelgaas@...gle.com>,
        <vigneshr@...com>, <kishon@...nel.org>,
        Siddharth Vadapalli
	<s-vadapalli@...com>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-pci@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <srk@...com>
Subject: Re: (subset) [PATCH 1/3] dt-bindings: mfd: syscon: Add
 ti,j784s4-acspcie-proxy-ctrl compatible

On Thu, Jul 25, 2024 at 11:23:34AM +0100, Lee Jones wrote:

Hello Lee,

> On Mon, 15 Jul 2024 17:39:34 +0530, Siddharth Vadapalli wrote:
> > The ACSPCIE_PROXY_CTRL registers within the CTRL_MMR space of TI's J784S4
> > SoC are used to drive the reference clock to the PCIe Endpoint device via
> > the PAD IO Buffers. Add the compatible for allowing the PCIe driver to
> > obtain the regmap for the ACSPCIE_CTRL register within the System
> > Controller device-tree node in order to enable the PAD IO Buffers.
> > 
> > The Technical Reference Manual for J784S4 SoC with details of the
> > ASCPCIE_CTRL registers is available at:
> > https://www.ti.com/lit/zip/spruj52
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/3] dt-bindings: mfd: syscon: Add ti,j784s4-acspcie-proxy-ctrl compatible
>       commit: d86ce301dcf715ea2d5147bb013a29f722bf5d0b

I don't see the commit in the MFD tree [1] and Linux-Next. Therefore I
am assuming that this patch was not committed and will be posting the v2
series with this patch included.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/log/?h=for-mfd-next

Regards,
Siddharth.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ