From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751586AbeECPxM (ORCPT ); Thu, 3 May 2018 11:53:12 -0400 Received: from lelnx194.ext.ti.com ([198.47.27.80]:17033 "EHLO lelnx194.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751195AbeECPw4 (ORCPT ); Thu, 3 May 2018 11:52:56 -0400 Subject: Re: [PATCH 1/2] ARM: dts: am335x: Replace numeric pinmux address with macro defines To: Tony Lindgren , Christina Quast CC: , , , , , Oleg Kokorin References: <20180430112006.20861-1-cquast@baylibre.com> <20180430112006.20861-2-cquast@baylibre.com> <20180430173146.GG5671@atomide.com> From: Grygorii Strashko Message-ID: <234521ee-3d8e-b413-65dd-5eefd44486d8@ti.com> Date: Thu, 3 May 2018 10:52:39 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180430173146.GG5671@atomide.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/30/2018 12:31 PM, Tony Lindgren wrote: > Hi, > > * Christina Quast [180430 11:23]: >> The values are extraced from the "AM335x SitaraTM Processors Technical >> Reference Manual", Section 9.3.1 CONTROL_MODULE Registers, based on the >> file autogenerated by TI PinMux. > > This certainly makes things easier to mux :) > > Have you verified that the registers are the same across all am335x > models and different revisions? > > It used to be that different SoC revisions could have different > amount of registers and also different options in some cases. > >> +#define AM335X_CONTROL_REVISION 0x0 >> +#define AM335X_CONTROL_HWINFO 0x4 >> +#define AM335X_CONTROL_SYSCONFIG 0x10 >> +#define AM335X_CONTROL_STATUS 0x40 > > You should only list the padconf mux registers here, no need to > list any of the controller registers. > To be honest, I do think it's right thing to do - DT by itself is documentation and previously DT maintainers were not very happy regarding introducing more defines instead of const. Adding such defines will introduce big headers in Linux common or platform folders again which we've just got rid of. If smth is unclear - comments can be used in DT. Just my 5c. -- regards, -grygorii