Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3678390imm; Sun, 10 Jun 2018 23:08:14 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKV2Um+5iBeUWr0MNwH4xv5PUziTjIgmSB1WFN7NomrirXO/Wl9pKGJuNKFGWfz99m72wLD X-Received: by 2002:a63:be4f:: with SMTP id g15-v6mr13840312pgo.115.1528697294134; Sun, 10 Jun 2018 23:08:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528697294; cv=none; d=google.com; s=arc-20160816; b=ZIMb5BBh06cr3cOtWUf2/3wbx1G+d75KDtKmupVOts3hrhbWa6lVTZKwEbnAVvQLr5 SrvrCsZAANqUss1dp0obIWEsB/oDK5504xSOAYJEmeSUZfZYa9k55ZYXIkLJDeQsIRqd SUKTTfvf85TjQrzJhTeVmBW0hSzVbP9ziUnKgfeWa/1ycD9w7nlJunsw9HP/D0J+rWU6 yUZVGtYr2BwaZZmPpQ3ZfuLdnVdbrx7KWmFylsrxmbD49CHC7EbIn0gPIltEQzHorrsV 4XiT4zk1VjhmbePuKGywxI2b2540ADIzCkL7Bzz98YEdBcp0F9P0HpxLkUoxuq4v32LY 4RVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=4Wi59mS72tNTUlJrSNPQqpOfK5Tm183MIXrc6ctymLQ=; b=bNtnKZvZ4yhlfqWmhPTo7Nzffw4BqZMEklksnYwsEd4DROi8DF+6EA+HOYmd2U28nO rwvAJUdbxvYPnAPHTHDVgtyueHB6dW7SOGSdpEiBLQAyOCPEpxS13dWeEvRh9/PnB3D8 0hAOjT6M21FtuNGIpS43ElgTbrMqiJ2JqlY1yBRdC6RMP84vBgbHXZ3A0YyydXXVcvyC 9XlR6CRN3FQOHBfezLhsgIUVdUmtBnWe6rXZPAGdVaAIe9k23VztQp3IXUOs8a/maFI0 66GRlDXe6GVYRN8YXoHJlPfI5wiSw+tqLSI8OnOa0TZX8SoWVh7bTqpfwOvj+WOA2a5g qsnQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=zP0T5dux; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s204-v6si17074706pgs.280.2018.06.10.23.07.59; Sun, 10 Jun 2018 23:08:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=zP0T5dux; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753983AbeFKGHe (ORCPT + 99 others); Mon, 11 Jun 2018 02:07:34 -0400 Received: from fllnx210.ext.ti.com ([198.47.19.17]:20695 "EHLO fllnx210.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753899AbeFKGHc (ORCPT ); Mon, 11 Jun 2018 02:07:32 -0400 Received: from dlelxv90.itg.ti.com ([172.17.2.17]) by fllnx210.ext.ti.com (8.15.1/8.15.1) with ESMTP id w5B677wu022275; Mon, 11 Jun 2018 01:07:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1528697227; bh=4Wi59mS72tNTUlJrSNPQqpOfK5Tm183MIXrc6ctymLQ=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=zP0T5duxQm9uBL+JDQ5FdXnUUDiiBb45I8r+HgbzI5feIT4qz9kJB62qYml7vPt9G +E1R29PqRDc3zn3NOkLfLnNfXBgLoKJPpyFzBwHbhAG31Z5Am/SF3Sc9UFgs/QK5ry J2v5Q2153EWnDUfAzk8AvrM45uqyK8Q27NFxn32I= Received: from DFLE102.ent.ti.com (dfle102.ent.ti.com [10.64.6.23]) by dlelxv90.itg.ti.com (8.14.3/8.13.8) with ESMTP id w5B677l7025518; Mon, 11 Jun 2018 01:07:07 -0500 Received: from DFLE101.ent.ti.com (10.64.6.22) by DFLE102.ent.ti.com (10.64.6.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 11 Jun 2018 01:07:06 -0500 Received: from dflp33.itg.ti.com (10.64.6.16) by DFLE101.ent.ti.com (10.64.6.22) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1466.3 via Frontend Transport; Mon, 11 Jun 2018 01:07:06 -0500 Received: from [172.24.190.215] (ileax41-snat.itg.ti.com [10.172.224.153]) by dflp33.itg.ti.com (8.14.3/8.13.8) with ESMTP id w5B673AN013871; Mon, 11 Jun 2018 01:07:03 -0500 Subject: Re: [PATCH v3 4/6] bus: ti-sysc: Add support for software reset To: Tony Lindgren CC: , , , , , , , , , References: <20180606060826.14671-1-faiz_abbas@ti.com> <20180606060826.14671-5-faiz_abbas@ti.com> <20180607073530.GH5738@atomide.com> <20180608062158.GI5738@atomide.com> From: Faiz Abbas Message-ID: Date: Mon, 11 Jun 2018 11:38:44 +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: <20180608062158.GI5738@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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tony, On Friday 08 June 2018 11:51 AM, Tony Lindgren wrote: > * Faiz Abbas [180607 10:24]: >> Hi, >> >> On Thursday 07 June 2018 01:05 PM, Tony Lindgren wrote: >>> * Faiz Abbas [180606 06:14]: >>>> +static int sysc_reset(struct sysc *ddata) >>>> +{ >>>> + int offset = ddata->offsets[SYSC_SYSCONFIG]; >>>> + int val = sysc_read(ddata, offset); >>>> + >>>> + val |= (0x1 << ddata->cap->regbits->srst_shift); >>>> + sysc_write(ddata, offset, val); >>>> + >>>> + /* Poll on reset status */ >>>> + if (ddata->cfg.quirks & SYSC_QUIRK_RESET_STATUS) { >>>> + offset = ddata->offsets[SYSC_SYSSTATUS]; >>>> + >>>> + return readl_poll_timeout(ddata->module_va + offset, val, >>>> + (val & ddata->cfg.syss_mask) == 0x0, >>>> + 100, MAX_MODULE_SOFTRESET_WAIT); >>>> + } >>>> + >>>> + return 0; >>>> +} >>> >>> I wonder if we should also add SYSS_QUIRK_RESET_STATUS in >>> addition to SYSC_QUIRK_RESET status to make it easy to >>> read the right register? >> >> I assumed SYSC_QUIRK is the prefix to indicate the ti-sysc driver not >> the register. Are there layouts in which the reset status bit is in the >> sysconfig register rather than the sysstatus register? > > Yes we can have reset status bit in either syss or syssconfig register. You mean sysstatus and sysconfig right? > We detect that in sysc_init_syss_mask() but we should also set something > at that point to make it clear which reset to use. But as we don't need > the quirk flag, it's probably set a function pointer after the detection. > So how about let's have two functions sysc_reset() and sysc_syss_reset() > and then we can implement sysc_syss_reset() in a separate patch after > testing it when we have a non-platform data using example for > sysc_syss_reset(). > Shouldn't the function I add be called sysc_syss_reset()? The reset status bit is in the sysstatus. Thanks, Faiz