public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Javier Carrasco <javier.carrasco@wolfvision.net>
Cc: Takashi Iwai <tiwai@suse.de>,
	Javier Carrasco <javier.carrasco.cruz@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] Missing bcm5974 touchpad on Macbooks
Date: Mon, 04 Mar 2024 13:45:30 +0100	[thread overview]
Message-ID: <874jdm17yt.wl-tiwai@suse.de> (raw)
In-Reply-To: <6ef6c5bf-e6e5-4711-81c6-6ae41de2e61e@wolfvision.net>

On Mon, 04 Mar 2024 12:26:48 +0100,
Javier Carrasco wrote:
> 
> On 04.03.24 09:35, Takashi Iwai wrote:
> > Hi,
> > 
> > we've received a few regression reports for openSUSE Leap about the
> > missing touchpad on Macbooks.  After debugging, this turned out to be
> > the backport of the commit 2b9c3eb32a699acdd4784d6b93743271b4970899
> >     Input: bcm5974 - check endpoint type before starting traffic
> > 
> > And, the same regression was confirmed on the upstream 6.8-rc6
> > kernel.
> > 
> > Reverting the commit above fixes the problem, the touchpad reappears.
> > 
> > The detailed hardware info is found at:
> >   https://bugzilla.suse.com/show_bug.cgi?id=1220030
> > 
> > Feel free to join the bugzilla above, or let me know if you need
> > something for debugging, then I'll delegate on the bugzilla.
> > 
> > 
> > thanks,
> > 
> > Takashi
> > 
> 
> Hi Takashi,
> 
> The commit adds a check to ensure that the endpoint type is interrupt.
> 
> According to that report, the issue arose with a MacBook Pro 5.1 (no
> button, only trackpad endpoint), so the check on the tp_ep address
> (0x81) returns false. I assume that you see an error message
> ("Unexpected non-int endpoint) and  the probe function fails returning
> -ENODEV.

Right, there is the message.

> Do you see any warning in the logs when you revert the commit? It was
> added to prevent using wrong endpoint types, which will display the
> following warning: "BOGUS urb xfer, pipe "some_number" != type
> "another_number""

The revert was tested on the downstream kernel, but it has also the
check of bogus pipe, and there was no such warning, as far as I see
the report.

> I am just wondering if for some reason the check on interrupt type is
> wrong here.

I'll ask reporters to give the lsusb -v output so that we can take a
deeper look.  Also, I'm building a test kernel based on 6.8-rc7 with
the revert, and ask reporters to test with it, just to be sure.


thanks,

Takashi

  reply	other threads:[~2024-03-04 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  8:35 [REGRESSION] Missing bcm5974 touchpad on Macbooks Takashi Iwai
2024-03-04 11:26 ` Javier Carrasco
2024-03-04 12:45   ` Takashi Iwai [this message]
2024-03-04 14:04     ` Javier Carrasco
2024-03-04 20:21     ` Javier Carrasco
2024-03-05  1:15       ` Dmitry Torokhov
2024-03-04 12:18 ` Linux regression tracking #adding (Thorsten Leemhuis)

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=874jdm17yt.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=javier.carrasco@wolfvision.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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