Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Csókás, Bence" <csokas.bence@prolan.hu>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
	Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH 6.6 0/3] Fix PPS channel routing
Date: Mon, 23 Dec 2024 13:38:21 +0100	[thread overview]
Message-ID: <2024122313-unsworn-think-a029@gregkh> (raw)
In-Reply-To: <20241217175042.284122-1-csokas.bence@prolan.hu>

On Tue, Dec 17, 2024 at 06:50:39PM +0100, Csókás, Bence wrote:
> On certain i.MX8 series parts [1], the PPS channel 0
> is routed internally to eDMA, and the external PPS
> pin is available on channel 1. In addition, on
> certain boards, the PPS may be wired on the PCB to
> an EVENTOUTn pin other than 0. On these systems
> it is necessary that the PPS channel be able
> to be configured from the Device Tree.
> 
> [1] https://lore.kernel.org/all/ZrPYOWA3FESx197L@lizhi-Precision-Tower-5810/
> 
> Now that these patches are applied to 6.12.y,
> it is time to include it in the upcoming 6.6.67.
> This series is picked onto 6.6.66.

All now queued up, thanks.

greg k-h

  parent reply	other threads:[~2024-12-23 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 17:50 [PATCH 6.6 0/3] Fix PPS channel routing Csókás, Bence
2024-12-17 17:50 ` [PATCH 6.6 1/3] dt-bindings: net: fec: add pps channel property Csókás, Bence
2024-12-17 17:50 ` [PATCH 6.6 2/3] net: fec: refactor PPS channel configuration Csókás, Bence
2024-12-17 17:50 ` [PATCH 6.6 3/3] net: fec: make PPS channel configurable Csókás, Bence
2024-12-23 12:38 ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-25  9:16 [PATCH 6.6 0/3] Fix PPS channel routing Csókás, Bence
2024-12-02  9:52 ` Greg Kroah-Hartman

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=2024122313-unsworn-think-a029@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=csokas.bence@prolan.hu \
    --cc=francesco.dolcini@toradex.com \
    --cc=sashal@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