From: Vinod Koul <vkoul@kernel.org>
To: Alex Elder <elder@riscstar.com>
Cc: neil.armstrong@linaro.org, dlan@gentoo.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
guodong@riscstar.com, linux-phy@lists.infradead.org,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] phy: Kconfig: spacemit: add COMMON_CLK dependency
Date: Mon, 29 Dec 2025 22:27:23 +0530 [thread overview]
Message-ID: <aVKy87c7afpWIx33@vaman> (raw)
In-Reply-To: <20251226173228.2020411-1-elder@riscstar.com>
On 26-12-25, 11:32, Alex Elder wrote:
> The SpacemiT PCIe PHY driver depends on the common clock framework.
> Not specifying that led to a failure when doing a COMPILE_TEST build
> for the SPARC architecture.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202512251903.sTVZgg6c-lkp@intel.com/
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> Note: This is based on phy/next, which I find doesn't currently build
> cleanly using "arch/riscv/configs/defconfig".
I dont build rsicv, I should add that. What is the failure you see,
looking at changes I dont see anything that might break this
>
> drivers/phy/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
> index aa2d30e0e3261..3bc7378ea8658 100644
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -104,6 +104,7 @@ config PHY_NXP_PTN3222
> config PHY_SPACEMIT_K1_PCIE
> tristate "PCIe and combo PHY driver for the SpacemiT K1 SoC"
> depends on ARCH_SPACEMIT || COMPILE_TEST
> + depends on COMMON_CLK
> depends on HAS_IOMEM
> depends on OF
> select GENERIC_PHY
>
> base-commit: 27287e3b52b5954b73203d32ee76ffd5f53f5074
> --
> 2.48.1
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Alex Elder <elder@riscstar.com>
Cc: neil.armstrong@linaro.org, dlan@gentoo.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
guodong@riscstar.com, linux-phy@lists.infradead.org,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] phy: Kconfig: spacemit: add COMMON_CLK dependency
Date: Mon, 29 Dec 2025 22:27:23 +0530 [thread overview]
Message-ID: <aVKy87c7afpWIx33@vaman> (raw)
In-Reply-To: <20251226173228.2020411-1-elder@riscstar.com>
On 26-12-25, 11:32, Alex Elder wrote:
> The SpacemiT PCIe PHY driver depends on the common clock framework.
> Not specifying that led to a failure when doing a COMPILE_TEST build
> for the SPARC architecture.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202512251903.sTVZgg6c-lkp@intel.com/
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> Note: This is based on phy/next, which I find doesn't currently build
> cleanly using "arch/riscv/configs/defconfig".
I dont build rsicv, I should add that. What is the failure you see,
looking at changes I dont see anything that might break this
>
> drivers/phy/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
> index aa2d30e0e3261..3bc7378ea8658 100644
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -104,6 +104,7 @@ config PHY_NXP_PTN3222
> config PHY_SPACEMIT_K1_PCIE
> tristate "PCIe and combo PHY driver for the SpacemiT K1 SoC"
> depends on ARCH_SPACEMIT || COMPILE_TEST
> + depends on COMMON_CLK
> depends on HAS_IOMEM
> depends on OF
> select GENERIC_PHY
>
> base-commit: 27287e3b52b5954b73203d32ee76ffd5f53f5074
> --
> 2.48.1
--
~Vinod
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Alex Elder <elder@riscstar.com>
Cc: neil.armstrong@linaro.org, dlan@gentoo.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
guodong@riscstar.com, linux-phy@lists.infradead.org,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] phy: Kconfig: spacemit: add COMMON_CLK dependency
Date: Mon, 29 Dec 2025 22:27:23 +0530 [thread overview]
Message-ID: <aVKy87c7afpWIx33@vaman> (raw)
In-Reply-To: <20251226173228.2020411-1-elder@riscstar.com>
On 26-12-25, 11:32, Alex Elder wrote:
> The SpacemiT PCIe PHY driver depends on the common clock framework.
> Not specifying that led to a failure when doing a COMPILE_TEST build
> for the SPARC architecture.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202512251903.sTVZgg6c-lkp@intel.com/
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> Note: This is based on phy/next, which I find doesn't currently build
> cleanly using "arch/riscv/configs/defconfig".
I dont build rsicv, I should add that. What is the failure you see,
looking at changes I dont see anything that might break this
>
> drivers/phy/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
> index aa2d30e0e3261..3bc7378ea8658 100644
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -104,6 +104,7 @@ config PHY_NXP_PTN3222
> config PHY_SPACEMIT_K1_PCIE
> tristate "PCIe and combo PHY driver for the SpacemiT K1 SoC"
> depends on ARCH_SPACEMIT || COMPILE_TEST
> + depends on COMMON_CLK
> depends on HAS_IOMEM
> depends on OF
> select GENERIC_PHY
>
> base-commit: 27287e3b52b5954b73203d32ee76ffd5f53f5074
> --
> 2.48.1
--
~Vinod
next prev parent reply other threads:[~2025-12-29 16:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 17:32 [PATCH] phy: Kconfig: spacemit: add COMMON_CLK dependency Alex Elder
2025-12-26 17:32 ` Alex Elder
2025-12-26 17:32 ` Alex Elder
2025-12-29 10:26 ` Javier Martinez Canillas
2025-12-29 10:26 ` Javier Martinez Canillas
2025-12-29 10:26 ` Javier Martinez Canillas
2025-12-29 16:57 ` Vinod Koul [this message]
2025-12-29 16:57 ` Vinod Koul
2025-12-29 16:57 ` Vinod Koul
2025-12-29 17:51 ` Alex Elder
2025-12-29 17:51 ` Alex Elder
2025-12-29 17:51 ` Alex Elder
2026-01-01 11:07 ` Vinod Koul
2026-01-01 11:07 ` Vinod Koul
2026-01-01 11:07 ` Vinod Koul
2026-01-02 13:29 ` Alex Elder
2026-01-02 13:29 ` Alex Elder
2026-01-02 13:29 ` Alex Elder
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=aVKy87c7afpWIx33@vaman \
--to=vkoul@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=guodong@riscstar.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=spacemit@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.