All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Stuart Henderson <stuarth@opensource.cirrus.com>
Cc: Luke Jones <luke@ljones.dev>, <linux-kernel@vger.kernel.org>,
	<tiwai@suse.com>, <sbinding@opensource.cirrus.com>,
	<perex@perex.cz>, <tangmeng@uniontech.com>,
	<andy.chi@canonical.com>, <p.jungkamp@gmx.net>,
	<kasper93@gmail.com>, <yangyuchi66@gmail.com>, <armas@codux.tech>,
	<ealex95@gmail.com>, <james.schulman@cirrus.com>,
	<david.rhodes@cirrus.com>, <tanureal@opensource.cirrus.com>,
	<rf@opensource.cirrus.com>, <patches@opensource.cirrus.com>,
	<alsa-devel@alsa-project.org>
Subject: Re: CSC3551 and devices missing related _DSD bits
Date: Wed, 24 May 2023 20:08:21 +0200	[thread overview]
Message-ID: <87o7m9d2lm.wl-tiwai@suse.de> (raw)
In-Reply-To: <b4c202b2-ab29-e2aa-b141-0c967b2c1645@opensource.cirrus.com>

On Wed, 24 May 2023 18:36:04 +0200,
Stuart Henderson wrote:
> 
> 
> > The problem is that this can really easily blow up your machine if
> > some incorrect bit is applied.  And more easily applicable, more
> > chance to break by novice users, simply by believing what a chat bot
> > speaks :)
> > That's the very reason why this kind of change should be via ACPI
> > table officially set up by the vendor.  That said, the question is
> > only who and how can be responsible for this kind of change.  It's
> > no technical issue, per se.
> > 
> > If BIOS can't be updated, at least, the configuration change has to be
> > confirmed by ASUS people.  If ASUS still ignores the inquires and
> > requests, we may put the quirk but with a bit fat warning (and maybe
> > complaints to ASUS) to be shown in the log as a very last resort.
> > 
> > Let's see what happens.
> 
> Thanks Takashi.
> 
> Just a note to say we're not ignoring this and are investigating the
> best way to support released laptops with ACPI incompatible with
> Linux.  We're hoping this is going to be less of an issue going
> forward.  Please bear with us while we look into this.

Good to hear that you're working on it!
Sure, it's no urgent issue and better wait for a proper solution.


thanks,

Takashi

  reply	other threads:[~2023-05-24 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 22:26 CSC3551 and devices missing related _DSD bits Luke Jones
2023-05-18 22:26 ` Luke Jones
2023-05-20  8:14 ` Takashi Iwai
2023-05-21 21:35   ` Luke Jones
2023-05-24 16:36   ` Stuart Henderson
2023-05-24 18:08     ` Takashi Iwai [this message]
2023-05-24 21:30     ` Luke Jones
2023-05-28  0:02       ` Armas Spann
2023-06-01  9:42         ` Stuart Henderson

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=87o7m9d2lm.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=andy.chi@canonical.com \
    --cc=armas@codux.tech \
    --cc=david.rhodes@cirrus.com \
    --cc=ealex95@gmail.com \
    --cc=james.schulman@cirrus.com \
    --cc=kasper93@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=p.jungkamp@gmx.net \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=sbinding@opensource.cirrus.com \
    --cc=stuarth@opensource.cirrus.com \
    --cc=tangmeng@uniontech.com \
    --cc=tanureal@opensource.cirrus.com \
    --cc=tiwai@suse.com \
    --cc=yangyuchi66@gmail.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 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.