From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rahul Sharma Subject: Re: [PATCHv2 1/3] phy: Add exynos-simple-phy driver Date: Wed, 7 May 2014 16:08:53 +0530 Message-ID: References: <1396967856-27470-1-git-send-email-t.stanislaws@samsung.com> <1396967856-27470-2-git-send-email-t.stanislaws@samsung.com> <534506B1.4040908@samsung.com> <53451A60.4050803@samsung.com> <53675D72.70103@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53675D72.70103@ti.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Kishon Vijay Abraham I Cc: Tomasz Stanislawski , "devicetree@vger.kernel.org" , linux-samsung-soc , Rob Herring , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , sunil joshi , Andrzej Hajda , Kyungmin Park , Kukjin Kim , Sylwester Nawrocki , Grant Likely , "linux-media@vger.kernel.org" List-Id: devicetree@vger.kernel.org On 5 May 2014 15:14, Kishon Vijay Abraham I wrote: > Hi, > > On Wednesday 09 April 2014 03:31 PM, Sylwester Nawrocki wrote: >> Hi, >> >> On 09/04/14 11:12, Rahul Sharma wrote: >>> Idea looks good. How about keeping compatible which is independent >>> of SoC, something like "samsung,exynos-simple-phy" and provide Reg >>> and Bit through phy provider node. This way we can avoid SoC specific >>> hardcoding in phy driver and don't need to look into dt bindings for >>> each new SoC. >> >> I believe it is a not recommended approach. > > Why not? We should try to avoid hard coding in the driver code. Moreover by > avoiding hardcoding we can make it a generic driver for single bit PHYs. > +1. @Tomasz, any plans to consider this approach for simple phy driver? Regards, Rahul Sharma. > Cheers > Kishon