From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>
Cc: <linux-phy@lists.infradead.org>,
Minda Chen <minda.chen@starfivetech.com>,
Roger Quadros <rogerq@kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] phy: starfive: make phys depend on HAS_IOMEM
Date: Tue, 25 Jul 2023 14:44:50 +0800 [thread overview]
Message-ID: <b466b004-e5f2-7494-2fa5-3d27e9339118@starfivetech.com> (raw)
In-Reply-To: <20230725063856.482696-1-vkoul@kernel.org>
On 2023/7/25 14:38, Vinod Koul wrote:
> the startfive phy drivers use devm_platform_ioremap_resource() which on
> some archs (s390) is not present. So make the drivers depend on HAS_IOMEM
>
> Fixes: f8aa660841bc ("phy: starfive: Add mipi dphy rx support")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202307250509.oeudxG28-lkp@intel.com/
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
Reviewed-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> ---
> drivers/phy/starfive/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/phy/starfive/Kconfig b/drivers/phy/starfive/Kconfig
> index a560533a674e..0508f9b123e0 100644
> --- a/drivers/phy/starfive/Kconfig
> +++ b/drivers/phy/starfive/Kconfig
> @@ -5,6 +5,7 @@
>
> config PHY_STARFIVE_JH7110_DPHY_RX
> tristate "StarFive JH7110 D-PHY RX support"
> + depends on HAS_IOMEM
> select GENERIC_PHY
> select GENERIC_PHY_MIPI_DPHY
> help
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2023-07-25 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:38 [PATCH v2] phy: starfive: make phys depend on HAS_IOMEM Vinod Koul
2023-07-25 6:44 ` Changhuang Liang [this message]
2023-07-25 13:52 ` Vinod Koul
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=b466b004-e5f2-7494-2fa5-3d27e9339118@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=kishon@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lkp@intel.com \
--cc=minda.chen@starfivetech.com \
--cc=rogerq@kernel.org \
--cc=vkoul@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