mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacobe Zang <jacobe.zang@wesion.com>,
	marcan@marcan.st, sven@svenpeter.dev, alyssa@rosenzweig.io,
	robh@kernel.org, heiko@sntech.de, krzk+dt@kernel.org
Cc: linux-rockchip@lists.infradead.org, dsimic@manjaro.org,
	conor+dt@kernel.org, asahi@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, nick@khadas.com
Subject: Re: [PATCH v12 2/2] arm64: dts: apple: add "brcm,bcm4329-fmac" fallback compatible
Date: Wed, 28 Aug 2024 11:08:34 +0200	[thread overview]
Message-ID: <9180e80b-f464-4a84-8c58-35383beec637@kernel.org> (raw)
In-Reply-To: <c5047173-d569-42d4-9676-4679100da118@wesion.com>

On 28/08/2024 08:13, Jacobe Zang wrote:
> 
> 
> On 2024/8/28 13:56, Krzysztof Kozlowski wrote:
>> On 28/08/2024 05:39, Jacobe Zang wrote:
>>> Broadcom driver need to check "brcm,bcm4329-fmac" compatible. Before
>>
>> What for?
>>
> 
> It matches the changes in the other series that I sent.

Commit msg did not explain this at all. Anyway, then bindings should
provide proper rationale without referring to "driver" as the reason.

> 
>>> PCIe devices used PCI ID as base compabile so add it as fallback
>>> compatible to pass the check.
>>>
>>> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
>>> ---
>>>   arch/arm64/boot/dts/apple/t8103-jxxx.dtsi | 2 +-
>>>   arch/arm64/boot/dts/apple/t8112-j413.dts  | 2 +-
>>>   arch/arm64/boot/dts/apple/t8112-j493.dts  | 2 +-
>>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/apple/t8103-jxxx.dtsi b/arch/arm64/boot/dts/apple/t8103-jxxx.dtsi
>>> index 5988a4eb6efaa..4b021626d4692 100644
>>> --- a/arch/arm64/boot/dts/apple/t8103-jxxx.dtsi
>>> +++ b/arch/arm64/boot/dts/apple/t8103-jxxx.dtsi
>>> @@ -72,7 +72,7 @@ hpm1: usb-pd@3f {
>>>   &port00 {
>>>   	bus-range = <1 1>;
>>>   	wifi0: network@0,0 {
>>> -		compatible = "pci14e4,4425";
>>> +		compatible = "pci14e4,4425", "brcm,bcm4329-fmac";
>>
>> So devices are not compatible, but your argument is that driver needs to
>> do something here? That's not enough.
>>
> Before this change, the check of "brcm,bcm4329-fmac" compatible is set 
> at the end of probe function for SDIO devices which need IRQ. But after 
> this change I set it to the top as the first check. So I add this 
> fallback compatible to the Apple's DTS.

You are not listening, I think, and still keep talking about driver. It
has nothing to do. Fix your driver.

> 
> Oh..I got what you mean. Maybe my commit message is not clearly. It is 
> no need to mention driver in it. Because the intent of adding the 
> "brcm,bcm4329-fmac" compatible is to conform to the bindings.

Explain the hardware, not the driver. DTS represents hardware, not drivers.

Best regards,
Krzysztof


  reply	other threads:[~2024-08-28  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28  3:39 [PATCH v12 0/2] Add Wi-Fi support for Khadas Edge2 and fallback compatible for Apple Jacobe Zang
2024-08-28  3:39 ` [PATCH v12 1/2] arm64: dts: rockchip: Add AP6275P wireless support to Khadas Edge 2 Jacobe Zang
2024-08-28  3:39 ` [PATCH v12 2/2] arm64: dts: apple: add "brcm,bcm4329-fmac" fallback compatible Jacobe Zang
2024-08-28  5:56   ` Krzysztof Kozlowski
2024-08-28  6:13     ` Jacobe Zang
2024-08-28  9:08       ` Krzysztof Kozlowski [this message]
2024-08-28  7:58 [PATCH v12 0/2] (no cover subject) Jacobe Zang
2024-08-28  7:58 ` [PATCH v12 2/2] arm64: dts: apple: add "brcm,bcm4329-fmac" fallback compatible Jacobe Zang

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=9180e80b-f464-4a84-8c58-35383beec637@kernel.org \
    --to=krzk@kernel.org \
    --cc=alyssa@rosenzweig.io \
    --cc=asahi@lists.linux.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=jacobe.zang@wesion.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=marcan@marcan.st \
    --cc=nick@khadas.com \
    --cc=robh@kernel.org \
    --cc=sven@svenpeter.dev \
    /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

all inboxes | Powered by JetHome®