From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] Make HWSPINLOCK a menuconfig to ease disabling
Date: Sun, 7 May 2017 22:07:49 -0700 [thread overview]
Message-ID: <20170508050749.GI15143@minitux> (raw)
In-Reply-To: <20170411142102.25838-2-vincent.legoll@gmail.com>
On Tue 11 Apr 07:21 PDT 2017, Vincent Legoll wrote:
> So that there's no need to get into the submenu to disable all related config
> entries.
>
> Signed-off-by: Vincent Legoll <vincent.legoll@gmail.com>
Looks reasonable, I'll pick this up after the merge window.
Regards,
Bjorn
> ---
> drivers/hwspinlock/Kconfig | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock/Kconfig
> index 73a4016..cc26b04 100644
> --- a/drivers/hwspinlock/Kconfig
> +++ b/drivers/hwspinlock/Kconfig
> @@ -2,16 +2,13 @@
> # Generic HWSPINLOCK framework
> #
>
> -# HWSPINLOCK always gets selected by whoever wants it.
> -config HWSPINLOCK
> - tristate
> -
> -menu "Hardware Spinlock drivers"
> +menuconfig HWSPINLOCK
> + tristate "Hardware Spinlock drivers"
>
> config HWSPINLOCK_OMAP
> tristate "OMAP Hardware Spinlock device"
> + depends on HWSPINLOCK
> depends on ARCH_OMAP4 || SOC_OMAP5 || SOC_DRA7XX || SOC_AM33XX || SOC_AM43XX
> - select HWSPINLOCK
> help
> Say y here to support the OMAP Hardware Spinlock device (firstly
> introduced in OMAP4).
> @@ -20,8 +17,8 @@ config HWSPINLOCK_OMAP
>
> config HWSPINLOCK_QCOM
> tristate "Qualcomm Hardware Spinlock device"
> + depends on HWSPINLOCK
> depends on ARCH_QCOM
> - select HWSPINLOCK
> select MFD_SYSCON
> help
> Say y here to support the Qualcomm Hardware Mutex functionality, which
> @@ -32,8 +29,8 @@ config HWSPINLOCK_QCOM
>
> config HWSPINLOCK_SIRF
> tristate "SIRF Hardware Spinlock device"
> + depends on HWSPINLOCK
> depends on ARCH_SIRF
> - select HWSPINLOCK
> help
> Say y here to support the SIRF Hardware Spinlock device, which
> provides a synchronisation mechanism for the various processors
> @@ -44,13 +41,11 @@ config HWSPINLOCK_SIRF
>
> config HSEM_U8500
> tristate "STE Hardware Semaphore functionality"
> + depends on HWSPINLOCK
> depends on ARCH_U8500
> - select HWSPINLOCK
> help
> Say y here to support the STE Hardware Semaphore functionality, which
> provides a synchronisation mechanism for the various processor on the
> SoC.
>
> If unsure, say N.
> -
> -endmenu
> --
> 2.9.3
>
prev parent reply other threads:[~2017-05-08 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 14:21 [RFC PATCH v1] Make HWSPINLOCK a menuconfig to ease disabling Vincent Legoll
2017-04-11 14:21 ` [PATCH] " Vincent Legoll
2017-05-06 10:32 ` Vincent Legoll
2017-05-08 5:07 ` Bjorn Andersson [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=20170508050749.GI15143@minitux \
--to=bjorn.andersson@linaro.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=vincent.legoll@gmail.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