From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from lelnx194.ext.ti.com ([198.47.27.80]:16099 "EHLO lelnx194.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753048AbdJMR7q (ORCPT ); Fri, 13 Oct 2017 13:59:46 -0400 Date: Fri, 13 Oct 2017 12:59:43 -0500 From: Benoit Parrot To: Tony Lindgren CC: Tero Kristo , Rob Herring , , , , Subject: Re: [Patch 3/6] ARM: OMAP: DRA7xx: Make CAM clock domain SWSUP only Message-ID: <20171013175942.GH25400@ti.com> References: <20171012192719.15193-1-bparrot@ti.com> <20171012192719.15193-4-bparrot@ti.com> <20171013170113.GL4394@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20171013170113.GL4394@atomide.com> Sender: linux-media-owner@vger.kernel.org List-ID: Tony Lindgren wrote on Fri [2017-Oct-13 10:01:13 -0700]: > * Benoit Parrot [171012 12:29]: > > HWSUP on this domain is only working when VIP1 probes. > > If only VIP2 on DRA74x or CAL on DRA72x probes the domain does > > not get enabled. This might indicates an issue in the HW Auto > > state-machine for this domain. > > > > Work around is to set the CAM domain to use SWSUP only. > > Hmm this you might get fixed automatically by configuring the > parent interconnect target module to use "ti,sysc-omap4" and > adding VIP1 and VIP2 as children to it. > > The reason why I suspect it will fix the issue is because > with the parent being "ti,sysc-omap4" with "ti,hwmods" being > in that parent node too, you automatically get PM runtime > refcounting keep the parent active for either child. > > Maybe give it a try against today's Linux next and see for > example how it was done for musb: > > https://patchwork.kernel.org/patch/9978783/ > > Just use "ti,sysc-omap2" for type1 and "ti,sysc-omap4" > for type2. Hmm interesting, I'll give that a try and if it fixes it. Benoit > > Regards, > > Tony