Hi Paul, >-----Original Message----- >From: Paul Menzel <pmenzel@xxxxxxxxxxxxx> >Sent: Wednesday, June 26, 2024 5:56 PM >To: K, Kiran <kiran.k@xxxxxxxxx> >Cc: Srivatsa, Ravishankar <ravishankar.srivatsa@xxxxxxxxx>; Tumkur Narayan, >Chethan <chethan.tumkur.narayan@xxxxxxxxx>; Devegowda, Chandrashekar ><chandrashekar.devegowda@xxxxxxxxx>; Satija, Vijay <vijay.satija@xxxxxxxxx>; >linux-bluetooth@xxxxxxxxxxxxxxx >Subject: Re: [PATCH v3] Bluetooth: btintel: Allow lowering of drive strength of >BRI > >Dear Kiran, > > >Thank you for the patch. > >Am 26.06.24 um 11:28 schrieb Kiran K: >> BRI (Bluetooth Radio Interface) traffic from CNVr to CNVi was found >> causing cross talk step errors to WiFi. As a workaround, driver needs >> to reduce the drive strength of BRI. During *setup*, driver reads the >> drive strength value from efi variable and passes it to the controller >> via vendor specific command with opcode 0xfc0a. > >I am still surprised this is done via an EFI variable. Could you please add a >reference to section in the UEFI(?) specification? Hopefully that explains who is >supposed to set the variable. "UefiCnvCommonDSBR" efi variable would be created by OEMs. > >[…] > > >Kind regards, > >Paul Thanks, Kiran
