On Mon, Aug 06, 2018 at 08:05:06PM +0200, Wolfram Sang wrote:
> On Wed, Jul 25, 2018 at 09:16:55PM +0200, Wolfram Sang wrote:
> > Update the binding docs for Renesas R-Car M3-N. No driver changes are
> > needed.
> >
> > Signed-off-by: Wolfram Sang
>
> Tejun, could you pick this also for 4.19?
>
On Mon, Aug 06, 2018 at 12:40:05PM +0200, Wolfram Sang wrote:
> Since R-Car Gen2, a new bit has been introduced to the interrupt mask
> register. Update the code to handle it properly as well.
>
> Signed-off-by: Wolfram Sang
Applied to libata/for-4.19.
Thanks.
--
tejun
On Mon, Aug 06, 2018 at 12:42:00PM +0200, Wolfram Sang wrote:
> From: Masaharu Hayakawa
>
> According to documentation, setting of PHY registers is unnecessary with
> R-Car Gen3. The registers are not even described. So, don't initialize
> them.
>
> Signed-off-by: Masaharu Hayakawa
> [wsa:
On Fri, Jul 20, 2018 at 02:27:38PM +0200, Geert Uytterhoeven wrote:
> No functional changes.
>
> Signed-off-by: Geert Uytterhoeven
Applied 1-2 to libata/for-4.19.
Thanks.
--
tejun
On Tue, Feb 13, 2018 at 01:43:23PM +0100, Geert Uytterhoeven wrote:
> drivers/ata/sata_rcar.c: In function 'sata_rcar_init_controller':
> drivers/ata/sata_rcar.c:821:8: warning: unused variable 'base'
> [-Wunused-variable]
>
> Fixes: da77d76b95a0e894 ("sata_rcar: Reset SATA PHY when Salvator-X
On Mon, Feb 05, 2018 at 04:18:51AM +0900, Yoshihiro Kaneko wrote:
> From: Khiem Nguyen
>
> Because power of Salvator-X board is cut off in suspend,
> it needs to reset SATA PHY state in resume.
> Otherwise, SATA partition could not be accessed anymore.
>
>
On Tue, Jul 11, 2017 at 01:44:20PM +0200, Simon Horman wrote:
> Add fallback compatibility string for R-Car Gen 2 and 3.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, e.g. Gen 1 and 2. But beyond that its not clear what the relationship
> between IP
On Tue, Apr 18, 2017 at 04:02:53PM +0900, Simon Horman wrote:
> In the case where power is cut on suspend the SATA PHY state needs to be
> suspended on resume.
^
re-initialized?
>
> This is the case on the Salvator-X board with the r8a7795 or r8a7796 SoC.
> In that environment it has been
On Thu, Mar 03, 2016 at 10:28:50AM +0900, Simon Horman wrote:
> Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
>
> This is part of an ongoing process to migrate from ARCH_SHMOBILE to
> ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
> appropriate name than
Hello,
On Mon, Feb 29, 2016 at 02:44:16PM +0100, Geert Uytterhoeven wrote:
> sata_rcar ee30.sata: DMA-API: cpu touching an active dma mapped
> cacheline [cln=0x0090ff40]
> [ cut here ]
> WARNING: at lib/dma-debug.c:604
> Modules linked in:
>
> CPU: 2 PID: 329
On Thu, Feb 25, 2016 at 4:40 PM, Tejun Heo <t...@kernel.org> wrote:
> Is this the problem fixed by the following patch from Harvey?
>
>
> http://lkml.kernel.org/g/CAMuHMdU0=_TJVfy=-zxwhkfjswh_fjulbrl8j9t60qs48wb...@mail.gmail.com
Oops, I meant
http://lkml.kernel.org/g/1456
Hello,
cc'ing Harvey.
On Wed, Feb 24, 2016 at 01:42:33PM +0100, Geert Uytterhoeven wrote:
> With CONFIG_DMA_API_DEBUG=y, I sometimes get the below warning
> on r8a7795/salvator-x. My tree is based on
> renesas-drivers-2016-02-23-v4.5-rc5.
>
> sata_rcar ee30.sata: DMA-API: cpu touching an
12 matches
Mail list logo