linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Duje Mihanović" <duje@dujemihanovic.xyz>
To: Brian Norris <briannorris@chromium.org>, Karel Balej <balejk@matfyz.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Francesco Dolcini <francesco@dolcini.it>,
	Ulf Hansson <ulf.hansson@linaro.org>, Frank Li <Frank.Li@nxp.com>,
	linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org, Jeff Chen <jeff.chen_1@nxp.com>,
	Peng Fan <peng.fan@nxp.com>
Subject: Re: [DONOTAPPLY RFC PATCH v2 4/4] arm64: dts: samsung,coreprimevelte: add wifi node
Date: Fri, 12 Dec 2025 23:44:33 +0100	[thread overview]
Message-ID: <5962754.DvuYhMxLoT@radijator> (raw)
In-Reply-To: <DEWJTWZ6Q51B.13HQYMDJZRFWA@matfyz.cz>

On Friday, 12 December 2025 22:17:12 Central European Standard Time Karel 
Balej wrote:
> Duje Mihanović, 2025-12-12T15:55:48+01:00:
> > On 12/12/25 09:36, Karel Balej wrote:
> >> Not having any board schematics, I don't really know what exactly the
> >> regulator's purpose is. As I mentioned in the commit message, the
> >> communication with the chipset seems to work even if this is disabled
> >> (e. g. FW loads, networks can be scanned for,...) which doesn't seem
> >> like it should be the case if this was a main power supply for the bus,
> >> only actual connecting to networks doesn't work (gives
> >> CONNECT_ERR_ASSOC_ERR_TIMEOUT errors).
> > 
> > To me, this strongly suggests that the regulator powers the WiFi
> > transmitter or at least a part of it (such as the RF amp).
> 
> Something like this occurred to me too but would the chip even see the
> networks if this was the case? Although you are right that it could only
> power some specific part of the radio.

AFAIK you don't need the transmitter to capture and parse beacon frames. Of 
course, connecting to networks is a completely different story.

Regards,
--
Duje





  reply	other threads:[~2025-12-12 22:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-26 18:20 [DONOTAPPLY RFC PATCH v2 0/4] WiFi support for samsung,coreprimevelte Karel Balej
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 1/4] dt-bindings: mwifiex: document use with the SD8777 chipset Karel Balej
2025-12-03 21:50   ` Brian Norris
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 2/4] net: mwifiex: add support for " Karel Balej
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 3/4] DONOTMERGE: net: mwifiex: fix timeouts with the SD8777 chip Karel Balej
2025-12-03 21:46   ` Brian Norris
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 4/4] arm64: dts: samsung,coreprimevelte: add wifi node Karel Balej
2025-12-03 21:47   ` Brian Norris
2025-12-12  8:36     ` Karel Balej
2025-12-12 14:55       ` Duje Mihanović
2025-12-12 21:17         ` Karel Balej
2025-12-12 22:44           ` Duje Mihanović [this message]
2025-11-27 15:29 ` [DONOTAPPLY RFC PATCH v2 0/4] WiFi support for samsung,coreprimevelte Karel Balej
2025-11-28 17:05   ` Francesco Dolcini
2025-12-01 16:25     ` Karel Balej

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=5962754.DvuYhMxLoT@radijator \
    --to=duje@dujemihanovic.xyz \
    --cc=Frank.Li@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=balejk@matfyz.cz \
    --cc=briannorris@chromium.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco@dolcini.it \
    --cc=gregory.clement@bootlin.com \
    --cc=jeff.chen_1@nxp.com \
    --cc=johannes@sipsolutions.net \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=ulf.hansson@linaro.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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;
as well as URLs for NNTP newsgroup(s).