Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sdtweak poll_once doesn't work on Pi 4 #3286

Closed
XECDesign opened this issue Oct 14, 2019 · 9 comments
Closed

sdtweak poll_once doesn't work on Pi 4 #3286

XECDesign opened this issue Oct 14, 2019 · 9 comments
Assignees

Comments

@XECDesign
Copy link
Contributor

When network booting a pi for with dtoverlay=sdtweak,poll_once, the card is still polled, causing log spam every 10 seconds:

[  144.474158] mmc0: Timeout waiting for hardware cmd interrupt.
[  144.474182] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[  144.474199] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[  144.474205] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[  144.474213] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[  144.474221] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[  144.474228] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[  144.474234] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[  144.474242] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[  144.474250] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[  144.474257] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[  144.474262] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[  144.474267] mmc0: sdhci: Cmd:       0x0000371a | Max curr: 0x00080008
[  144.474275] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[  144.474280] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[  144.474284] mmc0: sdhci: Host ctl2: 0x00000000
[  144.474288] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[  144.474293] mmc0: sdhci: ============================================
@pelwell
Copy link
Contributor

pelwell commented Oct 14, 2019

The immediate cause of sdtweak's failure to set the non-removable flag on pi4 is that it isn't meant to:

pi@raspberrypi:~ $ dtoverlay -h sdtweak
Name:   sdtweak

Info:   Tunes the bcm2835-sdhost SD/MMC driver
        N.B. This functionality is now available via the sd_* dtparams in the
        base DTB.
...

What is needed is a generic sd_pollonce dtparam, which is easy enough to add. However, it might not be what you want in that may not react well when an SD card is removed (or inserted late).

Perhaps what is really needed, in addition to sd_pollonce, is a driver change to reduce the log spam, perhaps making it conditional on sd_debug.

@pelwell pelwell self-assigned this Oct 16, 2019
@nniv-cmyk
Copy link

can this be resolved, please?

pelwell pushed a commit that referenced this issue Jan 30, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
@pelwell
Copy link
Contributor

pelwell commented Jan 30, 2020

I've pushed updated .dts files to rpi-4.19.y that add sd_poll_once dtparams to all downstream .dtbs. You can grab a pre-built version of bcm2711-rpi-4-b.dtb here. Use with dtparam=sd_poll_once.

popcornmix added a commit to raspberrypi/firmware that referenced this issue Jan 30, 2020
See: raspberrypi/linux#3434

kernel: adds LED OFF feature to HiFiBerry DAC+ADC sound card
See: raspberrypi/linux#3435

kernel: adds LED OFF feature to HiFiBerry DAC+/DAC+PRO sound cards
See: raspberrypi/linux#3436

kernel: fix master mode settings of HiFiBerry DAC+ADC PRO card
See: raspberrypi/linux#3424

kernel: pisound: Added reading Pisound board hardware revision and exposing it
See: raspberrypi/linux#3425

kernel: Fix i2c-pwm-pca9685a overlay
See: raspberrypi/linux#3431

kernel: tty: amba-pl011: Add un/throttle support
kernel: tty: amba-pl011: Avoid rare write-when-full error
See: #1150

kernel: ARM: dts: Declare RPi 4B SD card power regulator

kernel: usb: xhci: Raspberry Pi FW loader for VIA VL805

kernel: overlays: Correct the eth_led* colour assignments
See: #1311

kernel: overlays: Remove hack from uart0 overlay
See: raspberrypi/linux#2856

kernel: ARM: dts: Add sd_poll_once dtparam to bcm283x/2711
See: raspberrypi/linux#3286

firmware: isp/tuner: Resetting to a lamp mode cancels manual_gains_used_

firmware: board_info: Fix uninitialised phy_addr handling in network boot

firmware: IL video_decode: Default to H264 as MPEG4 isn't supported

firmware: IL egl_render: Fail the create on Pi4

firmware: arm_dispmanx: Column pitch for YUV10COL is in lines not bytes

firmware: platform: 2711: Also add chicken bits to dvfs voltage

firmware: MMAL / video_render: Allow column stride to be set on column formats

firmware: vc_image/video_decode: Move +16 lines for di_adv from vc_image to decoder
popcornmix added a commit to Hexxeh/rpi-firmware that referenced this issue Jan 30, 2020
See: raspberrypi/linux#3434

kernel: adds LED OFF feature to HiFiBerry DAC+ADC sound card
See: raspberrypi/linux#3435

kernel: adds LED OFF feature to HiFiBerry DAC+/DAC+PRO sound cards
See: raspberrypi/linux#3436

kernel: fix master mode settings of HiFiBerry DAC+ADC PRO card
See: raspberrypi/linux#3424

kernel: pisound: Added reading Pisound board hardware revision and exposing it
See: raspberrypi/linux#3425

kernel: Fix i2c-pwm-pca9685a overlay
See: raspberrypi/linux#3431

kernel: tty: amba-pl011: Add un/throttle support
kernel: tty: amba-pl011: Avoid rare write-when-full error
See: raspberrypi/firmware#1150

kernel: ARM: dts: Declare RPi 4B SD card power regulator

