From: Akhil R <akhilrajeev@nvidia.com>
To: <robh+dt@kernel.org>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <mperttunen@nvidia.com>,
<ldewangan@nvidia.com>, <digetx@gmail.com>,
<linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <akhilrajeev@nvidia.com>
Subject: [PATCH 0/6] Add I2C and PWM support for T234
Date: Thu, 13 Jan 2022 19:00:17 +0530 [thread overview]
Message-ID: <1642080623-15980-1-git-send-email-akhilrajeev@nvidia.com> (raw)
The patchset contains driver and devicetree changes to support I2C and
PWM for Tegra234
Akhil R (6):
i2c: tegra: Add support for Tegra234 I2C
dt-bindings: i2c: tegra: Add Tegra234 details
dt-bindings: Add headers for Tegra234 I2C
arm64: tegra: Add Tegra234 I2C devicetree nodes
dt-bindings: Add headers for Tegra234 PWM
arm64: tegra: Add Tegra234 PWM devicetree nodes
.../bindings/i2c/nvidia,tegra20-i2c.yaml | 5 +
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 133 +++++++++++++++++++++
drivers/i2c/busses/i2c-tegra.c | 25 ++++
include/dt-bindings/clock/tegra234-clock.h | 36 ++++++
include/dt-bindings/reset/tegra234-reset.h | 16 +++
5 files changed, 215 insertions(+)
--
2.7.4
next reply other threads:[~2022-01-13 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 13:30 Akhil R [this message]
2022-01-13 13:30 ` [PATCH 1/6] i2c: tegra: Add support for Tegra234 I2C Akhil R
2022-01-18 20:54 ` Dmitry Osipenko
2022-01-19 8:20 ` Akhil R
2022-01-19 12:20 ` Dmitry Osipenko
2022-01-20 14:23 ` Akhil R
2022-01-13 13:30 ` [PATCH 2/6] dt-bindings: i2c: tegra: Add Tegra234 details Akhil R
2022-02-09 2:17 ` Rob Herring
2022-02-09 3:54 ` Akhil R
2022-01-13 13:30 ` [PATCH 3/6] dt-bindings: Add headers for Tegra234 I2C Akhil R
2022-01-13 13:30 ` [PATCH 4/6] arm64: tegra: Add Tegra234 I2C devicetree nodes Akhil R
2022-01-13 13:30 ` [PATCH 5/6] dt-bindings: Add headers for Tegra234 PWM Akhil R
2022-01-13 13:30 ` [PATCH 6/6] arm64: tegra: Add Tegra234 PWM devicetree nodes Akhil R
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=1642080623-15980-1-git-send-email-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.