mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Steven Kendall <skend@chromium.org>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ALSA: hda/cs8409: Fix for Dell Cirrus audio jack detect
Date: Sun, 04 Oct 2026 20:49:38 +0200	[thread overview]
Message-ID: <87y0cdgv25.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAB1bpFDsVLApsW6nYOyLQYx83o9NpDrpKwoK_4KdoCV=GeWv=g@mail.gmail.com>

On Mon, 21 Sep 2026 23:00:28 +0200,
Steven Kendall wrote:
> 
> > > The code change looks acceptable, but the patch description gives too
> > > little information.
> > >
> > > And, should we apply it unconditionally all models with this code?
> 
> I've submitted a v4 that only applies the delay to this specific model
> I've observed the issue on.
> 
> > ... also please check sashiko's review
> >   https://sashiko.dev/#/patchset/20260915-fix-headphone-plug-cirrus-dell-v3-1-6dc555b00f61%40chromium.org
> >
> > They aren't always correct but often give good hints.
> 
> I looked over the AI feedback and I'm not sure what the best action to
> take is. It seemed like it was kind of a broad criticism of delayed
> work in general, which already exists in the same file. Now that the
> patch only applies to one machine and I've tested on that one machine
> I'm more confident in the fix but I'm open to doing additional
> testing. Or if there's some tooling I should be using to make the
> abstract "timing issues" more observable I would love to learn more
> about that too.

The review to v4 showed about only the usage of cancel_work_*(),
and the suggestion sounds reasonable.  Those new cancel_work_*()
should be put before disabling i2c.

BTW, at the remove patch, maybe better to use disable_work*() variant
than cancel_work*().  The existing code is old and they were before
disable_*() was introduced (so they should be replaced, too).


thanks,

Takashi

      reply	other threads:[~2026-10-04 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  2:11 Steven 'Steve' Kendall
2026-09-15 10:16 ` Takashi Iwai
2026-09-16  7:33   ` Takashi Iwai
2026-09-21 21:00     ` Steven Kendall
2026-10-04 18:49       ` Takashi Iwai [this message]

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=87y0cdgv25.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=skend@chromium.org \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®