linux-kernel - Re: [PATCH v8 1/3] ARM: EXYNOS: Add support for EXYNOS5410 SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 24 Apr 2014 18:01:06 +0200
From:	Tomasz Figa <t.figa@...sung.com>
To:	Tarek Dakhran <t.dakhran@...sung.com>,
	Arnd Bergmann <arnd@...db.de>,
	linux-arm-kernel@...ts.infradead.org
Cc:	linux-kernel@...r.kernel.org, Mark Rutland <mark.rutland@....com>,
	Heiko Stuebner <heiko@...ech.de>, linux-doc@...r.kernel.org,
	Chander Kashyap <chander.kashyap@...aro.org>,
	Romain Naour <romain.naour@...nwide.fr>,
	Tarek Dakhran <t.dakhran@...il.com>,
	Kukjin Kim <kgene.kim@...sung.com>,
	Russell King <linux@....linux.org.uk>,
	Thomas Abraham <thomas.abraham@...aro.org>,
	devicetree@...r.kernel.org, Pawel Moll <pawel.moll@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	linux-samsung-soc@...r.kernel.org,
	Vyacheslav Tyrtov <v.tyrtov@...sung.com>,
	Ben Dooks <ben-linux@...ff.org>,
	Mike Turquette <mturquette@...aro.org>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Rob Herring <robh+dt@...nel.org>,
	Rob Landley <rob@...dley.net>,
	Kumar Gala <galak@...eaurora.org>
Subject: Re: [PATCH v8 1/3] ARM: EXYNOS: Add support for EXYNOS5410 SoC

Hi Tarek,

On 14.04.2014 13:59, Tarek Dakhran wrote:
> On 04/14/2014 03:03 PM, Arnd Bergmann wrote:
>> On Monday 14 April 2014 11:17:38 Tarek Dakhran wrote:
>>> --- a/arch/arm/mach-exynos/exynos.c
>>> +++ b/arch/arm/mach-exynos/exynos.c
>>> @@ -159,6 +159,15 @@ static struct map_desc exynos5250_iodesc[]
>>> __initdata = {
>>>          },
>>>   };
>>> +static struct map_desc exynos5410_iodesc[] __initdata = {
>>> +       {
>>> +               .virtual        = (unsigned long)S5P_VA_SYSRAM_NS,
>>> +               .pfn            =
>>> __phys_to_pfn(EXYNOS5410_PA_SYSRAM_NS),
>>> +               .length         = SZ_4K,
>>> +               .type           = MT_DEVICE,
>>> +       },
>>> +};
>>> +
>>>   static struct map_desc exynos5_iodesc[] __initdata = {
>> NAK
>>
>> Why does this keep coming up?
>>
>>     Arnd
>>
> We need this memory region because boot address for exynos5410 located
> here, same as for 5250.
>

Is there really no way to map this region dynamically in the entity 
(driver, source file, whatever) that actually uses it? The goal is to 
get rid of all the static mappings entirely, so adding new one makes us 
further from it.

Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/