From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH 2/5] clk: Combine DT binding doc for max77686 and max77802 To: Javier Martinez Canillas , Laxman Dewangan , mturquette@baylibre.com, robh+dt@kernel.org, linux@armlinux.org.uk References: <1466000018-16784-1-git-send-email-ldewangan@nvidia.com> <1466000018-16784-3-git-send-email-ldewangan@nvidia.com> Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, Javier Martinez Canillas From: Krzysztof Kozlowski Message-id: <576272BA.50800@samsung.com> Date: Thu, 16 Jun 2016 11:34:50 +0200 MIME-version: 1.0 In-reply-to: Content-type: text/plain; charset=windows-1252 List-ID: On 06/15/2016 05:19 PM, Javier Martinez Canillas wrote: >> Remove the separate DT binding document file for maxim,max77802 and >> move all information to maxim,max77686 DT binding document. >> > > Now, I wonder if this is the correct approach. A system integrator is > probably going to search for the bindings of the chip that is present > in their system. For example there are different DT bindings docs for > both the max77686 and max77802 PMIC even when support is implemented > by the same driver (drivers/mfd/max77686.c). > > But maybe I'm wrong so I'll let people with more DT experience to say > if merging the bindings docs in a single one is the correct approach. I personally prefer having one binding document for all devices because essentially it is almost the same device. For looking up I use git grep with compatible string (or device name) so it does not matter, IMHO. Best regards, Krzysztof