From: Michal Kazior <michal.kazior@tieto.com> To: Ben Greear <greearb@candelatech.com> Cc: Benjamin Berg <benjamin@sipsolutions.net>, Kalle Valo <kvalo@qca.qualcomm.com>, linux-wireless <linux-wireless@vger.kernel.org>, Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>, Sebastian Gottschall <s.gottschall@dd-wrt.com>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>, Simon Wunderlich <sw@simonwunderlich.de> Subject: Re: [PATCH] ath10k: Allow setting coverage class Date: Wed, 3 Aug 2016 09:09:31 +0200 [thread overview] Message-ID: <CA+BoTQkbM8uQoOWhXnKp+qJXxnnvHXeW4rV_fSuy3ftzLgMsww@mail.gmail.com> (raw) In-Reply-To: <579B71B4.7080206@candelatech.com> On 29 July 2016 at 17:09, Ben Greear <greearb@candelatech.com> wrote: > On 07/29/2016 07:52 AM, Benjamin Berg wrote: [...] >> Yeah, I am aware of the fact that the firmware may do internal resets >> from time to time. The interesting question (and one for which I do not >> know the answer) is whether we get a wmi or other event under all >> conditions where the register may be rewritten due to a reset. >> >> The current code will re-set the register value after any wmi event >> including debug messages. If this is not enough, then the only solution >> might be to periodically poll the register values instead of relying on >> a received event. > > You will get a dbglog event at least most of the time, so maybe that > will be good enough. But you need to remember you need to enable dbglog first to get these events. I guess when coverage class is set the driver could, internally, override dbglog mask so that these events are guaranteed to be reported for the purpose of properly refreshing registers on channel programming. At that point I guess the update hook could be just placed in dbglog handler alone instead of all over wmi_rx variants. Michał
WARNING: multiple messages have this Message-ID (diff)
From: Michal Kazior <michal.kazior@tieto.com> To: Ben Greear <greearb@candelatech.com> Cc: Simon Wunderlich <sw@simonwunderlich.de>, Benjamin Berg <benjamin@sipsolutions.net>, linux-wireless <linux-wireless@vger.kernel.org>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>, Kalle Valo <kvalo@qca.qualcomm.com>, Sebastian Gottschall <s.gottschall@dd-wrt.com>, Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de> Subject: Re: [PATCH] ath10k: Allow setting coverage class Date: Wed, 3 Aug 2016 09:09:31 +0200 [thread overview] Message-ID: <CA+BoTQkbM8uQoOWhXnKp+qJXxnnvHXeW4rV_fSuy3ftzLgMsww@mail.gmail.com> (raw) In-Reply-To: <579B71B4.7080206@candelatech.com> On 29 July 2016 at 17:09, Ben Greear <greearb@candelatech.com> wrote: > On 07/29/2016 07:52 AM, Benjamin Berg wrote: [...] >> Yeah, I am aware of the fact that the firmware may do internal resets >> from time to time. The interesting question (and one for which I do not >> know the answer) is whether we get a wmi or other event under all >> conditions where the register may be rewritten due to a reset. >> >> The current code will re-set the register value after any wmi event >> including debug messages. If this is not enough, then the only solution >> might be to periodically poll the register values instead of relying on >> a received event. > > You will get a dbglog event at least most of the time, so maybe that > will be good enough. But you need to remember you need to enable dbglog first to get these events. I guess when coverage class is set the driver could, internally, override dbglog mask so that these events are guaranteed to be reported for the purpose of properly refreshing registers on channel programming. At that point I guess the update hook could be just placed in dbglog handler alone instead of all over wmi_rx variants. Michał _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-08-03 7:09 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-07-27 8:33 [PATCH] ath10k: Allow setting coverage class Benjamin Berg 2016-07-27 8:33 ` Benjamin Berg 2016-07-27 9:15 ` Michal Kazior 2016-07-27 9:15 ` Michal Kazior 2016-07-27 10:28 ` kbuild test robot 2016-07-27 10:28 ` kbuild test robot 2016-07-27 17:26 ` Ben Greear 2016-07-27 17:26 ` Ben Greear 2016-07-29 14:52 ` Benjamin Berg 2016-07-29 14:52 ` Benjamin Berg 2016-07-29 15:09 ` Ben Greear 2016-07-29 15:09 ` Ben Greear 2016-07-29 16:38 ` Sebastian Gottschall 2016-07-29 16:38 ` Sebastian Gottschall 2016-08-03 7:09 ` Michal Kazior [this message] 2016-08-03 7:09 ` Michal Kazior
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=CA+BoTQkbM8uQoOWhXnKp+qJXxnnvHXeW4rV_fSuy3ftzLgMsww@mail.gmail.com \ --to=michal.kazior@tieto.com \ --cc=ath10k@lists.infradead.org \ --cc=benjamin@sipsolutions.net \ --cc=greearb@candelatech.com \ --cc=kvalo@qca.qualcomm.com \ --cc=linux-wireless@vger.kernel.org \ --cc=mathias.kretschmer@fit.fraunhofer.de \ --cc=s.gottschall@dd-wrt.com \ --cc=sw@simonwunderlich.de \ /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: linkBe 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.