From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752153AbdHHL4I (ORCPT ); Tue, 8 Aug 2017 07:56:08 -0400 Received: from mail-qt0-f173.google.com ([209.85.216.173]:33979 "EHLO mail-qt0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751925AbdHHL4G (ORCPT ); Tue, 8 Aug 2017 07:56:06 -0400 MIME-Version: 1.0 In-Reply-To: <20170723141354.42646-2-icenowy@aosc.io> References: <20170723141354.42646-1-icenowy@aosc.io> <20170723141354.42646-2-icenowy@aosc.io> From: Vincent Legoll Date: Tue, 8 Aug 2017 13:56:05 +0200 Message-ID: Subject: Re: [linux-sunxi] [PATCH v3 1/5] dt-bindings: update the Allwinner GPADC device tree binding for H3 To: icenowy@aosc.io Cc: Lee Jones , Rob Herring , Maxime Ripard , Chen-Yu Tsai , Jonathan Cameron , Quentin Schulz , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Linux Kernel ML , linux-iio@vger.kernel.org, linux-sunxi@googlegroups.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Sorry for the very-clueless question On Sun, Jul 23, 2017 at 4:13 PM, Icenowy Zheng wrote: > + - clock-names: should be "bus" and "mod", When I first read that, I wondered what value clock-names should eally be given. Then... > + clock-names = "bus", "mod"; OK, now this is clearer, but still the documentation is less documenting than the code itself, sigh... I cannot think of a better wording, though, as a non-native-english speaker. Maybe just add a "(See example below)" would be sufficient... Or decide that this documentation is for clueful ones. WDYT ? -- Vincent Legoll From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Legoll Subject: Re: [PATCH v3 1/5] dt-bindings: update the Allwinner GPADC device tree binding for H3 Date: Tue, 8 Aug 2017 13:56:05 +0200 Message-ID: References: <20170723141354.42646-1-icenowy@aosc.io> <20170723141354.42646-2-icenowy@aosc.io> Reply-To: vincent.legoll-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org In-Reply-To: <20170723141354.42646-2-icenowy-h8G6r0blFSE@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: icenowy-h8G6r0blFSE@public.gmane.org Cc: Lee Jones , Rob Herring , Maxime Ripard , Chen-Yu Tsai , Jonathan Cameron , Quentin Schulz , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Linux Kernel ML , linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-Id: devicetree@vger.kernel.org Hello, Sorry for the very-clueless question On Sun, Jul 23, 2017 at 4:13 PM, Icenowy Zheng wrote: > + - clock-names: should be "bus" and "mod", When I first read that, I wondered what value clock-names should eally be given. Then... > + clock-names = "bus", "mod"; OK, now this is clearer, but still the documentation is less documenting than the code itself, sigh... I cannot think of a better wording, though, as a non-native-english speaker. Maybe just add a "(See example below)" would be sufficient... Or decide that this documentation is for clueful ones. WDYT ? -- Vincent Legoll From mboxrd@z Thu Jan 1 00:00:00 1970 From: vincent.legoll@gmail.com (Vincent Legoll) Date: Tue, 8 Aug 2017 13:56:05 +0200 Subject: [linux-sunxi] [PATCH v3 1/5] dt-bindings: update the Allwinner GPADC device tree binding for H3 In-Reply-To: <20170723141354.42646-2-icenowy@aosc.io> References: <20170723141354.42646-1-icenowy@aosc.io> <20170723141354.42646-2-icenowy@aosc.io> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello, Sorry for the very-clueless question On Sun, Jul 23, 2017 at 4:13 PM, Icenowy Zheng wrote: > + - clock-names: should be "bus" and "mod", When I first read that, I wondered what value clock-names should eally be given. Then... > + clock-names = "bus", "mod"; OK, now this is clearer, but still the documentation is less documenting than the code itself, sigh... I cannot think of a better wording, though, as a non-native-english speaker. Maybe just add a "(See example below)" would be sufficient... Or decide that this documentation is for clueful ones. WDYT ? -- Vincent Legoll