From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manikandan Muralidharan <manikandan.m@microchip.com>,
broonie@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
ryan.wanner@microchip.com, tudor.ambarus@linaro.org,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] spi: dt-bindings: atmel,at91rm9200-spi: Add support for optional 'spi_gclk' clock
Date: Wed, 30 Jul 2025 13:21:17 +0200 [thread overview]
Message-ID: <c1230d31-cb7e-4a21-b7d0-ea32d862823f@kernel.org> (raw)
In-Reply-To: <20250730101015.323964-2-manikandan.m@microchip.com>
On 30/07/2025 12:10, Manikandan Muralidharan wrote:
> Update the Atmel SPI DT binding to support an optional programmable
> SPI generic clock 'spi_gclk', in addition to the required 'spi_clk'.
>
> Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
> ---
> changes in v2:
> - Fixed mail threading
You already received comments. Respond to them instead of sending again
the same.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-30 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 10:10 [PATCH v2 1/3] spi: atmel: simplify MR register update in cs_activate() Manikandan Muralidharan
2025-07-30 10:10 ` [PATCH v2 2/3] spi: dt-bindings: atmel,at91rm9200-spi: Add support for optional 'spi_gclk' clock Manikandan Muralidharan
2025-07-30 11:21 ` Krzysztof Kozlowski [this message]
2025-08-01 3:36 ` Manikandan.M
2025-08-01 9:15 ` Krzysztof Kozlowski
2025-08-05 3:48 ` Manikandan.M
2025-07-30 10:10 ` [PATCH v2 3/3] spi: atmel: Add support for handling GCLK as a clock source Manikandan Muralidharan
2025-08-12 11:05 ` [PATCH v2 1/3] spi: atmel: simplify MR register update in cs_activate() Mark Brown
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=c1230d31-cb7e-4a21-b7d0-ea32d862823f@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=manikandan.m@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=ryan.wanner@microchip.com \
--cc=tudor.ambarus@linaro.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
all inboxes | Powered by JetHome®