From: "Rob Herring (Arm)" <robh@kernel.org>
To: Denzeel Oliva <wachiturroxd150@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: clock: exynos990: Add LHS_ACEL clock ID for HSI0 block
Date: Mon, 1 Sep 2025 16:33:00 -0500 [thread overview]
Message-ID: <175676238020.380265.9436129584616218710.robh@kernel.org> (raw)
In-Reply-To: <20250831-usb-v2-1-00b9c0559733@gmail.com>
On Sun, 31 Aug 2025 12:13:14 +0000, Denzeel Oliva wrote:
> Add the missing LHS_ACEL clock ID for the HSI0 block. This clock is
> required for proper USB operation, as without it, USB connections fail
> with errors like device descriptor read timeouts and address response
> issues.
>
> Signed-off-by: Denzeel Oliva <wachiturroxd150@gmail.com>
> ---
> include/dt-bindings/clock/samsung,exynos990.h | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-09-01 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 12:13 [PATCH v2 0/3] clk: samsung: exynos990: Fix USB clock support Denzeel Oliva
2025-08-31 12:13 ` [PATCH v2 1/3] dt-bindings: clock: exynos990: Add LHS_ACEL clock ID for HSI0 block Denzeel Oliva
2025-09-01 21:33 ` Rob Herring (Arm) [this message]
2025-08-31 12:13 ` [PATCH v2 2/3] clk: samsung: exynos990: Add LHS_ACEL gate clock for HSI0 and update CLK_NR_TOP Denzeel Oliva
2025-08-31 12:13 ` [PATCH v2 3/3] clk: samsung: exynos990: Add missing USB clock registers to HSI0 Denzeel Oliva
2025-09-04 13:48 ` [PATCH v2 0/3] clk: samsung: exynos990: Fix USB clock support Krzysztof Kozlowski
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=175676238020.380265.9436129584616218710.robh@kernel.org \
--to=robh@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=wachiturroxd150@gmail.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®