From: Kalle Valo <kvalo@codeaurora.org>
To: Jouni Malinen <jouni@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Abinaya Kalaiselvan <akalaise@codeaurora.org>,
Jouni Malinen <jouni@codeaurora.org>
Subject: Re: [PATCH] ath10k: Fix device boot error
Date: Wed, 20 Oct 2021 07:55:42 +0000 (UTC) [thread overview]
Message-ID: <163471653903.23156.15370975982440752540.kvalo@codeaurora.org> (raw)
In-Reply-To: <20210913175048.192812-1-jouni@codeaurora.org>
Jouni Malinen <jouni@codeaurora.org> wrote:
> From: Abinaya Kalaiselvan <akalaise@codeaurora.org>
>
> mask value ATH10K_FW_CRASH_DUMP_RAM_DATA is not mandatory to get iram
> mem layout. So introduced ath10k_coredump_get_hw_mem_layout to copy
> hardware memory layout.
>
> This fixes the below boot error:
> [ 17.468882] ath10k_pci 0000:06:00.0: failed to copy target iram contents: -12
> [ 17.513925] ath10k_pci 0000:06:00.0: could not init core (-12)
> [ 17.517635] ath10k_pci 0000:06:00.0: could not probe fw (-12)
>
> Tested-on: QCA9984 X86 10.4-3.9.0.2-00139
>
> Fixes: 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
> Signed-off-by: Abinaya Kalaiselvan <akalaise@codeaurora.org>
> Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
> Reported-by: kernel test robot <lkp@intel.com>
The patch had multiple issues so I sent v2:
https://patchwork.kernel.org/project/linux-wireless/patch/20211020075054.23061-1-kvalo@codeaurora.org/
Patch set to Changes Requested.
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210913175048.192812-1-jouni@codeaurora.org/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-10-20 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 17:50 [PATCH] ath10k: Fix device boot error Jouni Malinen
2021-09-14 3:20 ` kernel test robot
2021-10-20 7:55 ` Kalle Valo [this message]
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=163471653903.23156.15370975982440752540.kvalo@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akalaise@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=jouni@codeaurora.org \
--cc=linux-wireless@vger.kernel.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 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).