From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932224AbcFJOLc (ORCPT <rfc822;w@1wt.eu>);
	Fri, 10 Jun 2016 10:11:32 -0400
Received: from mailout3.w1.samsung.com ([210.118.77.13]:29464 "EHLO
	mailout3.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750886AbcFJOLb (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 10 Jun 2016 10:11:31 -0400
X-AuditID: cbfec7f4-f796c6d000001486-c7-575aca8e29fc
Subject: Re: [PATCH 2/2] clk: max77620: Add clock driver for MAX77620/MAX20024
To: Laxman Dewangan <ldewangan@nvidia.com>,
        Javier Martinez Canillas <javier@dowhile0.org>
References: <1465553536-23838-1-git-send-email-ldewangan@nvidia.com>
 <1465553536-23838-2-git-send-email-ldewangan@nvidia.com>
 <CABxcv=mrmN5Mzt595ZFgGbOoHJWQMwQ1wiCvcHEiWh_79EbJqQ@mail.gmail.com>
 <575ABD10.60208@nvidia.com>
 <CABxcv==7=PZ2HDtryNZHW0CcLaCAkBBT+XWJ0TJRS4uX48k_=w@mail.gmail.com>
 <575AC14D.4080907@nvidia.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
        Stephen Boyd <sboyd@codeaurora.org>, Rob Herring <robh+dt@kernel.org>,
        linux-clk@vger.kernel.org,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        Linux Kernel <linux-kernel@vger.kernel.org>
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Message-id: <575ACA8C.4000406@samsung.com>
Date: Fri, 10 Jun 2016 16:11:24 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.8.0
MIME-version: 1.0
In-reply-to: <575AC14D.4080907@nvidia.com>
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsVy+t/xy7p9p6LCDVruilvMP3KO1eLa7xls
	Fq9fGFos3beaxeJjzz1Wi8u75rBZXDzlatG69wi7xY8z3SwOnB7vb7Sye1zu62Xy+Du7ldlj
	06pONo/e5ndsHn1bVjF6fN4kF8AexWWTkpqTWZZapG+XwJXx68d71oIF7BWPrrUwNzBeZe1i
	5OSQEDCR+PSqhwnCFpO4cG89WxcjF4eQwFJGiY0bL7BDOM8YJVY0XgSrEhbwk7j+YhWQzcEh
	IhAjsb7TDKLmNJNE150rLCAOs0Ajk8TDd+1sIA1sAsYSm5cvAbN5BbQklnX0gw1iEVCV+Hdk
	MlhcVCBCYtb2H0wQNYISPybfYwGxOYHqb6++ywayjFlAXWLKlFyQMLOAvMTmNW+ZJzAKzELS
	MQuhahaSqgWMzKsYRVNLkwuKk9JzDfWKE3OLS/PS9ZLzczcxQiLhyw7GxcesDjEKcDAq8fBG
	7IoMF2JNLCuuzD3EKMHBrCTCu+RYVLgQb0piZVVqUX58UWlOavEhRmkOFiVx3rm73ocICaQn
	lqRmp6YWpBbBZJk4OKUaGIVSbl2dr8H8uSFs/k7h/f8m3DjK2ln0JOtk9t1dd086tLUYTZqp
	VnbgmvakGa9XlcS9Ojn9XNx2E+1fv6a9nTH9XaQep5W/4qrmo887lH/wttjreWREZ97vWT2r
	8Hr0kvP+U3N1I3JY95hfcYszKPxwrCWSP95NT9HRVy389oPXH274P+X+yaHEUpyRaKjFXFSc
	CADRI2RDgAIAAA==
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 06/10/2016 03:31 PM, Laxman Dewangan wrote:
> + Krzysztof,
> 
> On Friday 10 June 2016 07:02 PM, Javier Martinez Canillas wrote:
>> Hello Laxman,
>>
>> On Fri, Jun 10, 2016 at 9:13 AM, Laxman Dewangan
>> <ldewangan@nvidia.com> wrote:
>>> So until I change it too generic, it will not be possible.
>>> Also if it is require then what about all max77686/max77802 and
>>> max77620 in
>>> single file, the way we did for RTC.
>>> We dont need 4 files for the similar driver then.
>>>
>> Indeed, probably is better to have a single driver to handle all these
>> IP variants since they seem to be quite similar.
>>
>>
> Yaah, single driver will be very clean approach. But it needs some
> testing on max77802 and max77686 based platform as I do not have any
> driver.
> I will need help on this from you.

No problems, I have both devices at work so I can provide a tested-by.

Best regards,
Krzysztof