lkml.org 
[lkml]   [2017]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: n900 in next-20170901
* Joonsoo Kim <iamjoonsoo.kim@lge.com> [171109 00:05]:
> On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote:
> > * Joonsoo Kim <iamjoonsoo.kim@lge.com> [171108 07:43]:
> > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote:
> > > > So it seems the issue is currently at the atomic_pool_init()
> > > > related code?
> > >
> > > Yes, your test showed it although I can't find any clue in
> > > atomic_pool_init().
> > >
> > > Could you test updated branch?
> > >
> > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901
> > >
> > > There are two relevant commits.
> > >
> > > arm/dma: stop dma allocation before __dma_alloc_remap()
> > > arm/dma: disable atomic pool after dma allocation
> > >
> > > atomic pool initialization will be done partially to check
> > > exact point of failure. These are brain-dead commits however I have no
> > > idea what's going on here until now. :/
> >
> > OK that booted, dmesg output below. Hopefully that provides
> > you with some more clues.
>
> Thanks!
>
> Could you let me know which one is booted? Both of them? or just top
> commit ("arm/dma: stop dma allocation before __dma_alloc_remap()")?

Oh OK. Only the top commit boots.

Regards,

Tony

\
 
 \ /
  Last update: 2017-11-09 01:11    [W:0.130 / U:3.288 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site