[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-tegra
Subject:    Re: [PATCH v2 2/3] soc/tegra: bpmp: Update ABI header
From:       Thierry Reding <thierry.reding () gmail ! com>
Date:       2017-04-27 14:19:49
Message-ID: 20170427141949.GB21118 () ulmo ! ba ! sec
[Download RAW message or body]

On Thu, Apr 20, 2017 at 02:44:48AM +0200, Rafael J. Wysocki wrote:
> On Wednesday, March 29, 2017 06:34:51 PM Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> > 
> > Update the BPMP ABI header to a more recent version. The new version
> > adds support for a new powergating ABI as well as access to the ring
> > buffer console, which allows debug messages to be output to the BPMP
> > debug console.
> > 
> > Some of the previously undocumented fields have been documented and
> > missing bitmasks have been added. Furthermore the MRQ_RESET request
> > now has a sub-command that allows to determine the maximum ID which
> > in turn allows the resets to be enumerated, thereby allowing drivers
> > to become agnostic of the Tegra generation.
> > 
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> 
> I could queue up the [1,3/3] with the Ulf's ACKs, but I can't really say
> whether or not this one makes sense. :-)
> 
> Any chance to ask the ARM/soc people for an ACK?

Sorry for the late reply. I think at this point it might make the most
sense if you queued up 1/3 for 4.12 and I can take 2/3 and 3/3 into
linux-next shortly after v4.12-rc1, then merge this through ARM SoC
along with any other patches for v4.13.

Does that sound reasonable?

Thanks,
Thierry

["signature.asc" (application/pgp-signature)]
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[prev in list] [next in list] [prev in thread] [next in thread]