From: Thierry Reding <thierry.reding@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v3 2/2] i2c: Add Tegra BPMP I2C proxy driver
Date: Thu, 23 Feb 2017 17:18:50 +0100 [thread overview]
Message-ID: <20170223161850.GA15601@ulmo.ba.sec> (raw)
In-Reply-To: <20170220181747.lykox7o4ik6d5snu@ninjato>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On Mon, Feb 20, 2017 at 07:17:47PM +0100, Wolfram Sang wrote:
> On Mon, Feb 20, 2017 at 05:52:34PM +0100, Thierry Reding wrote:
> > From: Shardar Shariff Md <smohammed@nvidia.com>
> >
> > Add Tegra BPMP I2C driver. The BPMP is the boot and power management
> > processor embedded in Tegra SoCs. In newer SoC versions, access to one
> > of the I2C busses goes via the BPMP, requiring a different "proxy" I2C
> > driver that accesses the bus via the real I2C driver embedded in the
> > BPMP firmware.
> >
> > Signed-off-by: Shardar Shariff Md <smohammed@nvidia.com>
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> Applied to for-next, thanks (will be in for 4.11)!
Thanks for fast-tracking this!
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-23 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 16:52 [PATCH v3 1/2] dt-bindings: Add Tegra186 BPMP I2C binding Thierry Reding
[not found] ` <20170220165234.29299-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-20 16:52 ` [PATCH v3 2/2] i2c: Add Tegra BPMP I2C proxy driver Thierry Reding
[not found] ` <20170220165234.29299-2-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-20 18:17 ` Wolfram Sang
2017-02-23 16:18 ` Thierry Reding [this message]
2017-02-20 18:16 ` [PATCH v3 1/2] dt-bindings: Add Tegra186 BPMP I2C binding Wolfram Sang
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=20170223161850.GA15601@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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 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.