linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	linux-watchdog@vger.kernel.org,
	Srikanth Krishnakar <skrishnakar@gmail.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Gerd Haeussler <gerd.haeussler.ext@siemens.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Mark Gross <mgross@linux.intel.com>,
	Hans de Goede <hdegoede@redhat.com>, Pavel Machek <pavel@ucw.cz>,
	Enrico Weigelt <lkml@metux.net>,
	Michael Haener <michael.haener@siemens.com>
Subject: Re: [PATCH v4 4/4] platform/x86: pmc_atom: improve critclk_systems matching for Siemens PCs
Date: Fri, 26 Nov 2021 16:25:32 +0100	[thread overview]
Message-ID: <20211126162532.1cd42766@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAHp75Vf6x4-AYPPEMf7qXTi-RF92mdUn6rhghBpJ5avQAjYRzA@mail.gmail.com>

Am Fri, 26 Nov 2021 16:51:00 +0200
schrieb Andy Shevchenko <andy.shevchenko@gmail.com>:

> On Fri, Nov 26, 2021 at 4:10 PM Henning Schild
> <henning.schild@siemens.com> wrote:
> >
> > Siemens industrial PCs unfortunately can not always be properly
> > identified the way we used to. An earlier commit introduced code
> > that allows proper identification without looking at DMI strings
> > that could differ based on product branding.
> > Switch over to that proper way and revert commits that used to
> > collect the machines based on unstable strings.  
> 
> Usually we start a series with fixes, but I guess it's fine here since
> this can be taken separately, right?
> 
> ...

It can not be taken because it needs p1 to work. And p1 is mainly here
for p2 and p3 really. Splitting the patches up into

p1.1
p4
p1.2
p2
p3

would be possible but a lot of work for just that ordering topic i
guess.

> > +#include <linux/platform_data/x86/simatic-ipc.h>  
> 
> Seems not.  Question is then, what Fixes tags would  mean in this
> case?
> 

Which of the several tags confuses you? Maybe i just need to drop a few.

the original problem is
Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
which introduced the need for several quirks
Fixes: e8796c6c69d1 ("platform/x86: pmc_atom: Add Siemens CONNECT...")
Fixes: f110d252ae79 ("platform/x86: pmc_atom: Add Siemens SIMATIC...")
Fixes: ad0d315b4d4e ("platform/x86: pmc_atom: Add Siemens SIMATIC...")
These quirks use unstable dmi information. Unstable because the
DMI_PRODUCT_VERSION can be branded. Yes weird ... we do not allow new
ACPI entries but do allow custom dmi ...
p1 introduces the use of stable dmi and p4 brings that into the quirk
table ... fixing all the quirks based on customizable
DMI_PRODUCT_VERSION

Henning

  reply	other threads:[~2021-11-26 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 14:10 [PATCH v4 0/4] add device drivers for Siemens Industrial PCs Henning Schild
2021-11-26 14:10 ` [PATCH v4 1/4] platform/x86: simatic-ipc: add main driver for Siemens devices Henning Schild
2021-11-26 14:10 ` [PATCH v4 2/4] leds: simatic-ipc-leds: add new driver for Siemens Industial PCs Henning Schild
2021-11-26 15:02   ` Andy Shevchenko
2021-11-26 17:48     ` Henning Schild
2021-11-26 18:12     ` Henning Schild
2021-11-30 15:15       ` Andy Shevchenko
2021-12-03 19:35         ` Henning Schild
2021-11-26 14:10 ` [PATCH v4 3/4] watchdog: simatic-ipc-wdt: add new driver for Siemens Industrial PCs Henning Schild
2021-11-26 14:10 ` [PATCH v4 4/4] platform/x86: pmc_atom: improve critclk_systems matching for Siemens PCs Henning Schild
2021-11-26 14:51   ` Andy Shevchenko
2021-11-26 15:25     ` Henning Schild [this message]
2021-11-26 15:34 ` [PATCH v4 0/4] add device drivers for Siemens Industrial PCs Henning Schild
2021-11-26 16:02   ` Guenter Roeck
2021-11-26 17:28     ` Henning Schild
2021-12-03 19:44 ` Henning Schild

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=20211126162532.1cd42766@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gerd.haeussler.ext@siemens.com \
    --cc=hdegoede@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkml@metux.net \
    --cc=mgross@linux.intel.com \
    --cc=michael.haener@siemens.com \
    --cc=pavel@ucw.cz \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=skrishnakar@gmail.com \
    --cc=wim@linux-watchdog.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).