[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230609082348.GK8160@alpha.franken.de>
Date: Fri, 9 Jun 2023 10:23:48 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Paul Cercueil <paul@...pouillou.net>
Cc: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
"H . Nikolaus Schaller" <hns@...delico.com>,
linux-mips@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, list@...ndingux.net
Subject: Re: [PATCH 0/9] MIPS: CI20: Add WiFi / Bluetooth support
On Sun, Jun 04, 2023 at 04:56:33PM +0200, Paul Cercueil wrote:
> Hi,
>
> Here's a set of patches to add support for the WiFi / Bluetooth chip on
> the CI20.
>
> WiFi works pretty well, provided it is used with the latest firmware
> provided by linux-firmware. Bluetooth does not work very well here, as
> I cannot get my wireless keyboard to pair; but it does detect it, and it
> does see they key presses when I type the pairing code.
>
> I only tested with a somewhat recent (~2022) Buildroot-based userspace.
> I enabled WEXT compatibility because the CI20 is typically used with a
> very old userspace, but I did not try to use it with old tools like
> ifconfig/iwconfig.
>
> Cheers,
> -Paul
>
> Paul Cercueil (9):
> MIPS: DTS: CI20: Fix regulators
> MIPS: DTS: CI20: Fix ACT8600 regulator node names
> MIPS: DTS: CI20: Add parent supplies to ACT8600 regulators
> MIPS: DTS: CI20: Do not force-enable CIM and WiFi regulators
> MIPS: DTS: CI20: Misc. cleanups
> MIPS: DTS: CI20: Parent MSCMUX clock to MPLL
> MIPS: DTS: CI20: Enable support for WiFi / Bluetooth
> MIPS: configs: CI20: Regenerate defconfig
> MIPS: configs: CI20: Enable WiFi / Bluetooth
>
> arch/mips/boot/dts/ingenic/ci20.dts | 148 +++++++++++++++++++---------
> arch/mips/configs/ci20_defconfig | 47 ++++++---
> 2 files changed, 133 insertions(+), 62 deletions(-)
>
> --
> 2.39.2
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists