From: Jerome Brunet <jbrunet@baylibre.com> To: Kevin Hilman <khilman@baylibre.com> Cc: Jerome Brunet <jbrunet@baylibre.com>, linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 2/4] arm64: defconfig: enable FUSB302 as module Date: Mon, 9 Dec 2019 15:38:34 +0100 [thread overview] Message-ID: <20191209143836.825990-3-jbrunet@baylibre.com> (raw) In-Reply-To: <20191209143836.825990-1-jbrunet@baylibre.com> Enable the type C fusb302 driver as module Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> --- arch/arm64/configs/defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 6a83ba2aea3e..33147f54efe6 100644 --- a/arch/arm64/configs/defconfig +++ b/arch/arm64/configs/defconfig @@ -603,6 +603,8 @@ CONFIG_USB_GADGET=y CONFIG_USB_RENESAS_USBHS_UDC=m CONFIG_USB_RENESAS_USB3=m CONFIG_TYPEC=m +CONFIG_TYPEC_TCPM=m +CONFIG_TYPEC_FUSB302=m CONFIG_TYPEC_HD3SS3220=m CONFIG_MMC=y CONFIG_MMC_BLOCK_MINORS=32 -- 2.23.0
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com> To: Kevin Hilman <khilman@baylibre.com> Cc: linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Jerome Brunet <jbrunet@baylibre.com> Subject: [PATCH v2 2/4] arm64: defconfig: enable FUSB302 as module Date: Mon, 9 Dec 2019 15:38:34 +0100 [thread overview] Message-ID: <20191209143836.825990-3-jbrunet@baylibre.com> (raw) In-Reply-To: <20191209143836.825990-1-jbrunet@baylibre.com> Enable the type C fusb302 driver as module Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> --- arch/arm64/configs/defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 6a83ba2aea3e..33147f54efe6 100644 --- a/arch/arm64/configs/defconfig +++ b/arch/arm64/configs/defconfig @@ -603,6 +603,8 @@ CONFIG_USB_GADGET=y CONFIG_USB_RENESAS_USBHS_UDC=m CONFIG_USB_RENESAS_USB3=m CONFIG_TYPEC=m +CONFIG_TYPEC_TCPM=m +CONFIG_TYPEC_FUSB302=m CONFIG_TYPEC_HD3SS3220=m CONFIG_MMC=y CONFIG_MMC_BLOCK_MINORS=32 -- 2.23.0 _______________________________________________ linux-amlogic mailing list linux-amlogic@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-12-09 14:38 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-09 14:38 [PATCH v2 0/4] arm64: dts: meson: add libretech-pc support Jerome Brunet 2019-12-09 14:38 ` Jerome Brunet 2019-12-09 14:38 ` [PATCH v2 1/4] arm64: dts: meson: gxl: add i2c C pins Jerome Brunet 2019-12-09 14:38 ` Jerome Brunet 2019-12-09 14:38 ` Jerome Brunet [this message] 2019-12-09 14:38 ` [PATCH v2 2/4] arm64: defconfig: enable FUSB302 as module Jerome Brunet 2019-12-09 14:38 ` [PATCH v2 3/4] dt-bindings: arm: amlogic: add libretech-pc bindings Jerome Brunet 2019-12-09 14:38 ` Jerome Brunet 2019-12-09 14:38 ` [PATCH v2 4/4] arm64: dts: meson: add libretech-pc boards support Jerome Brunet 2019-12-09 14:38 ` Jerome Brunet 2019-12-16 20:00 ` [PATCH v2 0/4] arm64: dts: meson: add libretech-pc support Kevin Hilman 2019-12-16 20:00 ` Kevin Hilman 2019-12-16 20:01 ` patchwork-bot+linux-amlogic
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=20191209143836.825990-3-jbrunet@baylibre.com \ --to=jbrunet@baylibre.com \ --cc=devicetree@vger.kernel.org \ --cc=khilman@baylibre.com \ --cc=linux-amlogic@lists.infradead.org \ --cc=linux-kernel@vger.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: linkBe 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.