linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH 3/3] ath11k: add support for BSS coloring
Date: Mon, 22 Jun 2020 17:45:31 +0300	[thread overview]
Message-ID: <87h7v3f9bo.fsf@codeaurora.org> (raw)
In-Reply-To: <20200617150021.4183253-3-john@phrozen.org> (John Crispin's message of "Wed, 17 Jun 2020 17:00:21 +0200")

John Crispin <john@phrozen.org> writes:

> Whenever the MAC detects a color collision or any of its associated station
> detects one the FW will send out an event. Add the code to parse and handle
> this event. and pass the data up to mac80211.
>
> The FW does not provide an offload future such as the one used for CSA. The
> CCA process is hence triggered via the beacon offload tx completion events
> sent out by the FW.
>
> Signed-off-by: John Crispin <john@phrozen.org>

On what hardware and firmware did you test this? I'll add that to the
commit log.

> +	if (ev->obss_color_bitmap & BIT(arvif->vif->bss_conf.he_bss_color.color)) {
> +		/* FW sometime sends out stray events. Ignore them if our color is free */
> +		ieeee80211_obss_color_collision_notify(arvif->vif, ev->obss_color_bitmap);
> +
> +		ath11k_info(ab, "OBSS color collision detected vdev:%d, event:%d, bitmap:%08llx\n",
> +			    ev->vdev_id, ev->evt_type, ev->obss_color_bitmap);
> +	}

Is this really something so important that we should print it to the
log? What should the user do after seeing this warning?

And warnings should be printed with ath11k_warn(), but maybe this should
be a debug message?

-- 
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2020-06-22 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 15:00 [PATCH 1/3] nl80211: add support for BSS coloring John Crispin
2020-06-17 15:00 ` [PATCH 2/3] mac80211: " John Crispin
2020-06-17 15:00 ` [PATCH 3/3] ath11k: " John Crispin
2020-06-22 14:45   ` Kalle Valo [this message]
2020-06-23 21:53   ` Rajkumar Manoharan

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=87h7v3f9bo.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=john@phrozen.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).