Devicetree
 help / color / mirror / Atom feed
From: Thomas Gerner <thomas.gerner@muenchen-mail.de>
To: Shengyu Qu <wiagn233@outlook.com>,
	Drew Fustini <fustini@kernel.org>, Guo Ren <guoren@kernel.org>,
	Fu Wei <wefu@redhat.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Enable wifi on the BeagleV-Ahead
Date: Wed, 13 May 2026 19:38:24 +0200	[thread overview]
Message-ID: <86f7cb4e-9511-47a2-a2cb-4fedf3ae1ab8@muenchen-mail.de> (raw)
In-Reply-To: <TY4PR01MB14432F2BBDFF6E2C4AC79DD1E98392@TY4PR01MB14432.jpnprd01.prod.outlook.com>


Am 12.05.26 um 20:39 schrieb Shengyu Qu:
>> +
>> +    brcmf_pwrseq: brcmf-pwrseq {
>> +        compatible = "mmc-pwrseq-simple";
>> +        reset-gpios = <&gpio2 31 GPIO_ACTIVE_LOW>; /* WL-REG-ON */
>> +    };
>>   };
>
> I think such pwrseq won't work? Need to set timing parameter, for 
> example:
> https://github.com/torvalds/linux/blob/1d5dcaa3bd65f2e8c9baa14a393d3a2dc5db7524/arch/arm64/boot/dts/rockchip/rk3568-rock-3a.dts#L71 
>

I think this is not necessary. The WiFi chip gets powerd up with the 
board power and the power cannot be disabled. The only job for this 
pwrseq is to release gpio2 pin 31 when the kernel initialize the chip. 
According to the data sheet the release of the pin should happen not 
earlier than 2 cycles of the 32.768kHz clock after powered up. As the 
kernel start takes much longer than this 2 cycles and I think there is 
no extra timing necessary.

The broadcom driver has a also a property "reset-gpios", but this does 
not work. It does not configure the pin as output, it configure it as 
input. Then the driver does not initialize the chip. May be this is a 
bug in the broadcom driver, don't know.

Best regards
Thomas


  reply	other threads:[~2026-05-13 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 14:11 [PATCH] Enable wifi on the BeagleV-Ahead Thomas Gerner
2026-05-12  5:28 ` sashiko-bot
2026-05-12 17:33 ` Thomas Gerner
2026-05-12 18:39   ` Shengyu Qu
2026-05-13 17:38     ` Thomas Gerner [this message]
2026-05-13 23:43   ` sashiko-bot

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=86f7cb4e-9511-47a2-a2cb-4fedf3ae1ab8@muenchen-mail.de \
    --to=thomas.gerner@muenchen-mail.de \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fustini@kernel.org \
    --cc=guoren@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=wefu@redhat.com \
    --cc=wiagn233@outlook.com \
    /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