From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754379AbeEaKT6 (ORCPT ); Thu, 31 May 2018 06:19:58 -0400 Received: from fllnx210.ext.ti.com ([198.47.19.17]:44849 "EHLO fllnx210.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754207AbeEaKT4 (ORCPT ); Thu, 31 May 2018 06:19:56 -0400 Subject: Re: [PATCH v2 5/6] ARM: dts: Add generic interconnect target module node for MCAN To: Tony Lindgren CC: , , , , , , , , References: <20180530141133.3711-1-faiz_abbas@ti.com> <20180530141133.3711-6-faiz_abbas@ti.com> <20180530150402.GE5705@atomide.com> From: Faiz Abbas Message-ID: <2361da91-659d-1aaa-0ab8-d1473bc3a71a@ti.com> Date: Thu, 31 May 2018 15:51:04 +0530 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: <20180530150402.GE5705@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 Hi, On Wednesday 30 May 2018 08:34 PM, Tony Lindgren wrote: > * Faiz Abbas [180530 14:12]: >> The ti-sysc driver provides support for manipulating the idlemodes >> and interconnect level resets. > ... >> --- a/arch/arm/boot/dts/dra76x.dtsi >> +++ b/arch/arm/boot/dts/dra76x.dtsi >> @@ -11,6 +11,25 @@ >> / { >> compatible = "ti,dra762", "ti,dra7"; >> >> + ocp { >> + >> + target-module@0x42c00000 { >> + compatible = "ti,sysc-dra7-mcan"; >> + ranges = <0x0 0x42c00000 0x2000>; >> + #address-cells = <1>; >> + #size-cells = <1>; >> + reg = <0x42c01900 0x4>, >> + <0x42c01904 0x4>, >> + <0x42c01908 0x4>; >> + reg-names = "rev", "sysc", "syss"; >> + ti,sysc-mask = <(SYSC_OMAP4_SOFTRESET | >> + SYSC_DRA7_MCAN_ENAWAKEUP)>; >> + ti,syss-mask = <1>; >> + clocks = <&wkupaon_clkctrl DRA7_ADC_CLKCTRL 0>; >> + clock-names = "fck"; >> + }; >> + }; >> + >> }; > > Looks good to me except I think the reset won't do anything currently > with ti-sysc.c unless you specfify also "ti,hwmods" for the module? > > Can you please check? It might be worth adding the reset function to > ti-sysc.c for non "ti,hwmods" case and that just might remove the > need for any hwmod code for this module. > If I understand correctly, this involves adding a (*reset_module) in ti_sysc_platform_data and defining a ti_sysc_reset_module() in ti-sysc.c similar to ti_sysc_idle_module(). Right? Thanks, Faiz