From: Ingo Molnar <mingo@kernel.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: "Mario Limonciello" <superm1@kernel.org>,
"Borislav Petkov" <bp@alien8.de>,
"Jean Delvare" <jdelvare@suse.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:I2C/SMBUS CONTROLLER DRIVERS FOR PC"
<linux-i2c@vger.kernel.org>,
"open list:AMD PMC DRIVER" <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v4 4/5] platform/x86/amd: pmc: use FCH_PM_BASE definition
Date: Wed, 16 Apr 2025 09:58:20 +0200 [thread overview]
Message-ID: <Z_9jHCpbTciJ8d2_@gmail.com> (raw)
In-Reply-To: <20250415151326.GA624550@yaz-khff2.amd.com>
* Yazen Ghannam <yazen.ghannam@amd.com> wrote:
> On Mon, Apr 14, 2025 at 07:26:57PM -0500, Mario Limonciello wrote:
> > From: Mario Limonciello <mario.limonciello@amd.com>
> >
> > The s2idle mmio quirk uses a scratch register in the FCH.
> > Adjust the code to clarify that.
> >
> > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> > ---
> > v4:
> > * Use fch.h instead
> > ---
> > arch/x86/include/asm/amd/fch.h | 1 +
> > drivers/platform/x86/amd/pmc/pmc-quirks.c | 3 ++-
> > 2 files changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/x86/include/asm/amd/fch.h b/arch/x86/include/asm/amd/fch.h
> > index a5fd91ff92df3..9b32e8a03193e 100644
> > --- a/arch/x86/include/asm/amd/fch.h
> > +++ b/arch/x86/include/asm/amd/fch.h
> > @@ -8,5 +8,6 @@
> > /* register offsets from PM base */
> > #define FCH_PM_DECODEEN 0x00
> > #define FCH_PM_DECODEEN_SMBUS0SEL GENMASK(20, 19)
> > +#define FCH_PM_SCRATCH 0x80
> >
> > #endif
> > diff --git a/drivers/platform/x86/amd/pmc/pmc-quirks.c b/drivers/platform/x86/amd/pmc/pmc-quirks.c
> > index b4f49720c87f6..3c680d2029f62 100644
> > --- a/drivers/platform/x86/amd/pmc/pmc-quirks.c
> > +++ b/drivers/platform/x86/amd/pmc/pmc-quirks.c
> > @@ -8,6 +8,7 @@
> > * Author: Mario Limonciello <mario.limonciello@amd.com>
> > */
> >
> > +#include <asm/amd/fch.h>
>
> Arch headers should go after linux headers, I think.
That's true, but it's a mostly stylistic requirement these days.
> So that arch stuff can override generic stuff.
Arch headers that override generic stuff are very much supposed to be
able to build stand-alone and in pretty much any order with other
headers, with very few exceptions. Ordering dependencies are very much
frowned upon, because if they don't trigger build failures they can
result in subtle breakages.
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-16 7:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 0:26 [PATCH v4 0/5] AMD Zen debugging documentation Mario Limonciello
2025-04-15 0:26 ` [PATCH v4 1/5] Documentation: Add AMD Zen debugging document Mario Limonciello
2025-04-15 0:26 ` [PATCH v4 2/5] i2c: piix4: Depends on X86 Mario Limonciello
2025-04-17 22:16 ` Andi Shyti
2025-04-17 22:21 ` Mario Limonciello
2025-04-15 0:26 ` [PATCH v4 3/5] i2c: piix4: Move SB800_PIIX4_FCH_PM_ADDR definition to amd/fch.h Mario Limonciello
2025-04-15 0:26 ` [PATCH v4 4/5] platform/x86/amd: pmc: use FCH_PM_BASE definition Mario Limonciello
2025-04-15 15:13 ` Yazen Ghannam
2025-04-15 15:45 ` Mario Limonciello
2025-04-16 7:58 ` Ingo Molnar [this message]
2025-04-16 13:44 ` Yazen Ghannam
2025-04-15 0:26 ` [PATCH v4 5/5] x86/CPU/AMD: Print the reason for the last reset Mario Limonciello
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=Z_9jHCpbTciJ8d2_@gmail.com \
--to=mingo@kernel.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andi.shyti@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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