From: Rob Herring <robh@kernel.org>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: lee@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, srk@ti.com
Subject: Re: [PATCH v2] dt-bindings: mfd: syscon: Add ti,j784s4-acspcie-proxy-ctrl compatible
Date: Mon, 29 Jul 2024 10:04:53 -0600 [thread overview]
Message-ID: <20240729160453.GA805559-robh@kernel.org> (raw)
In-Reply-To: <20240729064012.1915674-1-s-vadapalli@ti.com>
On Mon, Jul 29, 2024 at 12:10:12PM +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
>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>
> Hello,
>
> This patch is based on linux-next tagged next-20240729.
> v1: https://lore.kernel.org/r/20240715120936.1150314-2-s-vadapalli@ti.com/
> Changes since v1:
> - Rebased patch on next-20240729.
> - Separated this patch from the series.
> - Collected Acked-by tag from:
> Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> https://lore.kernel.org/r/04d94188-5e30-4cab-b534-e97c0b2a61f3@kernel.org/
>
> NOTE: Though it was mentioned on 25th July 2024 that this patch was applied:
> https://lore.kernel.org/r/172190301400.925833.12525656543896105526.b4-ty@kernel.org/
> since I did not find the commit in the MFD tree and the Linux-Next tree,
> I am reposting this patch.
That's because it was in the middle of the merge window and only fixes
get published during that time. That's now over, so it should get
published soon. However, maintainers get busy on other work or take
vacation, so it could be delayed.
Unless a maintainer updates their tree with other later patches and your
patch is not there, no reason to worry and resend.
Rob
next prev parent reply other threads:[~2024-07-29 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 6:40 [PATCH v2] dt-bindings: mfd: syscon: Add ti,j784s4-acspcie-proxy-ctrl compatible Siddharth Vadapalli
2024-07-29 16:04 ` Rob Herring [this message]
2024-07-29 16:13 ` Siddharth Vadapalli
2024-08-01 12:43 ` Lee Jones
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=20240729160453.GA805559-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).