From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] usb: typec: mux: select not-visible INTEL_SCU_IPC
Date: Mon, 31 Jan 2022 10:42:31 +0200 [thread overview]
Message-ID: <Yfeg96P3no1FhWE5@kuha.fi.intel.com> (raw)
In-Reply-To: <20220130185032.29298-1-rdunlap@infradead.org>
On Sun, Jan 30, 2022 at 10:50:32AM -0800, Randy Dunlap wrote:
> Use "select INTEL_SCU_IPC" instead of depending on it since it is
> not a visible Kconfig symbol and it may not otherwise be set/enabled.
>
> Fixes: b62851491a55 ("usb: typec: mux: Convert the Intel PMC Mux driver to use new SCU IPC API")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> Cc: Lee Jones <lee.jones@linaro.org>
> Cc: linux-usb@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: kernel test robot <lkp@intel.com>
> ---
> v2: add dependency on X86_PLATFORM_DEVICES to fix build error that was
> Reported_by: kernel test robot <lkp@intel.com>
>
> drivers/usb/typec/mux/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next-20220128.orig/drivers/usb/typec/mux/Kconfig
> +++ linux-next-20220128/drivers/usb/typec/mux/Kconfig
> @@ -11,8 +11,8 @@ config TYPEC_MUX_PI3USB30532
>
> config TYPEC_MUX_INTEL_PMC
> tristate "Intel PMC mux control"
> - depends on ACPI
> - depends on INTEL_SCU_IPC
> + depends on ACPI && X86_PLATFORM_DEVICES
> + select INTEL_SCU_IPC
> select USB_ROLE_SWITCH
> help
> Driver for USB muxes controlled by Intel PMC FW. Intel PMC FW can
This will cause the driver to fail at probe time if there are no SCU
device drivers enabled.
The idea is that the SCU device drivers select the SCU IPC library,
not the users of the library like this mux driver.
thanks,
--
heikki
next prev parent reply other threads:[~2022-01-31 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 18:50 Randy Dunlap
2022-01-31 8:42 ` Heikki Krogerus [this message]
2022-01-31 16:26 ` Randy Dunlap
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=Yfeg96P3no1FhWE5@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rdunlap@infradead.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®