mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Carrasco <javier.carrasco@wolfvision.net>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Abdel Alkuor <abdelalkuor@geotab.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] usb: typec: tipd: fix event checking in interrupt service routines
Date: Tue, 2 Apr 2024 19:39:56 +0200	[thread overview]
Message-ID: <82e0f16a-8f25-4e69-97bb-ee3c78f2b183@wolfvision.net> (raw)
In-Reply-To: <ZgvcJPTJS7d4aYgr@kuha.fi.intel.com>

On 4/2/24 12:21, Heikki Krogerus wrote:
> On Thu, Mar 28, 2024 at 05:55:50PM +0100, Javier Carrasco wrote:
>> The ISRs of the tps25750 and tps6598x do not handle generated events
>> properly under all circumstances.
>>
>> The tps6598x ISR does not read all bits of the INT_EVENTX registers,
>> leaving events signaled with bits above 64 unattended. Moreover, these
>> events are not cleared, leaving the interrupt enabled.
>>
>> The tps25750 reads all bits of the INT_EVENT1 register, but the event
>> checking is not right because the same event is checked in two different
>> regions of the same register by means of an OR operation.
>>
>> This series aims to fix both issues by reading all bits of the
>> INT_EVENTX registers, and limiting the event checking to the region
>> where the supported events are defined (currently they are limited to
>> the first 64 bits of the registers, as the are defined as BIT_ULL()).
>>
>> If the need for events above the first 64 bits of the INT_EVENTX
>> registers arises, a different mechanism might be required. But for the
>> current needs, all definitions can be left as they are.
>>
>> Note: resend to add the Cc tag for 'stable' (fixes in the series).
> 
> So this should be v3 (or v2?). Next time please follow the guide
> when submitting patches:
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#the-canonical-patch-format
> 
> thanks,
> 
The first resend only added 'stable' to Cc (which was wrong) with no
modifications at all, and the second resend (this one) actually modified
the commit description to include 'stable', which should have turned it
into a v2.

I will tag the next version as v3 to account for this, thanks for the
feedback.

Best regards,
Javier Carrasco

  reply	other threads:[~2024-04-02 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 16:55 Javier Carrasco
2024-03-28 16:55 ` [PATCH RESEND 1/2] usb: typec: tipd: fix event checking for tps25750 Javier Carrasco
2024-04-02 10:21   ` Heikki Krogerus
2024-03-28 16:55 ` [PATCH RESEND 2/2] usb: typec: tipd: fix event checking for tps6598x Javier Carrasco
2024-04-02 10:29   ` Heikki Krogerus
2024-04-03  8:55     ` Javier Carrasco
2024-04-05  6:49       ` Heikki Krogerus
2024-04-11 20:13         ` Javier Carrasco
2024-04-02 10:21 ` [PATCH RESEND 0/2] usb: typec: tipd: fix event checking in interrupt service routines Heikki Krogerus
2024-04-02 17:39   ` Javier Carrasco [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-28 16:25 Javier Carrasco
2024-03-28 16:44 ` Greg Kroah-Hartman
2024-03-28 16:47   ` Javier Carrasco

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=82e0f16a-8f25-4e69-97bb-ee3c78f2b183@wolfvision.net \
    --to=javier.carrasco@wolfvision.net \
    --cc=abdelalkuor@geotab.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@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

all inboxes | Powered by JetHome®