linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org,
	Shahar S Matityahu <shahar.s.matityahu@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>
Subject: Re: [PATCH 4/7] iwlwifi: print fseq info upon fw assert
Date: Wed, 29 May 2019 17:39:49 +0300	[thread overview]
Message-ID: <87pno12ukq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20190529133955.31082-5-luca@coelho.fi> (Luca Coelho's message of "Wed, 29 May 2019 16:39:52 +0300")

Luca Coelho <luca@coelho.fi> writes:

> From: Shahar S Matityahu <shahar.s.matityahu@intel.com>
>
> Read fseq info from FW registers and print it upon fw assert.
> The print is needed since the fseq version coming from the TLV might
> not be the actual version that is used.
>
> Signed-off-by: Shahar S Matityahu <shahar.s.matityahu@intel.com>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>

[...]

> +void iwl_fw_error_print_fseq_regs(struct iwl_fw_runtime *fwrt)
> +{
> +	struct iwl_trans *trans = fwrt->trans;
> +	unsigned long flags;
> +	int i;
> +	struct {
> +		u32 addr;
> +		const char *str;
> +	} fseq_regs[] = {
> +		FSEQ_REG(FSEQ_ERROR_CODE),
> +		FSEQ_REG(FSEQ_TOP_INIT_VERSION),
> +		FSEQ_REG(FSEQ_CNVIO_INIT_VERSION),
> +		FSEQ_REG(FSEQ_OTP_VERSION),
> +		FSEQ_REG(FSEQ_TOP_CONTENT_VERSION),
> +		FSEQ_REG(FSEQ_ALIVE_TOKEN),
> +		FSEQ_REG(FSEQ_CNVI_ID),
> +		FSEQ_REG(FSEQ_CNVR_ID),
> +		FSEQ_REG(CNVI_AUX_MISC_CHIP),
> +		FSEQ_REG(CNVR_AUX_MISC_CHIP),
> +		FSEQ_REG(CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM),
> +		FSEQ_REG(CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR),
> +	};

Can fseq_regs be static const?

-- 
Kalle Valo

  reply	other threads:[~2019-05-29 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 13:39 [PATCH 0/7] wlwifi: fixes intended for 5.2 2019-05-29 Luca Coelho
2019-05-29 13:39 ` [PATCH 1/7] iwlwifi: mvm: remove d3_sram debugfs file Luca Coelho
2019-06-01  5:05   ` Kalle Valo
2019-05-29 13:39 ` [PATCH 2/7] iwlwifi: fix load in rfkill flow for unified firmware Luca Coelho
2019-05-29 13:39 ` [PATCH 3/7] iwlwifi: clear persistence bit according to device family Luca Coelho
2019-05-29 13:39 ` [PATCH 4/7] iwlwifi: print fseq info upon fw assert Luca Coelho
2019-05-29 14:39   ` Kalle Valo [this message]
2019-06-01 11:13     ` Luca Coelho
2019-05-29 13:39 ` [PATCH 5/7] iwlwifi: fix AX201 killer sku loading firmware issue Luca Coelho
2019-05-29 13:39 ` [PATCH 6/7] iwlwifi: Fix double-free problems in iwl_req_fw_callback() Luca Coelho
2019-05-29 13:39 ` [PATCH 7/7] iwlwifi: mvm: change TLC config cmd sent by rs to be async Luca Coelho

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=87pno12ukq.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    --cc=luciano.coelho@intel.com \
    --cc=shahar.s.matityahu@intel.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;
as well as URLs for NNTP newsgroup(s).