Messages in this thread |  | | Date | Wed, 6 Sep 2017 06:30:57 -0700 | From | Tony Lindgren <> | Subject | Re: n900 in next-20170901 |
| |
Hi,
* Joonsoo Kim <iamjoonsoo.kim@lge.com> [170905 16:32]: > I think that I made a mistake for configuration CONFIG_HIGHMEM=y and > CONFIG_HAVE_MEMBLOCK_NODE_MAP=y. In this case, the MOVABLE_ZONE can > be *!highmem*. Could you check that your configuration have above > options?
CONFIG_HIGHMEM is set yeah.
> And, could you check that following patch works for you?
Does not seem to help, tried against next with just 9caf25f996e8 revert and also with 9caf25f996e8.
Regards,
Tony
> ------------>8----------------- > diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c > index 38f0fde..4c39c92 100644 > --- a/arch/arm/mm/dma-mapping.c > +++ b/arch/arm/mm/dma-mapping.c > @@ -518,7 +518,7 @@ void __init dma_contiguous_remap(void) > * considered as highmem even if it's physical address belong > * to lowmem. Therefore, re-mapping isn't required. > */ > - if (!IS_ENABLED(CONFIG_HIGHMEM)) > + if (!is_highmem_idx(ZONE_MOVABLE)) > iotable_init(&map, 1); > } > } >
|  |