From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH v2] board/stmicroelectronics/stm32mp157*-dk*: cleanup linux.config
Date: Sun, 14 Nov 2021 16:26:58 +0100 [thread overview]
Message-ID: <20211114162658.7ac403eb@windsurf> (raw)
In-Reply-To: <20211025170520.1086081-1-francois.perrad@gadz.org>
Hello,
It is not clear what you are "cleaning up" here. Could you clarify? Is
about removing options that are useless?
On Mon, 25 Oct 2021 19:05:20 +0200
Francois Perrad <fperrad@gmail.com> wrote:
> note:
> - AFAIK, the HDMI ouput never works on DK1 & DK2
At least with the vendor kernel, HDMI does work.
> - AFAIK, the status of BT & Wifi on DK2 is unknown
Also with the vendor kernel, I know they work. It would be good to make
sure they also work with the Buildroot defconfigs, that use the
upstream kernel.
> -CONFIG_USB_DWC2=y
> -CONFIG_USB_CHIPIDEA=y
> -CONFIG_USB_CHIPIDEA_HOST=y
> -CONFIG_USB_ISP1760=y
> -CONFIG_USB_HSIC_USB3503=y
> -CONFIG_USB_GPIO_VBUS=y
> -CONFIG_USB_ISP1301=y
> -CONFIG_USB_ULPI=y
I don't remember which USB controller is used, but I'm surprised by the
removal of CONFIG_USB_DWC2 as I thought it was the one used for the OTG
controller.
> CONFIG_TYPEC=y
> -CONFIG_TYPEC_STUSB=y
> +CONFIG_TYPEC_STUSB160X=y
Why?
> CONFIG_STM32_RPROC=y
> -CONFIG_RPMSG_VIRTIO=y
> -CONFIG_RPMSG_TTY=y
This is potentially useful to communicate with the Cortrex-M4.
> CONFIG_IIO=y
> CONFIG_IIO_SW_TRIGGER=y
> CONFIG_SD_ADC_MODULATOR=y
> CONFIG_STM32_ADC_CORE=y
> CONFIG_STM32_ADC=y
> -CONFIG_STM32_ADC_TEMP=y
Why?
> CONFIG_STM32_DFSDM_ADC=y
> -CONFIG_STM32_LPTIMER_CNT=y
Why?
> CONFIG_STM32_DAC=y
> CONFIG_IIO_HRTIMER_TRIGGER=y
> CONFIG_IIO_STM32_LPTIMER_TRIGGER=y
> @@ -175,7 +108,7 @@ CONFIG_PWM_STM32_LP=y
> CONFIG_PHY_STM32_USBPHYC=y
> CONFIG_NVMEM_STM32_ROMEM=y
> CONFIG_EXT4_FS=y
> -CONFIG_MSDOS_FS=y
> +CONFIG_EXT4_FS_POSIX_ACL=y
Why?
(The same question applied to the DK2 configuration, of course).
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-11-14 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 17:05 [Buildroot] [PATCH v2] board/stmicroelectronics/stm32mp157*-dk*: cleanup linux.config Francois Perrad
2021-11-14 15:26 ` Thomas Petazzoni [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=20211114162658.7ac403eb@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
--cc=fperrad@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