devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kane Jiang <jian.jiang@nxp.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Steve Longerbeam <slongerbeam@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org
Cc: Kane Jiang <jian.jiang@nxp.com>
Subject: [PATCH 0/3] About i.MX GPT input capture patches
Date: Thu, 10 Feb 2022 16:43:32 +0800	[thread overview]
Message-ID: <20220210084335.1979778-1-jian.jiang@nxp.com> (raw)

The backgroud of this upstream is: I used to enable i.MX GPT input
capture function for i.MX8MM. And I found patches following from Steve:
https://lore.kernel.org/linux-arm-kernel/20191016010544.14561-2-slongerbeam@gmail.com/
https://lore.kernel.org/linux-arm-kernel/20191016010544.14561-3-slongerbeam@gmail.com/
After applied the patches and do some modification, GPT input capture
function was enabled in i.MX8MM. When checked in latest BSP, seems the
two patches are not included. I am not sure about the upstream status
initiated by Steve. So as a latercomer, I am doing this upsteam again.

Kane Jiang (2):
  Change to cyclecounter for GPT input capture. Add support for i.MX8MM.
  Add i.MX8MM GPT input capture example.

Steve Longerbeam (1):
  This patch adds support for the input capture function in the i.MX
    GPT. Output compare and input capture functions are mixed in the
    same register block, so we need to modify the irq ack/enable/
    disable primitives to not stomp on the other function.

 .../devicetree/bindings/timer/fsl,imxgpt.yaml |  48 ++
 drivers/clocksource/timer-imx-gpt.c           | 482 ++++++++++++++++--
 include/linux/mxc_icap.h                      |  16 +
 3 files changed, 496 insertions(+), 50 deletions(-)
 create mode 100644 include/linux/mxc_icap.h

-- 
2.25.1


             reply	other threads:[~2022-02-10  8:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  8:43 Kane Jiang [this message]
2022-02-10  8:43 ` [PATCH 1/3] This patch adds support for the input capture function in the i.MX GPT. Output compare and input capture functions are mixed in the same register block, so we need to modify the irq ack/enable/ disable primitives to not stomp on the other function Kane Jiang
2022-02-10  8:43 ` [PATCH 2/3] Change to cyclecounter for GPT input capture. Add support for i.MX8MM Kane Jiang
2022-02-10  8:43 ` [PATCH 3/3] Add i.MX8MM GPT input capture example Kane Jiang
2022-02-10 14:47   ` Rob Herring
2022-02-11  8:40     ` [EXT] " Kane Jiang
2022-02-17  0:24       ` Rob Herring

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=20220210084335.1979778-1-jian.jiang@nxp.com \
    --to=jian.jiang@nxp.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=slongerbeam@gmail.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).