Linux Media Controller development
 help / color / mirror / Atom feed
From: Alan Cox <alan@llwyncelyn.cymru>
To: linux-media@vger.kernel.org
Subject: [2/7/] staging: atomisp: Do not call dev_warn with a NULL device
Date: Sun, 28 May 2017 18:35:35 +0100	[thread overview]
Message-ID: <20170528183535.21d49466@alans-desktop> (raw)

>On Sun, May 28, 2017 at 3:31 PM, Hans de Goede <hdegoede@redhat.com>
wrote:
>> Do not call dev_warn with a NULL device, this silence the following 2
>> warnings:
>>
>> [   14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO
>> [   14.392257] (NULL device *): Failed to find gmin variable gmin_V1P8GPIO
>>
>> We could switch to using pr_warn for dev == NULL instead, but as comments
>> in the source indicate, the check for these 2 special gmin variables with
>> a NULL device is a workaround for 2 specific evaluation boards, so
>> completely silencing the missing warning for these actually is a good
>> thing.
>
> Perhaps removing all code related explicitly to Gmin is a right thing to do.

That would make the driver somewhat useless because the Android derived
platforms I have seen that you can re-install Linux on that use this as
far as I am aware use the GMIN EFI variables.

Only the Windows platforms do it differently, and they appear to embed
the entire configuration in a machine specific driver for each platform
(at least the supposedly relevant ACPI in my T100TA appears to be copied
from an Intel reference board and bears no relation to the actual
hardware!)

Easy enough to check what a given Android x86 tablet does - plug it into a
powered OTG hub, add a live USB stick and a keyboard, hit the Fn key for
BIOS entry as it boots and boot off USB. You can then check lsacpi and
the EFI variables.

Alan

                 reply	other threads:[~2017-05-28 17:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170528183535.21d49466@alans-desktop \
    --to=alan@llwyncelyn.cymru \
    --cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox