From: "Rob Herring (Arm)" <robh@kernel.org>
To: Alex Elder <elder@riscstar.com>
Cc: dlan@gentoo.org, bastien.curutchet@bootlin.com,
krzk+dt@kernel.org, devicetree@vger.kernel.org,
andriy.shevchenko@linux.intel.com, linux-serial@vger.kernel.org,
benjamin.larsson@genexis.eu, spacemit@lists.linux.dev,
conor+dt@kernel.org, jirislaby@kernel.org,
u.kleine-koenig@baylibre.com, lkundrak@v3.sk,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 1/2] dt-bindings: serial: 8250: support an optional second clock
Date: Thu, 10 Apr 2025 08:01:45 -0500 [thread overview]
Message-ID: <174429010339.3601181.9300442715706668225.robh@kernel.org> (raw)
In-Reply-To: <20250409192213.1130181-2-elder@riscstar.com>
On Wed, 09 Apr 2025 14:22:11 -0500, Alex Elder wrote:
> The SpacemiT UART driver requires a bus clock to be enabled in addition
> to the primary function clock. Add the option to specify two clocks
> for an 8250-compatible UART, named "core" and "bus". If both are needed,
> require them to be named.
>
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> v2: Require both clocks to be specified with names for SpacemiT
>
> .../devicetree/bindings/serial/8250.yaml | 30 ++++++++++++++++++-
> 1 file changed, 29 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-04-10 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 19:22 [PATCH v2 0/2] serial: 8250_of: support an optional bus clock Alex Elder
2025-04-09 19:22 ` [PATCH v2 1/2] dt-bindings: serial: 8250: support an optional second clock Alex Elder
2025-04-10 13:01 ` Rob Herring (Arm) [this message]
2025-04-09 19:22 ` [PATCH v2 2/2] serial: 8250_of: add support for an optional bus clock Alex Elder
2025-04-09 21:43 ` Yixun Lan
2025-04-09 22:47 ` Alex Elder
2025-04-09 23:59 ` Yixun Lan
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=174429010339.3601181.9300442715706668225.robh@kernel.org \
--to=robh@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bastien.curutchet@bootlin.com \
--cc=benjamin.larsson@genexis.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=spacemit@lists.linux.dev \
--cc=u.kleine-koenig@baylibre.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®