mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: Hrushikesh Salunke <h-salunke@ti.com>, <nm@ti.com>,
	<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <s-vadapalli@ti.com>, <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<danishanwar@ti.com>
Subject: Re: [PATCH v2 0/4] arm64: dts: ti: Add bootph-all tag to USB PHY controller
Date: Thu, 4 Sep 2025 16:17:40 -0500	[thread overview]
Message-ID: <83bdbff9-57d5-4391-8ec7-661b1ba012cd@ti.com> (raw)
In-Reply-To: <20250902053009.1732607-1-h-salunke@ti.com>

Hi Hrushikesh,

On 9/2/25 12:30 AM, Hrushikesh Salunke wrote:
> This patch series adds the bootph-all property to USB0 PHY controller
> nodes across multiple TI SoCs (AM62, AM62A, AM62P, J722S).
> 
> The bootph-all tag ensures that these USB PHY controller nodes are
> available during all boot phases, which is required for USB DFU
> (Device Firmware Upgrade) boot functionality.
> 
> Changes sice v1:
> Updated patch series to add "bootph-all" tag to board specific file
> instead of SoC file.
> Rebased on current next.
> 
> This series is based on commit:
> 33bcf93b9a6b Add linux-next specific files for 20250901
> 

Thanks for the patches.

Reviewed-by: Judith Mendez <jm@ti.com>

  parent reply	other threads:[~2025-09-04 21:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  5:30 Hrushikesh Salunke
2025-09-02  5:30 ` [PATCH v2 1/4] arm64: dts: ti: k3-am62a7-sk: Add bootph-all tag to usb0_phy_ctrl node Hrushikesh Salunke
2025-09-02  5:30 ` [PATCH v2 2/4] arm64: dts: ti: k3-am62p5-sk: " Hrushikesh Salunke
2025-09-02  5:30 ` [PATCH v2 3/4] arm64: dts: ti: k3-am62x-sk-common: " Hrushikesh Salunke
2025-09-02  5:30 ` [PATCH v2 4/4] arm64: dts: ti: k3-j722s-evm: " Hrushikesh Salunke
2025-09-03  9:52 ` [PATCH v2 0/4] arm64: dts: ti: Add bootph-all tag to USB PHY controller s-vadapalli
2025-09-04 21:17 ` Judith Mendez [this message]
2025-09-12  9:50 ` Nishanth Menon

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=83bdbff9-57d5-4391-8ec7-661b1ba012cd@ti.com \
    --to=jm@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=danishanwar@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=h-salunke@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=vigneshr@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
all inboxes | Powered by JetHome®