From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756558AbbIUMKY (ORCPT ); Mon, 21 Sep 2015 08:10:24 -0400 Received: from mx0b-0016f401.pphosted.com ([67.231.156.173]:19799 "EHLO mx0b-0016f401.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752950AbbIUMKV (ORCPT ); Mon, 21 Sep 2015 08:10:21 -0400 Date: Mon, 21 Sep 2015 20:06:11 +0800 From: Jisheng Zhang To: Sebastian Hesselbarth CC: , , , , , , , , , , , , Subject: Re: [PATCH 2/5] pinctrl: berlin: add the berlin4ct pinctrl driver Message-ID: <20150921200611.5e55e9d5@xhacker> In-Reply-To: <55FF09D5.6090707@gmail.com> References: <1442656956-5740-1-git-send-email-jszhang@marvell.com> <1442656956-5740-3-git-send-email-jszhang@marvell.com> <55FF09D5.6090707@gmail.com> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-09-21_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1507310000 definitions=main-1509210190 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Sebastian, On Sun, 20 Sep 2015 21:32:37 +0200 Sebastian Hesselbarth wrote: > > + BERLIN_PINCTRL_GROUP("SM_TDO", 0x0, 0x3, 0x12, > > + BERLIN_PINCTRL_FUNCTION(0x0, "sm_tdo"), > > + BERLIN_PINCTRL_FUNCTION(0x1, "sm_gpio2")), > > + BERLIN_PINCTRL_GROUP("SM_URT0_TXD", 0x0, 0x3, 0x15, > > + BERLIN_PINCTRL_FUNCTION(0x0, "sm_urt0_txd"), > > Please avoid abbreviating acronyms even more, we can afford the > few extra bytes. In the 2nd version, I kept using HW names, for example: 1. "urt0" as the function name, 2. "SM_URT0_TXD" as the pin name (group name) to keep sync with HW, especially the pin names are the same as HW's, because that's what HW doc, sch, etc. call them. IMHO, using a different name with HW is not a good idea, what do you think? Thanks, Jisheng