From: Kalle Valo <kvalo@codeaurora.org>
To: ryanhsu@codeaurora.org
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
ryanhsu@codeaurora.org
Subject: Re: [1/2] ath10k: enable QCA6174/QCA9377 to read the chip temperature
Date: Thu, 29 Mar 2018 08:52:30 +0000 (UTC) [thread overview]
Message-ID: <20180329085230.48C6860C64@smtp.codeaurora.org> (raw)
In-Reply-To: <1521183942-4291-1-git-send-email-ryanhsu@codeaurora.org>
ryanhsu@codeaurora.org wrote:
> The firmware of QCA6174/QCA9377 already support the feature, just enable
> it to be able to handle the get_temperature command and process the event.
>
> You can read the temperature by using the hwmon interface,
>
> cat /sys/class/ieee80211/phy*/device/hwmon/hwmon2/temp1_input
>
> Verified with the following hardware and software combination,
> QCA6174, only firmware-4.bin doesn't support this, otherwise all support.
> QCA9377, all the firmwares upstreamed support this command
>
> Signed-off-by: Ryan Hsu <ryanhsu@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
2 patches applied to ath-next branch of ath.git, thanks.
e98199a8c27f ath10k: enable QCA6174/QCA9377 to read the chip temperature
e3814bec380f ath10k: add FW API 6 firmware image for QCA9377
--
https://patchwork.kernel.org/patch/10286439/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-03-29 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 7:05 [PATCH 1/2] ath10k: enable QCA6174/QCA9377 to read the chip temperature ryanhsu
2018-03-16 7:05 ` ryanhsu
2018-03-16 7:05 ` [PATCH 2/2] ath10k: add FW API 6 firmware image for QCA9377 ryanhsu
2018-03-16 7:05 ` ryanhsu
2018-03-29 8:52 ` Kalle Valo [this message]
2018-03-29 8:52 ` [1/2] ath10k: enable QCA6174/QCA9377 to read the chip temperature Kalle Valo
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=20180329085230.48C6860C64@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ryanhsu@codeaurora.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.