All of lore.kernel.org
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: "S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <markgross@kernel.org>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: amd_pmc module not autoloading on Thinkpad X13 Gen 2a
Date: Sun, 22 Jan 2023 15:34:19 +0100	[thread overview]
Message-ID: <Y81Ja5Y/tgPXk5FA@eldamar.lan> (raw)
In-Reply-To: <MN0PR12MB6101ACCD8A5003CBB4BEF58DE2CB9@MN0PR12MB6101.namprd12.prod.outlook.com>

Hi Mario,

Thanks for your followup.

On Sun, Jan 22, 2023 at 02:08:00PM +0000, Limonciello, Mario wrote:
> [AMD Official Use Only - General]
> 
> Salvatore,
> 
> The issue has been debugged to be an s3 issue not an s0ix issue.
> This patch series has been submitted for it.
> 
> https://lore.kernel.org/linux-gpio/20230121134812.16637-1-mario.limonciello@amd.com/T/#t

Yes I'm aware of that (and planning for Debian to queue them up after
acceptance). Sorry I was unclear maybe. The other part of the question
is, would not autoloading amd_pmc be an issue, and what information
would be helpful to gather to tackle this?

Regards,
Salvatore

  parent reply	other threads:[~2023-01-22 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 10:18 amd_pcm module not autoloading on Thinkpad X13 Gen 2a Salvatore Bonaccorso
     [not found] ` <MN0PR12MB6101ACCD8A5003CBB4BEF58DE2CB9@MN0PR12MB6101.namprd12.prod.outlook.com>
2023-01-22 14:34   ` Salvatore Bonaccorso [this message]
     [not found]     ` <MN0PR12MB61019EC33FA0F91C0E79967BE2CB9@MN0PR12MB6101.namprd12.prod.outlook.com>
2023-01-24  9:27       ` amd_pmc " Salvatore Bonaccorso

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=Y81Ja5Y/tgPXk5FA@eldamar.lan \
    --to=carnil@debian.org \
    --cc=Mario.Limonciello@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@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 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.