From: Akhil R <akhilrajeev@nvidia.com>
To: <andy.shevchenko@gmail.com>, <christian.koenig@amd.com>,
<digetx@gmail.com>, <dri-devel@lists.freedesktop.org>,
<jonathanh@nvidia.com>, <ldewangan@nvidia.com>,
<linaro-mm-sig@lists.linaro.org>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <p.zabel@pengutronix.de>,
<sumit.semwal@linaro.org>, <thierry.reding@gmail.com>,
<robh+dt@kernel.org>, <devicetree@vger.kernel.org>
Cc: akhilrajeev@nvidia.com
Subject: [PATCH 0/2] Add SMBus features to Tegra I2C
Date: Thu, 9 Dec 2021 20:35:19 +0530 [thread overview]
Message-ID: <1639062321-18840-1-git-send-email-akhilrajeev@nvidia.com> (raw)
Add support for SMBus Alert and SMBus block read functions to
i2c-tegra driver
Akhil R (2):
dt-bindings: i2c: tegra: Add SMBus feature properties
i2c: tegra: Add SMBus block read and SMBus alert functions
.../devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 4 ++
drivers/i2c/busses/i2c-tegra.c | 54 +++++++++++++++++++++-
2 files changed, 57 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2021-12-09 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 15:05 Akhil R [this message]
2021-12-09 15:05 ` [PATCH 1/2] dt-bindings: i2c: tegra: Add SMBus feature properties Akhil R
2021-12-09 15:30 ` Andy Shevchenko
2021-12-15 18:37 ` Rob Herring
2021-12-09 15:05 ` [PATCH 2/2] i2c: tegra: Add SMBus block read and SMBus alert functions Akhil R
2021-12-09 15:27 ` Dmitry Osipenko
2021-12-09 15:30 ` Dmitry Osipenko
2021-12-09 15:33 ` Andy Shevchenko
2021-12-09 15:42 ` Dmitry Osipenko
2021-12-09 15:43 ` Dmitry Osipenko
2021-12-09 16:04 ` [PATCH 0/2] Add SMBus features to Tegra I2C Dmitry Osipenko
2021-12-10 8:56 ` Thierry Reding
2021-12-15 18:42 ` 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=1639062321-18840-1-git-send-email-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=andy.shevchenko@gmail.com \
--cc=christian.koenig@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sumit.semwal@linaro.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 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).