linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH v2 0/2] i2c: Add Tegra BPMP I2C proxy driver
Date: Fri, 27 Jan 2017 09:39:37 +0100	[thread overview]
Message-ID: <20170127083939.20393-1-thierry.reding@gmail.com> (raw)

From: Thierry Reding <treding@nvidia.com>

Hi Wolfram,

I had originally sent these in for the last merge window but then got
bounces indicating that your email server was not accepting emails. At
the time it seemed like I wasn't the only one having these problems.

Looking at my mailbox that situation now seems to be resolved, so here's
hoping it'll work this time. Note that because of the above I've carried
this in the Tegra tree for a while now to get it more compile testing.
If you end up applying the set, please let me know so I can drop them
from the Tegra tree and avoid conflicts in linux-next.

On the bright side the dependencies for this were merged during the last
release cycle, so these should be good to go in without further
complications.

Thanks,
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                         |  11 +
 drivers/i2c/busses/Makefile                        |   1 +
 drivers/i2c/busses/i2c-tegra-bpmp.c                | 365 +++++++++++++++++++++
 4 files changed, 419 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/i2c/nvidia,tegra186-bpmp-i2c.txt
 create mode 100644 drivers/i2c/busses/i2c-tegra-bpmp.c

-- 
2.11.0

             reply	other threads:[~2017-01-27  8:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27  8:39 Thierry Reding [this message]
     [not found] ` <20170127083939.20393-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-27  8:39   ` [PATCH v2 1/2] dt-bindings: Add Tegra186 BPMP I2C binding Thierry Reding
2017-01-27 16:09     ` Wolfram Sang
     [not found]     ` <20170127083939.20393-2-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-27 22:19       ` Thierry Reding
     [not found]         ` <20170127221857.GA15715-+E7KM1FDEuO2P7RxrfNFTMXXUOn6P5/W@public.gmane.org>
2017-01-27 22:52           ` Rob Herring
     [not found]             ` <CAL_Jsq+Sr=dOw7_9UAL4jO0zXycT7sHoCvUM4C2-9LBgdx=25g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-30  6:47               ` Thierry Reding
2017-01-28  5:42         ` Stephen Warren
     [not found]           ` <8841854b-d058-1a8d-3e40-955bf3546cef-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2017-01-30  6:50             ` Thierry Reding
2017-01-27  8:39   ` [PATCH v2 2/2] i2c: Add Tegra BPMP I2C proxy driver Thierry Reding
2017-02-10 16:37     ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2016-11-15 16:23 [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=20170127083939.20393-1-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=wsa@the-dreams.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).