From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/2] i2c: Add Tegra BPMP I2C proxy driver
Date: Tue, 15 Nov 2016 17:23:48 +0100 [thread overview]
Message-ID: <20161115162350.32405-1-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Hi Wolfram,
This series of patches depends on two branches in the Tegra tree, so I
think the easiest would be if you Acked-by'd this so that I can manage
the dependencies in the Tegra tree. The DT binding has already been
reviewed and I've tested the driver in my development tree for a while
and it's working great.
Thierry
Shardar Shariff Md (1):
i2c: Add Tegra BPMP I2C proxy driver
Stephen Warren (1):
dt-bindings: Add Tegra186 BPMP I2C binding
.../bindings/i2c/nvidia,tegra186-bpmp-i2c.txt | 42 +++
drivers/i2c/busses/Kconfig | 13 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-tegra-bpmp.c | 365 +++++++++++++++++++++
4 files changed, 421 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/nvidia,tegra186-bpmp-i2c.txt
create mode 100644 drivers/i2c/busses/i2c-tegra-bpmp.c
--
2.10.2
next reply other threads:[~2016-11-15 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 16:23 Thierry Reding [this message]
2016-11-15 16:23 ` [PATCH v2 1/2] dt-bindings: Add Tegra186 BPMP I2C binding Thierry Reding
2016-11-15 16:23 ` [PATCH v2 2/2] i2c: Add Tegra BPMP I2C proxy driver Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2017-01-27 8:39 [PATCH v2 0/2] " Thierry Reding
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=20161115162350.32405-1-thierry.reding@gmail.com \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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 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.