From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Nicolas Escande <nico.escande@gmail.com>,
Maharaja Kennadyrajan <maharaja.kennadyrajan@oss.qualcomm.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
Aishwarya R <aishwarya.r@oss.qualcomm.com>
Subject: Re: [PATCH ath-next v2] wifi: ath12k: add basic hwmon temperature reporting
Date: Thu, 19 Feb 2026 13:37:33 -0800 [thread overview]
Message-ID: <017ec99b-693f-47e5-ac38-6c207a32eb62@oss.qualcomm.com> (raw)
In-Reply-To: <DGITONL8L200.PJE38TDXYRQC@gmail.com>
On 2/19/2026 1:15 AM, Nicolas Escande wrote:
> On Thu Feb 19, 2026 at 8:34 AM CET, Maharaja Kennadyrajan wrote:
>> +ath12k-$(CONFIG_THERMAL) += thermal.o
>>
>
> I may be wrong but I do not see Kconfig changes that allows to actually build
> the new files. Is this intended ?
There is no configuration specifically for the driver -- it just follows
whatever has been configured globally. So CONFIG_THERMAL would need to be
enabled to have the file compiled, and CONFIG_HWMON would need to be enabled
to have the sysfs file exposed. ath10k and ath11k have the same logic.
/jeff
next prev parent reply other threads:[~2026-02-19 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 7:34 [PATCH ath-next v2] wifi: ath12k: add basic hwmon temperature reporting Maharaja Kennadyrajan
2026-02-19 9:15 ` Nicolas Escande
2026-02-19 21:37 ` Jeff Johnson [this message]
2026-02-20 9:26 ` Nicolas Escande
2026-02-23 11:21 ` Maharaja Kennadyrajan
2026-02-19 11:31 ` Pablo MARTIN-GOMEZ
2026-02-19 11:45 ` Maharaja Kennadyrajan
2026-02-19 21:44 ` Jeff Johnson
2026-02-20 9:55 ` Maharaja Kennadyrajan
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=017ec99b-693f-47e5-ac38-6c207a32eb62@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=aishwarya.r@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maharaja.kennadyrajan@oss.qualcomm.com \
--cc=nico.escande@gmail.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