From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vinod Koul Subject: Re: [PATCH v3] dmaengine: mv_xor_v2: Fix clock resource by adding a register clock Date: Sun, 11 Mar 2018 20:34:23 +0530 Message-ID: <20180311150423.GC15443@localhost> References: <20180307154010.10430-1-gregory.clement@bootlin.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20180307154010.10430-1-gregory.clement@bootlin.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Gregory CLEMENT Cc: Andrew Lunn , Jason Cooper , devicetree@vger.kernel.org, Antoine Tenart , Hanna Hawa , Omri Itach , Nadav Haklai , Rob Herring , Shadi Ammouri , Igal Liberman , Thomas Petazzoni , =?iso-8859-1?Q?Miqu=E8l?= Raynal , dmaengine@vger.kernel.org, Marcin Wojtas , linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth List-Id: devicetree@vger.kernel.org On Wed, Mar 07, 2018 at 04:40:10PM +0100, Gregory CLEMENT wrote: > On the CP110 components which are present on the Armada 7K/8K SoC we need > to explicitly enable the clock for the registers. However it is not > needed for the AP8xx component, that's why this clock is optional. > > With this patch both clock have now a name, but in order to be backward > compatible, the name of the first clock is not used. It allows to still > use this clock with a device tree using the old binding. Applied, thanks -- ~Vinod