From: Rodolfo Giometti <giometti@enneenne.com>
To: dylan.laduranty@mesotic.com
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] pps: clients: pps-gpio: fix echo pin configuration
Date: Mon, 2 Mar 2026 09:11:13 +0100 [thread overview]
Message-ID: <f32bc1db-4ecd-4175-adb2-10f70d0f3c0e@enneenne.com> (raw)
In-Reply-To: <20260227-drivers-pps-clients-fix-echo-pin-setup-v1-1-a5a5f52d7d96@mesotic.com>
On 2/27/26 16:45, Dylan Laduranty via B4 Relay wrote:
> From: Dylan Laduranty <dylan.laduranty@mesotic.com>
>
> This patch adds PPS_ECHOASSERT and PPS_ECHOCLEAR to pps_default_params
> when needed.
>
> The pps_gpio_echo() function will check if these flags are set inside
> params.mode to update the echo pin state.
>
> However, these flags need to be set during probe sequence otherwise
> pps_gpio_echo() function will never update the pin's state.
>
> Signed-off-by: Dylan Laduranty <dylan.laduranty@mesotic.com>
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
> ---
> drivers/pps/clients/pps-gpio.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps-gpio.c
> index 935da68610c701e6d9de53c667237f77438d7107..83ca24118eccfdb9eebe272023ef4980c9d54cf2 100644
> --- a/drivers/pps/clients/pps-gpio.c
> +++ b/drivers/pps/clients/pps-gpio.c
> @@ -200,8 +200,13 @@ static int pps_gpio_probe(struct platform_device *pdev)
>
> /* register PPS source */
> pps_default_params = PPS_CAPTUREASSERT | PPS_OFFSETASSERT;
> - if (data->capture_clear)
> + if (data->echo_pin)
> + pps_default_params |= PPS_ECHOASSERT;
> + if (data->capture_clear) {
> pps_default_params |= PPS_CAPTURECLEAR | PPS_OFFSETCLEAR;
> + if (data->echo_pin)
> + pps_default_params |= PPS_ECHOCLEAR;
> + }
> data->pps = pps_register_source(&data->info, pps_default_params);
> if (IS_ERR(data->pps)) {
> dev_err(dev, "failed to register IRQ %d as PPS source\n",
>
> ---
> base-commit: 3fa5e5702a82d259897bd7e209469bc06368bf31
> change-id: 20260227-drivers-pps-clients-fix-echo-pin-setup-fe52d3b8596f
>
> Best regards,
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming
prev parent reply other threads:[~2026-03-02 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:45 Dylan Laduranty via B4 Relay
2026-03-02 8:11 ` Rodolfo Giometti [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=f32bc1db-4ecd-4175-adb2-10f70d0f3c0e@enneenne.com \
--to=giometti@enneenne.com \
--cc=akpm@linux-foundation.org \
--cc=dylan.laduranty@mesotic.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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®