All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Mario.Limonciello@dell.com
Cc: alex.hung@canonical.com, rjw@rjwysocki.net, lenb@kernel.org,
	gregkh@linuxfoundation.org, davem@davemloft.net,
	mika.westerberg@linux.intel.com,
	andriy.shevchenko@linux.intel.com, f.fainelli@gmail.com,
	dmitry.torokhov@gmail.com, kishon@ti.com,
	karniksayli1995@gmail.com, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI / osi: add DMI quirk for Dell systems
Date: Mon, 5 Feb 2018 22:55:17 +0100	[thread overview]
Message-ID: <20180205225517.4c565351@endymion> (raw)
In-Reply-To: <ddcf31de6764453e98fb8647514ad8fa@ausx13mpc120.AMER.DELL.COM>

On Mon, 5 Feb 2018 17:24:43 +0000, Mario.Limonciello@dell.com wrote:
> > > +static int __init dmi_oem_osi_add(const struct dmi_system_id *d)
> > > +{
> > > +	struct acpi_osi_entry *osi;
> > > +	const char *str = d->driver_data;
> > > +	int i;
> > > +
> > > +	for (i = 0; i < OSI_STRING_ENTRIES_MAX; i++) {
> > > +		osi = &osi_setup_entries[i];
> > > +		if (!strcmp(osi->string, str)) {  
> > 
> > This can only happen if the user passes acpi_osi=Linux-Dell-Video or
> > acpi_osi=!Linux-Dell-Video on the boot command line, right?
> >   
> > > +			osi->enable = true;  
> > 
> > Does this not prevent the user from explicitly disabling it with
> > acpi_osi=!Linux-Dell-Video ?
> >   
> > > +			continue;  
> > 
> > Are you not done at this point? I think you want to break, not
> > continue, else you may add a duplicate Linux-Dell-Video entry below.  
> 
> You might have two different entries that apply to the same system in the future.
> 
> At least the way that Dell is intending to use this is that "Linux-Dell-Video" would
> only apply to ASL related to video configuration.
> 
> If for example there is later an issue with audio on a different platform that also
> needed "Linux-Dell-Video", the ASL to do the audio configuration would be activated
> by "Linux-Dell-Audio".

I understand what you say, but can't see how this relates to my
concerns above.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2018-02-05 21:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  8:40 [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches Alex Hung
2018-01-31  8:40 ` [PATCH 2/2] ACPI / osi: add DMI quirk for Dell systems Alex Hung
2018-02-05 13:14   ` Jean Delvare
2018-02-05 14:15     ` Andy Shevchenko
2018-02-05 17:36       ` Mario.Limonciello
2018-02-05 22:45         ` Dmitry Torokhov
2018-02-06  0:45           ` Mario.Limonciello
2018-02-06 13:45             ` Andy Shevchenko
2018-02-06 16:24               ` Mario.Limonciello
2018-02-07 20:38                 ` Alex Hung
2018-02-07 20:49                   ` Mario.Limonciello
2018-02-11  9:29               ` Rafael J. Wysocki
2018-02-11 13:45                 ` Lukas Wunner
2018-02-12  9:49                   ` Rafael J. Wysocki
2018-02-12 20:29                     ` Mario.Limonciello
2018-02-12 22:57                       ` Rafael J. Wysocki
2018-02-12 23:14                         ` Mario.Limonciello
2018-02-13  5:25                           ` Alex Hung
2018-02-13  7:32                           ` Mika Westerberg
2018-02-14  9:06                             ` Rafael J. Wysocki
2018-02-14  9:50                               ` Mika Westerberg
2018-02-13  9:18                           ` Rafael J. Wysocki
2018-02-13  9:55                             ` Lukas Wunner
2018-02-14  9:10                               ` Rafael J. Wysocki
2018-02-14 18:47                             ` Mario.Limonciello
2018-02-15  9:44                               ` Rafael J. Wysocki
2018-02-05 17:24     ` Mario.Limonciello
2018-02-05 21:55       ` Jean Delvare [this message]
2018-02-07 20:05     ` Alex Hung
2018-02-05 10:26 ` [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches Jean Delvare
2018-02-07  5:25   ` Alex Hung

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=20180205225517.4c565351@endymion \
    --to=jdelvare@suse.de \
    --cc=Mario.Limonciello@dell.com \
    --cc=alex.hung@canonical.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=karniksayli1995@gmail.com \
    --cc=kishon@ti.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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.