From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750998AbbABJNs (ORCPT ); Fri, 2 Jan 2015 04:13:48 -0500 Received: from mail-pa0-f41.google.com ([209.85.220.41]:46066 "EHLO mail-pa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750722AbbABJNp (ORCPT ); Fri, 2 Jan 2015 04:13:45 -0500 Message-ID: <54A66143.2080506@gmail.com> Date: Fri, 02 Jan 2015 18:13:39 +0900 From: Tomasz Figa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Nishanth Menon CC: Marek Szyprowski , linux-kernel , linux-arm-kernel , Kyungmin Park , "linux-samsung-soc@vger.kernel.org" , linux-omap , Arnd Bergmann , Olof Johansson , Russell King - ARM Linux , Kukjin Kim , Laura Abbott , Linus Walleij , Tony Lindgren , Daniel Drake , Jon Loeliger , Mark Rutland , Kevin Hilman Subject: Re: [PATCH v10 2/8] ARM: l2c: Refactor the driver to use commit-like interface References: <1419331716-8972-1-git-send-email-m.szyprowski@samsung.com> <1419331716-8972-3-git-send-email-m.szyprowski@samsung.com> <54A19C17.1020909@ti.com> <54A2BBDC.1020900@ti.com> In-Reply-To: <54A2BBDC.1020900@ti.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30.12.2014 23:51, Nishanth Menon wrote: >>> Looks like the following also need addressing: >>> data->save is called twice (once more after l2cof_init) >>> l2c310_init_fns also needs l2c310_configure >>> will be nice to use l2x0_data only after we kmemdup data in __l2c_init >> >> I'll check this. > Thanks. > Apparently the second save in __l2c_init() is not needed and it should have been removed. However it might be a good idea to actually do second save in l2c_enable() after l2c_configure() so that the values actually permitted by hardware and/or secure firmware are stored. l2c310_init_fns needs to be updated indeed. However I'm not sure about your concern about using l2x0_data before kmemdup(). I don't see any code potentially doing this. Best regards, Tomasz