From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: f.fainelli@gmail.com, jonas.gorski@gmail.com, nbd@nbd.name,
toke@toke.dk, kvalo@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
chunkeey@gmail.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH v2 0/2] ath9k: of_init: add endian check
Date: Mon, 17 Apr 2023 07:35:07 +0200 [thread overview]
Message-ID: <20230417053509.4808-1-noltari@gmail.com> (raw)
Add new endian check flag to allow checking the endianness of EEPROM and swap
its values if needed.
This flag was already present on ath9k_platform_data as "endian_check".
For compatibility with current devices the AH_NO_EEP_SWAP flag will be
activated only when qca,endian-check isn't present in the device tree.
This is because some devices have the magic values swapped but not the actual
EEPROM data, so activating the flag for those devices will break them.
Álvaro Fernández Rojas (2):
dt-bindings: net: wireless: ath9k: document endian check
ath9k: fix calibration data endianness
.../devicetree/bindings/net/wireless/qca,ath9k.yaml | 5 +++++
drivers/net/wireless/ath/ath9k/init.c | 5 +++--
2 files changed, 8 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2023-04-17 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 5:35 Álvaro Fernández Rojas [this message]
2023-04-17 5:35 ` [PATCH v2 1/2] dt-bindings: net: wireless: ath9k: document endian check Álvaro Fernández Rojas
2023-04-17 7:19 ` Krzysztof Kozlowski
2023-04-17 9:38 ` Kalle Valo
2023-04-17 17:43 ` Álvaro Fernández Rojas
2023-04-17 5:35 ` [PATCH v2 2/2] ath9k: of_init: add " Álvaro Fernández Rojas
2023-04-17 9:21 ` Toke Høiland-Jørgensen
2023-04-17 17:54 ` Álvaro Fernández Rojas
2023-04-17 22:56 ` Toke Høiland-Jørgensen
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=20230417053509.4808-1-noltari@gmail.com \
--to=noltari@gmail.com \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@toke.dk \
/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).