netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Evan Quan <evan.quan@amd.com>
Cc: lenb@kernel.org, alexander.deucher@amd.com,
	christian.koenig@amd.com, Xinhui.Pan@amd.com, airlied@gmail.com,
	daniel@ffwll.ch, johannes@sipsolutions.net, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	mdaenzer@redhat.com, maarten.lankhorst@linux.intel.com,
	tzimmermann@suse.de, hdegoede@redhat.com, jingyuwang_vip@163.com,
	lijo.lazar@amd.com, jim.cromie@gmail.com, bellosilicio@gmail.com,
	andrealmeid@igalia.com, trix@redhat.com, jsg@jsg.id.au,
	arnd@arndb.de, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH V4 1/8] drivers/acpi: Add support for Wifi band RF mitigations
Date: Fri, 23 Jun 2023 10:57:38 -0500	[thread overview]
Message-ID: <c518da2a-5ba5-af7e-e26d-1973db7b4c9e@amd.com> (raw)
In-Reply-To: <CAJZ5v0iqy0yMJP5H7ub67R8R6i42=TcS_6+VF-+fWrM-9tYFQA@mail.gmail.com>


On 6/23/2023 9:52 AM, Rafael J. Wysocki wrote:
> On Wed, Jun 21, 2023 at 7:47 AM Evan Quan <evan.quan@amd.com> wrote:
>> From: Mario Limonciello <mario.limonciello@amd.com>
>>
>> Due to electrical and mechanical constraints in certain platform designs
>> there may be likely interference of relatively high-powered harmonics of
>> the (G-)DDR memory clocks with local radio module frequency bands used
>> by Wifi 6/6e/7.
>>
>> To mitigate this, AMD has introduced an ACPI based mechanism that
>> devices can use to notify active use of particular frequencies so
>> that devices can make relative internal adjustments as necessary
>> to avoid this resonance.
>>
>> In order for a device to support this, the expected flow for device
>> driver or subsystems:
>>
>> Drivers/subsystems contributing frequencies:
>>
>> 1) During probe, check `wbrf_supported_producer` to see if WBRF supported
> The prefix should be acpi_wbrf_ or acpi_amd_wbrf_ even, so it is clear
> that this uses ACPI and is AMD-specific.

I guess if we end up with an intermediary library approach
wbrf_supported_producer makes sense and that could call acpi_wbrf_*.

But with no intermediate library your suggestion makes sense.

I would prefer not to make it acpi_amd as there is no reason that
this exact same problem couldn't happen on an
Wifi 6e + Intel SOC + AMD dGPU design too and OEMs could use the
same mitigation mechanism as Wifi6e + AMD SOC + AMD dGPU too.

>
> Whether or not there needs to be an intermediate library wrapped
> around this is a different matter.

  reply	other threads:[~2023-06-23 15:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  5:45 [PATCH V4 0/8] Support Wifi RFI interference mitigation feature Evan Quan
2023-06-21  5:45 ` [PATCH V4 1/8] drivers/acpi: Add support for Wifi band RF mitigations Evan Quan
2023-06-21 15:36   ` Andrew Lunn
2023-06-21 15:39     ` Johannes Berg
2023-06-21 16:14       ` Andrew Lunn
2023-06-21 16:23         ` Limonciello, Mario
2023-06-21 16:31           ` Andrew Lunn
2023-06-21 16:40             ` Limonciello, Mario
2023-06-21 17:20               ` Andrew Lunn
2023-06-21 16:37         ` Johannes Berg
2023-06-21 16:15       ` Limonciello, Mario
2023-06-21 16:52         ` Andrew Lunn
2023-06-21 17:08           ` Limonciello, Mario
2023-06-21 17:26             ` Andrew Lunn
2023-06-21 17:43               ` Limonciello, Mario
2023-06-21 18:30                 ` Andrew Lunn
2023-06-21 18:50                   ` Limonciello, Mario
2023-06-21 19:25                     ` Andrew Lunn
2023-06-21 22:18                       ` Johannes Berg
2023-06-22  1:55                         ` Andrew Lunn
2023-06-22 20:28                           ` Limonciello, Mario
2023-06-22 21:20                     ` Andrew Lunn
2023-06-23 14:52   ` Rafael J. Wysocki
2023-06-23 15:57     ` Limonciello, Mario [this message]
2023-06-23 16:28       ` Rafael J. Wysocki
2023-06-23 16:48         ` Limonciello, Mario
2023-06-23 17:15           ` Rafael J. Wysocki
2023-06-30 10:37             ` Quan, Evan
2023-06-23 16:38   ` Rafael J. Wysocki
2023-06-21  5:45 ` [PATCH V4 2/8] cfg80211: expose nl80211_chan_width_to_mhz for wide sharing Evan Quan
2023-06-21  5:45 ` [PATCH V4 3/8] wifi: mac80211: Add support for ACPI WBRF Evan Quan
2023-06-21 10:22   ` Johannes Berg
2023-06-21 14:12     ` Limonciello, Mario
2023-06-21 14:25       ` Johannes Berg
2023-06-21  5:45 ` [PATCH V4 4/8] drm/amd/pm: update driver_if and ppsmc headers for coming wbrf feature Evan Quan
2023-06-21  5:46 ` [PATCH V4 5/8] drm/amd/pm: setup the framework to support Wifi RFI mitigation feature Evan Quan
2023-06-21  5:46 ` [PATCH V4 6/8] drm/amd/pm: add flood detection for wbrf events Evan Quan
2023-06-21  5:46 ` [PATCH V4 7/8] drm/amd/pm: enable Wifi RFI mitigation feature support for SMU13.0.0 Evan Quan
2023-06-21  5:46 ` [PATCH V4 8/8] drm/amd/pm: enable Wifi RFI mitigation feature support for SMU13.0.7 Evan Quan

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=c518da2a-5ba5-af7e-e26d-1973db7b4c9e@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrealmeid@igalia.com \
    --cc=arnd@arndb.de \
    --cc=bellosilicio@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=evan.quan@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=jim.cromie@gmail.com \
    --cc=jingyuwang_vip@163.com \
    --cc=johannes@sipsolutions.net \
    --cc=jsg@jsg.id.au \
    --cc=kuba@kernel.org \
    --cc=lenb@kernel.org \
    --cc=lijo.lazar@amd.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mdaenzer@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafael@kernel.org \
    --cc=trix@redhat.com \
    --cc=tzimmermann@suse.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: 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).