kernel: usb: xhci: Raspberry Pi FW loader for VIA VL805

kernel: overlays: Correct the eth_led* colour assignments
See: raspberrypi/firmware#1311

kernel: overlays: Remove hack from uart0 overlay
See: raspberrypi/linux#2856

kernel: ARM: dts: Add sd_poll_once dtparam to bcm283x/2711
See: raspberrypi/linux#3286

firmware: isp/tuner: Resetting to a lamp mode cancels manual_gains_used_

firmware: board_info: Fix uninitialised phy_addr handling in network boot

firmware: IL video_decode: Default to H264 as MPEG4 isn't supported

firmware: IL egl_render: Fail the create on Pi4

firmware: arm_dispmanx: Column pitch for YUV10COL is in lines not bytes

firmware: platform: 2711: Also add chicken bits to dvfs voltage

firmware: MMAL / video_render: Allow column stride to be set on column formats

firmware: vc_image/video_decode: Move +16 lines for di_adv from vc_image to decoder
pelwell pushed a commit that referenced this issue Feb 5, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
pelwell pushed a commit that referenced this issue Feb 5, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Feb 6, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Feb 6, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Feb 20, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Feb 20, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Feb 25, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Feb 25, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Mar 6, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Mar 10, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Mar 23, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Mar 23, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Mar 27, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Mar 27, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Apr 1, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Apr 1, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Apr 7, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Apr 16, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Apr 16, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Apr 27, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue May 4, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue May 11, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue May 20, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue May 20, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Jun 3, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
jpuhlman pushed a commit to MontaVista-OpenSourceTechnology/linux-mvista that referenced this issue Jun 8, 2020
Source: kernel.org
MR: 103889
Type: Enhancement
Disposition: Merged from https://github.com/raspberrypi/linux.git rpi-5.4.y
ChangeID: abbd782ecdafba3ab6823faddfff3ad0d7b1d34d
Description:

The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: raspberrypi/linux#3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
Signed-off-by: Corey Minyard <cminyard@mvista.com>
popcornmix pushed a commit that referenced this issue Jun 10, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Jun 17, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
@ricktendo
Copy link

After using sd_poll_once now the green LED does not work

popcornmix pushed a commit that referenced this issue Jun 26, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Jul 1, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
popcornmix pushed a commit that referenced this issue Jul 13, 2020
The old sdtweak overlay allowed the SD interface to be effectively
disabled unless there was a card present at boot time, but that
overlay doesn't work on bcm2711 and has largely been replaced by
a set of sd_* dtparams (which have the advantage of being board-
specific.

Add an sd_poll_once dtparam to allow the same functionality on
all Raspberry Pi boards.

See: #3286

Signed-off-by: Phil Elwell <phil@raspberrypi.org>
@ctborg
Copy link

ctborg commented Nov 3, 2020

Hi @pelwell you pushed a build to Google Drive back in January that fixed this issue. Any chance you can post the patch here?

@pelwell
Copy link
Contributor

pelwell commented Nov 3, 2020

As the sdtweak documentation says, the functionality it provides is now available via the board-specific dtparams:

dtparam=sd_poll_once

sdtweak is effectively deprecated, and will be formally deprecated and removed.

@ssackett
Copy link

@pelwell

Hi,

I am hoping you can help me with a problem similar to the one in this thread.

I have a PI 4B and am experiencing a kworker that hogs the cpu only when using WIFI. I have updated the kernel to 5.10.16-v7l+ and added "dtparam=sd_poll_once=on" to config.txt. I have verified that "sd_poll_once" is active using "dtc -I fs /proc/device-tree" which shows "sd_poll_once = "\0\0\0?non-removable?";". None of these changes fixed the problem.

Using top the the first two lines are:

1387 root 20 0 0 0 0 I 21.6 0.0 0:16.66 kworker/u8:2-brcmf_wq/mmc1:0001:1
839 root 20 0 6964 2380 4 S 14.0 0.1 0:18.22 vhusbdarmpi4

The offending kworker always shows as "kworker/u8:2-brcmf_wq/mmc1:0001:1" with the number after "/u8:" changing between 2, 3, and 4. Also the number is followed alternately by "+" and "-" (ie: "u8:2+brcmf" and "u8:2-brcmf").

The process "vhusbdarmpi4" is running as a service started by systemd, it is communicating via WIFI and is running a USBIP protocol. If I use a wired connection instead of WIFI the kworker disappears and the service runs as expected.

Thanks,

Steve

@pelwell
Copy link
Contributor

pelwell commented Feb 22, 2021

Please start a new thread for a new issue.

@andrewufrank
Copy link

andrewufrank commented Apr 18, 2021

I have observed that the patch to insert the sd_poll_once dtparam is not in the raspi-firmware bmc2711-rpi-4-b.dtb for bullseye and therefore it is not surprising that the dtparam does not have an effect. I tried to copy the new version from the linux project to the firmware project, but do not understand about the necessary conversion etc. What are the correct procedures to have this change arrive in the firmware used for bullseye? I pose this question in both, the firmware and the linux project, not knowing who should act. Thank you for help and clarification!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants