From: Conor Dooley <conor@kernel.org>
To: Jan Dakinevich <jan.dakinevich@salutedevices.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: reset: add bindings for A1 SoC audio reset controller
Date: Thu, 14 Nov 2024 20:14:40 +0000 [thread overview]
Message-ID: <20241114-latticed-freight-859a3d78d413@spud> (raw)
In-Reply-To: <20241112230056.1406222-2-jan.dakinevich@salutedevices.com>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Wed, Nov 13, 2024 at 02:00:55AM +0300, Jan Dakinevich wrote:
> This reset controller is part of audio clock controller and handled by
> auxiliary reset driver.
I appreciate this, saved me looking up why there was no compatible
added.
> Introduced defines supposed to be used together
> with upcoming device tree nodes for audio clock controller fo A1 SoC.
>
> Signed-off-by: Jan Dakinevich <jan.dakinevich@salutedevices.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-14 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 23:00 [PATCH 0/2] Add support for A1 SoC in auxiliary reset driver Jan Dakinevich
2024-11-12 23:00 ` [PATCH 1/2] dt-bindings: reset: add bindings for A1 SoC audio reset controller Jan Dakinevich
2024-11-14 20:14 ` Conor Dooley [this message]
2024-11-12 23:00 ` [PATCH 2/2] reset: amlogic: add support for A1 SoC in auxiliary reset driver Jan Dakinevich
2024-12-06 16:03 ` [PATCH 0/2] Add " Philipp Zabel
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=20241114-latticed-freight-859a3d78d413@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jan.dakinevich@salutedevices.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
/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