From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Udit Kumar <u-kumar1@ti.com>, Nitin Yadav <n-yadav@ti.com>,
Neha Malcom Francis <n-francis@ti.com>
Subject: Re: [PATCH 2/6] arm64: dts: ti: k3-j721e: Configure pinctrl for timer IO
Date: Fri, 2 Jun 2023 10:08:17 +0300 [thread overview]
Message-ID: <20230602070817.GI14287@atomide.com> (raw)
In-Reply-To: <20230531213215.602395-3-nm@ti.com>
* Nishanth Menon <nm@ti.com> [230531 21:32]:
> There are timer IO pads in the MCU domain, and in the MAIN domain. These
> pads can be muxed for the related timers.
>
> There are timer IO control registers for input and output. The registers
> for CTRLMMR_TIMER*_CTRL and CTRLMMR_MCU_TIMER*_CTRL are used to control
> the input. The registers for CTCTRLMMR_TIMERIO*_CTRL and
> CTRLMMR_MCU_TIMERIO*_CTRL the output.
>
> The multiplexing is documented in Technical Reference Manual[1] under
> "Timer IO Muxing Control Registers" and "Timer IO Muxing Control
> Registers", and the "Timers Overview" chapters.
>
> We do not expose the cascade_en bit due to the racy usage of
> independent 32 bit registers in-line with the timer instantiation in
> the device tree. The MCU timer controls are also marked as reserved for
> usage by the MCU firmware.
Reviewed-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-02 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 21:32 [PATCH 0/6] arm64: dts: ti: k3-j7*: Add general purpose timers Nishanth Menon
2023-05-31 21:32 ` [PATCH 1/6] arm64: dts: ti: k3-j721e: " Nishanth Menon
2023-06-02 7:07 ` Tony Lindgren
2023-05-31 21:32 ` [PATCH 2/6] arm64: dts: ti: k3-j721e: Configure pinctrl for timer IO Nishanth Menon
2023-06-02 7:08 ` Tony Lindgren [this message]
2023-05-31 21:32 ` [PATCH 3/6] arm64: dts: ti: k3-j721s2: Add general purpose timers Nishanth Menon
2023-06-02 7:09 ` Tony Lindgren
2023-05-31 21:32 ` [PATCH 4/6] arm64: dts: ti: k3-j721s2: Configure pinctrl for timer IO Nishanth Menon
2023-06-02 7:09 ` Tony Lindgren
2023-05-31 21:32 ` [PATCH 5/6] arm64: dts: ti: k3-j784s4: Add general purpose timers Nishanth Menon
2023-06-02 7:10 ` Tony Lindgren
2023-05-31 21:32 ` [PATCH 6/6] arm64: dts: ti: k3-j784s4: Configure pinctrl for timer IO Nishanth Menon
2023-06-02 7:10 ` Tony Lindgren
2023-06-15 13:19 ` [PATCH 0/6] arm64: dts: ti: k3-j7*: Add general purpose timers Vignesh Raghavendra
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=20230602070817.GI14287@atomide.com \
--to=tony@atomide.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=n-yadav@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).