From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753930AbbJTIUy (ORCPT ); Tue, 20 Oct 2015 04:20:54 -0400 Received: from mailout2.samsung.com ([203.254.224.25]:41967 "EHLO mailout2.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753878AbbJTIUv (ORCPT ); Tue, 20 Oct 2015 04:20:51 -0400 X-AuditID: cbfee68d-f79ae6d00000149a-41-5625f95f8ab5 Date: Tue, 20 Oct 2015 17:20:47 +0900 From: Andi Shyti To: Pavel Fedin Cc: "'Krzysztof Kozlowski'" , "'Pankaj Dubey'" , linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kgene.kim@samsung.com, thomas.ab@samsung.com Subject: Re: [PATCH v4 6/8] drivers: soc: add support for exynos SROM driver Message-id: <20151020082047.GA923@samsunx.samsung> References: <1445255206-11148-1-git-send-email-pankaj.dubey@samsung.com> <1445255206-11148-7-git-send-email-pankaj.dubey@samsung.com> <56258683.7070204@samsung.com> <5625B92C.10505@samsung.com> <5625C07D.4030706@samsung.com> <014301d10b01$488873f0$d9995bd0$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline In-reply-to: <014301d10b01$488873f0$d9995bd0$@samsung.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDIsWRmVeSWpSXmKPExsWyRsSkQDf+p2qYwcXFchavXxha9C64ymax 6fE1VovLu+awWcw4v4/J4tWlVWwWi7Z+YbfoWMbowOGxeUm9R9+WVYwenzfJBTBHcdmkpOZk lqUW6dslcGVcXf6QseAWe8WXbSfYGhj/s3YxcnBICJhITHpq3cXICWSKSVy4t56ti5GLQ0hg BaPE/n9LmCESJhKHjuxihUgsZZT4uPEDI4TziVHi66Yb7CBVLAKqEsfPtrKB2GwCmhJNt3+A 2SJA8fsNV9lBGpgFfjJK7D2ymBEkISzgI3F2zQcWEJtXwEhibudzqN1TmCSe9D1hhUgISvyY fA+siFlAS2L9zuNMELa0xKO/M8A2cwpYSSx9uJgN5B9RARWJVwfrQeZICBxjl1jesIQN4joB iW+TD7FA/CwrsekA1GuSEgdX3GCZwCg2C8m2WUi2zUKybQEj8ypG0dSC5ILipPQiQ73ixNzi 0rx0veT83E2MwEg7/e9Z7w7G2wesDzEKcDAq8fBqxKiGCbEmlhVX5h5iNAW6YiKzlGhyPjCe 80riDY3NjCxMTUyNjcwtzZTEeRWlfgYLCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYGT7GvlJ f/VblYZpyQze8sc1X9zaH8guuXHxEdEdYdO3PXYSmxY1aWLUlFv9IpV66iYrtvWecWs5uOdR 9au/Uosfuxx/sraf73gLF4O7znQl/x88PhPmtjWmXLv+v2qvzKsy5wXmEg12PzMivmSuXD77 xpq7HE/31x2pvn3Ihy3XimvjPMmZldpKLMUZiYZazEXFiQCnCr48rwIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsVy+t9jAd34n6phBlfmSFq8fmFo0bvgKpvF psfXWC0u75rDZjHj/D4mi1eXVrFZLNr6hd2iYxmjA4fH5iX1Hn1bVjF6fN4kF8Ac1cBok5Ga mJJapJCal5yfkpmXbqvkHRzvHG9qZmCoa2hpYa6kkJeYm2qr5OIToOuWmQO0X0mhLDGnFCgU kFhcrKRvh2lCaIibrgVMY4Sub0gQXI+RARpIWMOYcXX5Q8aCW+wVX7adYGtg/M/axcjJISFg InHoyC4oW0ziwr31bF2MXBxCAksZJT5u/MAI4XxilPi66QY7SBWLgKrE8bOtbCA2m4CmRNPt H2C2CFD8fsNVdpAGZoGfjBJ7jyxmBEkIC/hInF3zgQXE5hUwkpjb+RxqxRQmiSd9T1ghEoIS PybfAytiFtCSWL/zOBOELS3x6O8MsM2cAlYSSx8uBmrm4BAVUJF4dbB+AqPALCTds5B0z0LS vYCReRWjRGpBckFxUnquYV5quV5xYm5xaV66XnJ+7iZGcDw/k9rBeHCX+yFGAQ5GJR5ejRjV MCHWxLLiytxDjBIczEoivM9OAIV4UxIrq1KL8uOLSnNSiw8xmgJDZCKzlGhyPjDV5JXEGxqb mBlZGpkbWhgZmyuJ8944xBAmJJCeWJKanZpakFoE08fEwSnVwBjwYV29t/jdzv2t+hOE41N5 dv+uWiKofl/pgoHAMRFX3Vd/H89fcPFRbeXqAKsop/+1EXJHTphGCfTEz2CPeatTe9dT1H3L tV/dZ/yfr1/s5q9zh3Hq8iWqFa71SamrVW0Y131ONwv+q/VrdsSOr1LTj1eyLV6rVybaYFqr 6zt55oW7F/RfLFBiKc5INNRiLipOBAA6X0Tr/QIAAA== DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Pavel, > > AFAIR Fedin was talking about missing functionality, not about adding > > the contribution by himself. So he might add it or he might not. I did > > not receive any commitments from him. > > I am waiting for the driver to be integrated, because i see it's constantly redesigned. Then i'll post my patches. By the way, they > will be useful only if pin controller driver for 5410 is accepted upstream, several authors have done it but i still didn't see it > in upstream. > Pin controller is needed in order to configure multi-functional pins correctly. > > > The driver should be "proper" for > > the time being (which could mean !PM dependency). If there is a need, > > then the dependency will be removed. > > I can do it later if you prefer. can we add the "depends on ... && PM" now, later, once you'll extend it, you remove it again? Personally I'd prefer this way rather than having a driver that does nothing in case of !PM. Andi