mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bastien Curutchet <bastien.curutchet@bootlin.com>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	herve.codina@bootlin.com, christophercordahi@nanometrics.ca
Subject: Re: [PATCH 1/1] pps: clients: gpio: Bypass edge's direction check when not needed
Date: Thu, 11 Apr 2024 14:44:44 +0200	[thread overview]
Message-ID: <28c5456d-535c-4ed9-b13a-fab7f50412be@bootlin.com> (raw)
In-Reply-To: <c1e93cfe-371c-4855-9a13-b4b453bb9e88@enneenne.com>

Hi Rodolfo

>>> diff --git a/drivers/pps/clients/pps-gpio.c 
>>> b/drivers/pps/clients/pps-gpio.c
>>> index 2f4b11b4dfcd..f05fb15ed7f4 100644
>>> --- a/drivers/pps/clients/pps-gpio.c
>>> +++ b/drivers/pps/clients/pps-gpio.c
>>> @@ -52,7 +52,9 @@ static irqreturn_t pps_gpio_irq_handler(int irq, 
>>> void *data)
>>>
>>>          info = data;
>>>
>>> -       rising_edge = gpiod_get_value(info->gpio_pin);
>>> +       rising_edge = info->capture_clear ? \
>>> +                       gpiod_get_value(info->gpio_pin) : \
>>> +                       !info->assert_falling_edge;
>>>          if ((rising_edge && !info->assert_falling_edge) ||
>>>                          (!rising_edge && info->assert_falling_edge))
>>>                  pps_event(info->pps, &ts, PPS_CAPTUREASSERT, data);
>>>
>>> Please, review and test it before resubmitting. :)
>>>
>>
>> I'll try this and send a V2 after my tests, thank you.
> 
> OK, thanks.
> 
> However we should think very well about this modification since it could 
> be the case where we have a device sending both assert and clear events 
> but we wish to catch just the asserts... in this case we will get 
> doubled asserts!
> 

My understanding is that clear events are to be captured only when this
capture_clear boolean is set. If it is not set, the PPS_CAPTURECLEAR
flag is not added to pps_source_info->mode and get_irqf_trigger_flags()
will return only one edge flag (rising or falling depending on
assert-falling-edge DT property).

By the way, I see that the capture_clear is never set since the legacy
platform data support has been dropped (commit ee89646619ba).


Best regards,
Bastien


  reply	other threads:[~2024-04-11 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 11:35 Bastien Curutchet
2024-04-10 14:23 ` Rodolfo Giometti
2024-04-10 14:46   ` Bastien Curutchet
2024-04-10 15:24     ` Rodolfo Giometti
2024-04-10 16:05       ` Bastien Curutchet
2024-04-11  7:20         ` Rodolfo Giometti
2024-04-11 12:44           ` Bastien Curutchet [this message]
2024-04-12  6:44             ` Rodolfo Giometti
2024-04-12 12:20               ` Bastien Curutchet
2024-04-25  6:11                 ` Bastien Curutchet
2024-04-25 11:46                   ` Rodolfo Giometti

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=28c5456d-535c-4ed9-b13a-fab7f50412be@bootlin.com \
    --to=bastien.curutchet@bootlin.com \
    --cc=christophercordahi@nanometrics.ca \
    --cc=giometti@enneenne.com \
    --cc=herve.codina@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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®