Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751547AbdLLFFT (ORCPT ); Tue, 12 Dec 2017 00:05:19 -0500 Received: from netsrv01.beckhoff.com ([62.159.14.10]:57625 "EHLO Netsrv01.beckhoff.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750715AbdLLFFR (ORCPT ); Tue, 12 Dec 2017 00:05:17 -0500 From: =?utf-8?B?UGF0cmljayBCcsO8bm4=?= To: Fabio Estevam CC: Rob Herring , linux-kernel-dev , Shawn Guo , "Sascha Hauer" , Alessandro Zummo , Alexandre Belloni , Patrick Bruenn , Mark Rutland , "open list:REAL TIME CLOCK (RTC) SUBSYSTEM" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , open list , "Fabio Estevam" , Juergen Borleis , "Noel Vellemans" , Russell King , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Philippe Ombredanne , =?utf-8?B?TG90aGFyIFdhw59tYW5u?= Subject: RE: [PATCH v2 1/5] dt-bindings: rtc: add bindings for i.MX53 SRTC Thread-Topic: [PATCH v2 1/5] dt-bindings: rtc: add bindings for i.MX53 SRTC Thread-Index: AQHTbtzSyHH+KupWZEO997m97BxtEqM9oC1wgAEbHACAAHOJ4A== Date: Tue, 12 Dec 2017 05:05:14 +0000 Message-ID: <3BB206AB2B1BD448954845CE6FF69A8E01CB532561@NT-Mail07.beckhoff.com> References: <20171205140646.30367-1-linux-kernel-dev@beckhoff.com> <20171205140646.30367-2-linux-kernel-dev@beckhoff.com> <20171206215436.lwttn445wjilh3wo@rob-hp-laptop> <3BB206AB2B1BD448954845CE6FF69A8E01CB53233C@NT-Mail07.beckhoff.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.17.64.168] x-olx-disclaimer: Done Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id vBC55N0E026320 Content-Length: 1432 Lines: 44 >From: Fabio Estevam [mailto:festevam@gmail.com] >Sent: Dienstag, 12. Dezember 2017 00:08 >Hi Patrick, > Hi Fabio, >On Mon, Dec 11, 2017 at 5:08 AM, Patrick BrĂ¼nn >wrote: > >>>rtc@... >>> >> The rtc for which this series adds support is embedded within a function >block called >> "Secure Real Time Clock". This driver doesn't utilize all of the hardware >features by >> now. But maybe someone else wants to extend the functionalities, later. >> For that possibility I wanted to name the node "srtc". Should I still change >this? >> >> I believe you have a much better understanding of what should be done >here. I don't >> want to argue with you, just thought you might not had that information. So >if I am >> wrong just tell me and I will change it without further "complaining". > >From the Devicetree Specification document: > >"Generic Names Recommendation > >The name of a node should be somewhat generic, reflecting the function >of the device and not its precise program- >ming model. If appropriate, the name should be one of the following choices: >... >rtc >" > >So better use 'rtc' as suggested by Rob. Thanks for this clarification. I will wait a few days for more comments on the rest of the driver and then send a v4. Regards, Patrick Beckhoff Automation GmbH & Co. KG | Managing Director: Dipl. Phys. Hans Beckhoff Registered office: Verl, Germany | Register court: Guetersloh HRA 7075