Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Florian Fainelli <f.fainelli@gmail.com>
To:     bcm-kernel-feedback-list@broadcom.com,
        Markus Mayer <code@mmayer.net>,
        Brian Norris <computersforpeace@gmail.com>,
        Gregory Fong <gregory.0xf0@gmail.com>
Cc:     Markus Mayer <mmayer@broadcom.com>,
        ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] soc: brcmstb: dpfe: use byte 3 of registers MR4-MR8
Date:   Sat,  9 Mar 2019 14:03:32 -0800
Message-Id: <20190309220332.26100-1-f.fainelli@gmail.com>
In-Reply-To: <20190212012443.21819-4-code@mmayer.net>
References: <20190212012443.21819-1-code@mmayer.net> <20190212012443.21819-4-code@mmayer.net>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, 11 Feb 2019 17:24:43 -0800, Markus Mayer <code@mmayer.net> wrote:
> From: Markus Mayer <mmayer@broadcom.com>
> 
> For dual-rank LPDDR4, result data for any command is placed in byte 0
> and byte 3 of the corresponding MR register by the firmware.
> Single-rank RAM was supposed to work the same way. However, due to a
> firmware bug, result values are only placed in byte 3 of the
> corresponding MR register.
> 
> Since byte 3 works for single-rank and dual-rank setups, we change the
> Linux driver to always use byte 3, thus returning the correct value in
> either case.
> 
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---

Applied to drivers/next, thanks!
--
Florian