[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <2B479B54-2784-4D75-BEE8-23A52EEFBF17@gmail.com>
Date: Wed, 27 Nov 2024 08:05:33 +0400
From: Christian Hewitt <christianshewitt@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Neil Armstrong <neil.armstrong@...aro.org>,
Kevin Hilman <khilman@...libre.com>,
Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Subject: Re: [PATCH] WIP: arm64: dts: meson: drop broadcom compatible from
reference board SDIO nodes
> On 24 Nov 2024, at 8:11 pm, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> wrote:
>
> On 24/11/2024 09:34, Christian Hewitt wrote:
>> Drop the Broadcom compatible and use a generic sdio identifier with the Amlogic
>
> 1. Heh, what? Why? This is not really explained and does not look
> sensible at all.
> 2. What is "generioc sdio identifier"?
>
>> reference boards. This allows a wider range of Android STB devices with QCA9377
>> and RTL8189ES/FS chips to have working WiFi when booting from the reference dtb
>
> Please wrap commit message according to Linux coding style / submission
> process (neither too early nor over the limit):
> https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
>
>> files. There is no observed impact on Broadcom devices.
>
> So how does it allow wider range of devices to have working wifi?
Sending patches while recovering from a 100km Triathlon last weekend
resulted in some formatting and submission mistakes - sorry for that :(
I’ll send a v2 shortly with reduced subject/line length and a better
description of the change and reasoning.
Christian
Powered by blists - more mailing lists