mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuai Liu <847807867@qq.com>
To: Kwanghoon Son <asdfkwang@gmail.com>
Cc: Shuai Liu <847807867@qq.com>, Miguel Ojeda <ojeda@kernel.org>,
	rust-for-linux@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 06/12] rust: serial: Add minimal serial-core polling console support
Date: Mon,  2 Nov 2026 14:02:20 +0800	[thread overview]
Message-ID: <tencent_2A5F482BB0F8C8773425E14A8B3D4C70BA0A@qq.com> (raw)
In-Reply-To: <auSGbrP19XfI3S5N@debian>

Hi Kwanghoon,

On Fri, Oct 30, 2026 at 07:58:38AM -0400, Kwanghoon Son <asdfkwang@gmail.com> wrote:
> I don't understand for now, COMMON_CLK not possible on x86?
> or you mean CI not supported?

You are right to question this -- my comment was incorrect, sorry for
the confusion.

COMMON_CLK is not restricted away on x86. It only depends on
!HAVE_LEGACY_CLK, which x86 does not select, and several x86 platform
options (e.g. X86_INTEL_LPSS, X86_AMD_PLATFORM_DEVICE) select it
themselves. I verified that "make ARCH=x86 allmodconfig" results in
CONFIG_OF=y and CONFIG_COMMON_CLK=y, so with Rust enabled, as in the
Rust CI, all of the dependencies of SERIAL_BFLB_RUST (RUST, OF,
COMMON_CLK, HAS_IOMEM) are satisfiable on x86 and the driver is
eligible for build coverage from allmodconfig there.

To back this up, I also build-tested the series on x86 (LLVM=1,
allmodconfig-based configuration with Rust enabled): the serial-core
abstractions, the C helper glue and SERIAL_BFLB_RUST all compile
cleanly, and a full x86-64 vmlinux links with the driver built in.

What happened is that I conflated COMMON_CLK with arch-scoped
dependencies I had been looking at in other drivers (e.g. RISCV- or
OF-scoped Kconfig entries) and stated it without verifying it first.
It also means my suggestion of "depends on RISCV || COMPILE_TEST" in
that mail was unnecessary; the Kconfig as it stands is fine.

Thanks for catching this and for the question.

Best regards,
Shuai Liu


  reply	other threads:[~2026-11-02  6:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  5:05 [PATCH RFC 00/12] Add BL808 UART3 support with a Rust serial-core polling console Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 01/12] dt-bindings: vendor-prefixes: Add Bouffalo Lab Kwanghoon Son
2026-10-29 18:52   ` Conor Dooley
2026-10-30  5:42     ` Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 02/12] dt-bindings: interrupt-controller: Add BL808 PLIC Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 03/12] dt-bindings: timer: Add BL808 CLINT Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 04/12] dt-bindings: riscv: Add Bouffalo Lab BL808 Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 05/12] dt-bindings: serial: Add BL808 UART Kwanghoon Son
2026-10-29 18:54   ` Conor Dooley
2026-10-29 19:18     ` Conor Dooley
2026-10-30  5:56       ` Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 06/12] rust: serial: Add minimal serial-core polling console support Kwanghoon Son
2026-10-30  2:16   ` Shuai Liu
2026-10-30 11:58     ` Kwanghoon Son
2026-11-02  6:02       ` Shuai Liu [this message]
2026-10-29  5:05 ` [PATCH RFC 07/12] serial: bflb: Add Rust BL808 polling console Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 08/12] riscv: Add Bouffalo Lab SoC selection Kwanghoon Son
2026-10-29 18:58   ` Conor Dooley
2026-10-30  5:58     ` Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 09/12] riscv: dts: bouffalolab: Add BL808 SoC Kwanghoon Son
2026-10-29 19:05   ` Conor Dooley
2026-10-29  5:05 ` [PATCH RFC 10/12] riscv: dts: bouffalolab: Add Sipeed M1s Dock Kwanghoon Son
2026-10-29 19:07   ` Conor Dooley
2026-10-30 11:37     ` Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 11/12] riscv: defconfig: Enable Bouffalo Lab SoCs Kwanghoon Son
2026-10-29  5:05 ` [PATCH RFC 12/12] MAINTAINERS: Add Bouffalo Lab BL808 support Kwanghoon Son
2026-10-29 19:08   ` Conor Dooley
2026-10-29 19:20     ` Conor Dooley
2026-10-30 11:44       ` Kwanghoon Son
2026-10-30 18:48         ` Conor Dooley
2026-10-31 11:26           ` Kwanghoon Son

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=tencent_2A5F482BB0F8C8773425E14A8B3D4C70BA0A@qq.com \
    --to=847807867@qq.com \
    --cc=asdfkwang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.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

all inboxes | Powered by JetHome®