From: Abel Vesa <abel.vesa@nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 3/7] arm64: defconfig: enable drivers for TQ TQMa8MxML-MBa8Mx
Date: Thu, 16 Dec 2021 22:26:09 +0200 [thread overview]
Message-ID: <Ybug4acjSvCG+XxA@ryzen> (raw)
In-Reply-To: <20211201072949.53947-4-alexander.stein@ew.tq-group.com>
On 21-12-01 08:29:44, Alexander Stein wrote:
> With the device tree in place, enable missing drivers as modules, if
> possible. PHY driver needs built-in for interrupt support.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> Changes in v3:
> * None
>
> Changes in v2:
> * Add interconnect driver for imx8mm and imx8mn
>
> arch/arm64/configs/defconfig | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 0da6a944d5cd..44ce56dd2638 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -363,6 +363,7 @@ CONFIG_MICROSEMI_PHY=y
> CONFIG_AT803X_PHY=y
> CONFIG_REALTEK_PHY=y
> CONFIG_ROCKCHIP_PHY=y
> +CONFIG_DP83867_PHY=y
> CONFIG_VITESSE_PHY=y
> CONFIG_USB_PEGASUS=m
> CONFIG_USB_RTL8150=m
> @@ -397,6 +398,7 @@ CONFIG_TOUCHSCREEN_EDT_FT5X06=m
> CONFIG_INPUT_MISC=y
> CONFIG_INPUT_PM8941_PWRKEY=y
> CONFIG_INPUT_PM8XXX_VIBRATOR=m
> +CONFIG_INPUT_PWM_BEEPER=m
> CONFIG_INPUT_PWM_VIBRA=m
> CONFIG_INPUT_HISI_POWERKEY=y
> # CONFIG_SERIO_SERPORT is not set
> @@ -556,6 +558,7 @@ CONFIG_BATTERY_MAX17042=m
> CONFIG_CHARGER_BQ25890=m
> CONFIG_CHARGER_BQ25980=m
> CONFIG_SENSORS_ARM_SCPI=y
> +CONFIG_SENSORS_JC42=m
> CONFIG_SENSORS_LM90=m
> CONFIG_SENSORS_PWM_FAN=m
> CONFIG_SENSORS_RASPBERRYPI_HWMON=m
> @@ -793,6 +796,7 @@ CONFIG_SND_SOC_RT5659=m
> CONFIG_SND_SOC_SIMPLE_AMPLIFIER=m
> CONFIG_SND_SOC_SIMPLE_MUX=m
> CONFIG_SND_SOC_TAS571X=m
> +CONFIG_SND_SOC_TLV320AIC32X4_I2C=m
> CONFIG_SND_SOC_WCD934X=m
> CONFIG_SND_SOC_WM8904=m
> CONFIG_SND_SOC_WM8960=m
> @@ -908,6 +912,7 @@ CONFIG_RTC_DRV_DS1307=m
> CONFIG_RTC_DRV_HYM8563=m
> CONFIG_RTC_DRV_MAX77686=y
> CONFIG_RTC_DRV_RK808=m
> +CONFIG_RTC_DRV_PCF85063=m
> CONFIG_RTC_DRV_PCF85363=m
> CONFIG_RTC_DRV_M41T80=m
> CONFIG_RTC_DRV_RX8581=m
> @@ -1175,6 +1180,8 @@ CONFIG_SLIM_QCOM_NGD_CTRL=m
> CONFIG_MUX_MMIO=y
> CONFIG_INTERCONNECT=y
> CONFIG_INTERCONNECT_IMX=m
> +CONFIG_INTERCONNECT_IMX8MM=m
> +CONFIG_INTERCONNECT_IMX8MN=m
Nope. The interconnect doesn't work without imx8m-ddrc
and imx-bus devfreq drivers. Those drivers do not work
yet.
So please drop the interconnect configs for now.
> CONFIG_INTERCONNECT_IMX8MQ=m
> CONFIG_INTERCONNECT_QCOM=y
> CONFIG_INTERCONNECT_QCOM_MSM8916=m
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-12-16 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 7:29 [PATCH v3 0/7] Support for some TQMa8M* boards Alexander Stein
2021-12-01 7:29 ` [PATCH v3 1/7] dt-bindings: arm: fsl: add TQMa8MxML boards Alexander Stein
2021-12-01 7:29 ` [PATCH v3 2/7] arm64: dts: freescale: add initial device tree for TQMa8MQML with i.MX8MM Alexander Stein
2021-12-01 7:29 ` [PATCH v3 3/7] arm64: defconfig: enable drivers for TQ TQMa8MxML-MBa8Mx Alexander Stein
2021-12-16 20:26 ` Abel Vesa [this message]
2021-12-17 8:32 ` (EXT) " Alexander Stein
2021-12-01 7:29 ` [PATCH v3 4/7] dt-bindings: arm: fsl: add TQMa8MxNL boards Alexander Stein
2021-12-01 7:29 ` [PATCH v3 5/7] arm64: dts: freescale: add initial device tree for TQMa8MQNL with i.MX8MN Alexander Stein
2021-12-01 7:29 ` [PATCH v3 6/7] dt-bindings: arm: fsl: add TQMa8Mx boards Alexander Stein
2021-12-01 7:29 ` [PATCH v3 7/7] arm64: dts: freescale: add initial device tree for TQMa8Mx with i.MX8M Alexander Stein
2021-12-06 3:39 ` [PATCH v3 0/7] Support for some TQMa8M* boards Shawn Guo
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=Ybug4acjSvCG+XxA@ryzen \
--to=abel.vesa@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@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).