linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
	Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH v2 5/5] wcn36xx: Set PHY into correct mode for 80MHz channel width
Date: Mon, 31 Aug 2020 12:30:31 +0100	[thread overview]
Message-ID: <51f134b0-cde8-595b-b3b1-e6b3b5b151aa@linaro.org> (raw)
In-Reply-To: <CAMZdPi_YB7aurY_XsbPeqytPNBUteRkh+VH79mHfESL=rf5LGw@mail.gmail.com>

On 31/08/2020 11:08, Loic Poulain wrote:
> Hi Bryan,
> 
> On Sat, 29 Aug 2020 at 05:39, Bryan O'Donoghue
> <bryan.odonoghue@linaro.org> wrote:
>>
>> For the 80MHz channel we need to set the PHY mode to one of four PHY modes
>> that span the 80MHz range.
> 
> What about 40Mhz bonding?

The existing code handles 40MHz HT in wcn36xx_smd_join()



      reply	other threads:[~2020-08-31 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  3:39 [PATCH v2 0/5] wcn36xx: PHY modifications to support 80MHz operation Bryan O'Donoghue
2020-08-29  3:39 ` [PATCH v2 1/5] wcn36xx: Add accessor macro HW_VALUE_CHANNEL for hardware channels Bryan O'Donoghue
2020-08-29  3:39 ` [PATCH v2 2/5] wcn36xx: Use HW_VALUE_CHANNEL macro to get channel number Bryan O'Donoghue
2020-08-29  3:39 ` [PATCH v2 3/5] wcn36xx: Add accessor macro HW_VALUE_PHY for PHY settings Bryan O'Donoghue
2020-08-29  3:39 ` [PATCH v2 4/5] wcn36xx: Encode PHY mode for 80MHz channel in hw_value Bryan O'Donoghue
2020-08-29  3:39 ` [PATCH v2 5/5] wcn36xx: Set PHY into correct mode for 80MHz channel width Bryan O'Donoghue
2020-08-31 10:08   ` Loic Poulain
2020-08-31 11:30     ` Bryan O'Donoghue [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=51f134b0-cde8-595b-b3b1-e6b3b5b151aa@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=shawn.guo@linaro.org \
    --cc=wcn36xx@lists.infradead.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).