Hi,
On Thu, Nov 12, 2020 at 12:09 PM Abhishek Kumar wrote:
>
> In some devices difference in chip-id should be enough to pick
> the right BDF. Add another support for chip-id based BDF selection.
> With this new option, ath10k supports 2 fallback options.
>
> The board name with chip-id as
Venkateswara Naralasetty wrote:
> This target IRAM recovery feature support is to copy target
> IRAM contents available at ATH10K_MEM_REGION_TYPE_REG to host
> memory for back up after firmware loaded. Target IRAM contents
> are copied to wmi memory chunks allocated for the
>
Jani Nikula writes:
> This is v2 of [1], with a number of cleanups added first based on
> Christoph's feedback, making the actual constness patch much smaller and
> cleaner.
>
> I don't know who actually maintains relay, it's not in MAINTAINERS -
> Cc'd Andrew just in case.
>
> I'd think it
On Thu, 19 Nov 2020, Christoph Hellwig wrote:
> But taking one step back: All instances implement create_buf_file
> and remove_buf_file, which makes sense as that is the prime aim
> of these methods. So there is no point in making those optional.
> subbuf_start_callback is overriden by two
Now that relay_open() accepts const callbacks, make relay callbacks
const.
Cc: Kalle Valo
Cc: ath10k@lists.infradead.org
Acked-by: Kalle Valo
Signed-off-by: Jani Nikula
---
drivers/net/wireless/ath/ath10k/spectral.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This is v2 of [1], with a number of cleanups added first based on
Christoph's feedback, making the actual constness patch much smaller and
cleaner.
I don't know who actually maintains relay, it's not in MAINTAINERS -
Cc'd Andrew just in case.
I'd think it would be simplest to queue patches 5-9
None of the relay users require the use of mutable structs for
callbacks, however the relay code does. Instead of assigning the default
callback for subbuf_start, add a wrapper to conditionally call the
client callback if available, and fall back to default behaviour
otherwise.
This lets all
Workaround to get WiFi working on Xiaomi Poco F1 (sdm845)
phone. We get a non-fatal QMI_ERR_MALFORMED_MSG_V01 error
message in ath10k_qmi_host_cap_send_sync(), but we can still
bring up WiFi services successfully on AOSP if we ignore it.
We suspect either the host cap is not implemented or there
The default value is true returned by ieee80211_chandef_he_6ghz_oper,
change it to true same with before.
Fixes: 1d00ce807efa ("mac80211: support S1G association")
Signed-off-by: Wen Gong
---
net/mac80211/util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git