linux-phy.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	Vinod Koul <vkoul@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	 <linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: mediatek: Kconfig: Add configuration menu for Mediatek phy drivers
Date: Thu, 23 Sep 2021 17:02:34 +0800	[thread overview]
Message-ID: <cf5a0b929b9600ec3314f1370939a94ee43a5519.camel@mediatek.com> (raw)
In-Reply-To: <20210923025036.348-1-caihuoqing@baidu.com>

On Thu, 2021-09-23 at 10:50 +0800, Cai Huoqing wrote:
> Adding a configuration menu to hold many Mediatek phy drivers
> helps to make the menu display more concise.
> 
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
> ---
>  drivers/phy/mediatek/Kconfig | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/phy/mediatek/Kconfig
> b/drivers/phy/mediatek/Kconfig
> index 55f8e6c048ab..5da045813b5a 100644
> --- a/drivers/phy/mediatek/Kconfig
> +++ b/drivers/phy/mediatek/Kconfig
> @@ -2,9 +2,11 @@
>  #
>  # Phy drivers for Mediatek devices
>  #
> +menu "PHY drivers for Mediatek platforms"
> +	depends on ARCH_MEDIATEK || COMPILE_TEST
> +
>  config PHY_MTK_TPHY
>  	tristate "MediaTek T-PHY Driver"
> -	depends on ARCH_MEDIATEK || COMPILE_TEST
>  	depends on OF && OF_ADDRESS
>  	depends on HAS_IOMEM
>  	select GENERIC_PHY
> @@ -18,7 +20,6 @@ config PHY_MTK_TPHY
>  
>  config PHY_MTK_UFS
>  	tristate "MediaTek UFS M-PHY driver"
> -	depends on ARCH_MEDIATEK || COMPILE_TEST
>  	depends on OF
>  	select GENERIC_PHY
>  	help
> @@ -29,7 +30,6 @@ config PHY_MTK_UFS
>  
>  config PHY_MTK_XSPHY
>  	tristate "MediaTek XS-PHY Driver"
> -	depends on ARCH_MEDIATEK || COMPILE_TEST
>  	depends on OF && OF_ADDRESS
>  	depends on HAS_IOMEM
>  	select GENERIC_PHY
> @@ -40,7 +40,6 @@ config PHY_MTK_XSPHY
>  
>  config PHY_MTK_HDMI
>  	tristate "MediaTek HDMI-PHY Driver"
> -	depends on ARCH_MEDIATEK || COMPILE_TEST
>  	depends on COMMON_CLK
>  	depends on OF
>  	select GENERIC_PHY
> @@ -49,9 +48,10 @@ config PHY_MTK_HDMI
>  
>  config PHY_MTK_MIPI_DSI
>  	tristate "MediaTek MIPI-DSI Driver"
> -	depends on ARCH_MEDIATEK || COMPILE_TEST
>  	depends on COMMON_CLK
>  	depends on OF
>  	select GENERIC_PHY
>  	help
>  	  Support MIPI DSI for Mediatek SoCs.
> +
> +endmenu

Reviewed-by: Chunfeng Yun <chunfeng.yun@mediatek.com>

Thanks a lot

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

      reply	other threads:[~2021-09-23  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  2:50 [PATCH] phy: mediatek: Kconfig: Add configuration menu for Mediatek phy drivers Cai Huoqing
2021-09-23  9:02 ` Chunfeng Yun [this message]

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=cf5a0b929b9600ec3314f1370939a94ee43a5519.camel@mediatek.com \
    --to=chunfeng.yun@mediatek.com \
    --cc=caihuoqing@baidu.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).