linux-kernel - Re: [PATCH v5 3/6] ARM: AM335x/AM437x: hwmod: Remove eQEP, ePWM and eCAP hwmod entries

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL_Jsq+mEPzt3DZLSWhnSuGdqErWQLEv_rGcu2zcn67HfUkMew@mail.gmail.com>
Date:	Thu, 17 Mar 2016 14:04:07 -0500
From:	Rob Herring <robh@...nel.org>
To:	"Franklin S Cooper Jr." <fcooper@...com>
Cc:	Thierry Reding <thierry.reding@...il.com>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Benoit Cousson <bcousson@...libre.com>,
	Tony Lindgren <tony@...mide.com>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	"paul@...an.com" <paul@...an.com>,
	Linux PWM List <linux-pwm@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-omap <linux-omap@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>, Vignesh R <vigneshr@...com>
Subject: Re: [PATCH v5 3/6] ARM: AM335x/AM437x: hwmod: Remove eQEP, ePWM and
 eCAP hwmod entries

On Thu, Mar 17, 2016 at 10:45 AM, Franklin S Cooper Jr. <fcooper@...com> wrote:
>
>
> On 03/17/2016 10:06 AM, Rob Herring wrote:
>> On Mon, Mar 07, 2016 at 07:23:41PM -0600, Franklin S Cooper Jr wrote:
>>> Devices that utilize the OCP registers and/or PRCM registers and
>>> register bit fields should be modelled using hwmod. Since eQEP, ePWM and
>> s/modelled/modeled/
>
> Will fix.
>>
>>> eCAP don't fall under this category, remove their hwmod entries.
>>>
>>> Instead these clocks simply use the clock that is pass through by its
>>> parent PWMSS. Therefore, PWMSS handles the clock for itself and its
>>> subdevices.
>> Are you breaking compatibility with old DTs here?
>
> No. The first patch makes sure that the ecap and ehrpwm get
> their clocks from their parent which is all they care about.
> Old dtbs will have hwmod entries for ecap and ehrpwm which
> will end up not doing anything.

Okay.

Acked-by: Rob Herring <robh@...nel.org>