Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp8195954ybi; Tue, 23 Jul 2019 04:30:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqyFyXOEONH15BLVym62Zd1GdxRPVzrlwU47jlBjJ7VC9kVpjE7eNJ0ioAWZVB5mBqRacb+8 X-Received: by 2002:aa7:9a8a:: with SMTP id w10mr5285693pfi.66.1563881405533; Tue, 23 Jul 2019 04:30:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563881405; cv=none; d=google.com; s=arc-20160816; b=y8DxBm83TQ9oQRGHZKpzAiED5xO4+AGcBxYj+St4HxznEgDcpmvE48dTZKwATrq3tx g/+RguO6Qv3bLyVVIG3qE8/2TH9tmRoukOpgt24+PkbEsqH9lJv60oX2pJGqAiXGKAQC duAfJMV0gAF8yGgxj6CnkuNWafNcIUWuK7Wh6F0bEjOZEpBySyOG1x8pgHCj/uNdrnG5 viXwfLcaBSvsQMLttRD4JqYuILvY2rvHKt0SJawD/PE8t4kdE91lGPY3qyJxybq/fVAU 7iZeOPL76NV6h7DcDv59UjsjA42LtgVQZEpaFTSE5giQoBY1AuXJ95klDWTxp2r0qAaE Jl+w== 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:references:cc:to:from:subject:dkim-signature; bh=iXecZHhC/EqaFk3SuaI94lJ9SQId4NXdMqEs66WG+tI=; b=IJkZlawdXNLcKdXDmsRkCn9Ib7h4UmjGlUmJWsHGIrkl+0wy/+jw5UzAT2Magx7YOd nblh1uuRcBjppoSsQaAAGAfjXc45bXI9nZ3UyJjO6ybNugp/Nh04IHqZsSlAE5VUz6QD IX2rX7BKRPKenQP75XQd0GSu7rK+7M9Y59DVcsNH+bCREaeWSvIaacTY0eaPKf/cFJep HzovRjIjFc/YlOnKF4gykGPjesg+9W67diq9MbfN85INmimDR3J6lxdN44FOOcoU1cWB QMIvx/hv5hFqUhj9ooCzvsaKpUB5og18CNTafLnp0ieocpDlX9tU1Ez5L92A6gtAHFxf lJGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=nsZq3YeG; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v4si10571963plp.212.2019.07.23.04.29.49; Tue, 23 Jul 2019 04:30:05 -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=@gmail.com header.s=20161025 header.b=nsZq3YeG; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387682AbfGWBIX (ORCPT + 99 others); Mon, 22 Jul 2019 21:08:23 -0400 Received: from mail-lj1-f195.google.com ([209.85.208.195]:46022 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731384AbfGWBIX (ORCPT ); Mon, 22 Jul 2019 21:08:23 -0400 Received: by mail-lj1-f195.google.com with SMTP id m23so39294857lje.12; Mon, 22 Jul 2019 18:08:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=iXecZHhC/EqaFk3SuaI94lJ9SQId4NXdMqEs66WG+tI=; b=nsZq3YeGylIk6fKPnJyklhiLr9PpiuM+mKBhC9jyY1wNK4xfjXKe2uhtZ5DGR1u1WQ gYJNhUlpQMKFuxvSQnb89Sk6ckQQs5lY3Q5qhEDdK3owjRcGlgV9klf+G99MDnN3ZCXJ bP4hya3i84wNp/GBy+NXwAaexmIt4PH9lV9kh4OC5rngDa42FFyIJU1sjkdoGRs46nF1 e3faJgBb6F4I8MsnOvj4/El3tGI9elHxUm9Tk5tqZwP7a+wFS/nwOQoFUfEEH/ZUfg6K qH+3cnEO7el2ooYYyXOJEVm7K/7lMAjbdnslUIAYR9CNmukrgOqvmPtWSZ8LVTSg2OOr lKNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iXecZHhC/EqaFk3SuaI94lJ9SQId4NXdMqEs66WG+tI=; b=nTpEUmFdGNEzeV5MxMo9uK1OoarDpqPYQ9+Y3lSfTAhP+4cdUbJEdVRlCEu2PFyoHw obhPUbZrIAi710LhB3Rum9fh00hizUmx00nqlYwoJ2nZSSptcPOlmmCHDnknwOpQ0s4d 6ehbMn3x1RGkHZbSAz7UGlZrNX8E1HEkM5grO7N90V+dbYrUWY9WP520OXLYzaxNAdjP LOpAAyQK4/UeCAoOANWDcnq8/Hva/coIgpxEJEfH/gn+2hlkEbvrtfmtXH4Nt9K7VULo AYbQ2g4dXZ39VxrpAdreNRpu0gzU7OAB/d7JLi/fGOP2O9u7Bawphy9KyfATif0bkjYg UbcA== X-Gm-Message-State: APjAAAWHyAC/h0ERml1ivRhT75kseJHJ90lOjTW1ip+NWp/C28eav7aZ twzlvIcUDMT8XkXncSoQXOgI5Oxb X-Received: by 2002:a2e:9d8a:: with SMTP id c10mr14110238ljj.147.1563844099142; Mon, 22 Jul 2019 18:08:19 -0700 (PDT) Received: from [192.168.2.145] (ppp91-78-220-99.pppoe.mtu-net.ru. [91.78.220.99]) by smtp.googlemail.com with ESMTPSA id y15sm6221587lfg.43.2019.07.22.18.08.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jul 2019 18:08:18 -0700 (PDT) Subject: Re: [PATCH V6 16/21] soc/tegra: pmc: Add pmc wake support for tegra210 From: Dmitry Osipenko To: Sowjanya Komatineni , thierry.reding@gmail.com, jonathanh@nvidia.com, tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com, linus.walleij@linaro.org, stefan@agner.ch, mark.rutland@arm.com Cc: pdeschrijver@nvidia.com, pgaikwad@nvidia.com, sboyd@kernel.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, jckuo@nvidia.com, josephl@nvidia.com, talho@nvidia.com, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, mperttunen@nvidia.com, spatra@nvidia.com, robh+dt@kernel.org, devicetree@vger.kernel.org References: <1563738060-30213-1-git-send-email-skomatineni@nvidia.com> <1563738060-30213-17-git-send-email-skomatineni@nvidia.com> <0b3d08ea-4633-8a54-ba66-c3f3146a1ece@gmail.com> Message-ID: Date: Tue, 23 Jul 2019 04:08:17 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <0b3d08ea-4633-8a54-ba66-c3f3146a1ece@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 23.07.2019 3:58, Dmitry Osipenko пишет: > 21.07.2019 22:40, Sowjanya Komatineni пишет: >> This patch implements PMC wakeup sequence for Tegra210 and defines >> common used RTC alarm wake event. >> >> Signed-off-by: Sowjanya Komatineni >> --- >> drivers/soc/tegra/pmc.c | 111 ++++++++++++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 111 insertions(+) >> >> diff --git a/drivers/soc/tegra/pmc.c b/drivers/soc/tegra/pmc.c >> index 91c84d0e66ae..c556f38874e1 100644 >> --- a/drivers/soc/tegra/pmc.c >> +++ b/drivers/soc/tegra/pmc.c >> @@ -57,6 +57,12 @@ >> #define PMC_CNTRL_SYSCLK_OE BIT(11) /* system clock enable */ >> #define PMC_CNTRL_SYSCLK_POLARITY BIT(10) /* sys clk polarity */ >> #define PMC_CNTRL_MAIN_RST BIT(4) >> +#define PMC_CNTRL_LATCH_WAKEUPS BIT(5) Please follow the TRM's bits naming. PMC_CNTRL_LATCHWAKE_EN >> +#define PMC_WAKE_MASK 0x0c >> +#define PMC_WAKE_LEVEL 0x10 >> +#define PMC_WAKE_STATUS 0x14 >> +#define PMC_SW_WAKE_STATUS 0x18 >> >> #define DPD_SAMPLE 0x020 >> #define DPD_SAMPLE_ENABLE BIT(0) >> @@ -87,6 +93,11 @@ >> >> #define PMC_SCRATCH41 0x140 >> >> +#define PMC_WAKE2_MASK 0x160 >> +#define PMC_WAKE2_LEVEL 0x164 >> +#define PMC_WAKE2_STATUS 0x168 >> +#define PMC_SW_WAKE2_STATUS 0x16c >> + >> #define PMC_SENSOR_CTRL 0x1b0 >> #define PMC_SENSOR_CTRL_SCRATCH_WRITE BIT(2) >> #define PMC_SENSOR_CTRL_ENABLE_RST BIT(1) >> @@ -1922,6 +1933,55 @@ static const struct irq_domain_ops tegra_pmc_irq_domain_ops = { >> .alloc = tegra_pmc_irq_alloc, >> }; >> >> +static int tegra210_pmc_irq_set_wake(struct irq_data *data, unsigned int on) >> +{ >> + struct tegra_pmc *pmc = irq_data_get_irq_chip_data(data); >> + unsigned int offset, bit; >> + u32 value; >> + >> + if (data->hwirq == ULONG_MAX) >> + return 0; >> + >> + offset = data->hwirq / 32; >> + bit = data->hwirq % 32; >> + >> + /* >> + * Latch wakeups to SW_WAKE_STATUS register to capture events >> + * that would not make it into wakeup event register during LP0 exit. >> + */ >> + value = tegra_pmc_readl(pmc, PMC_CNTRL); >> + value |= PMC_CNTRL_LATCH_WAKEUPS; >> + tegra_pmc_writel(pmc, value, PMC_CNTRL); >> + udelay(120); > > Why it takes so much time to latch the values? Shouldn't some status-bit > be polled for the completion of latching? > > Is this register-write really getting buffered in the PMC? > >> + value &= ~PMC_CNTRL_LATCH_WAKEUPS; >> + tegra_pmc_writel(pmc, value, PMC_CNTRL); >> + udelay(120); > > 120 usecs to remove latching, really? > >> + tegra_pmc_writel(pmc, 0, PMC_SW_WAKE_STATUS); >> + tegra_pmc_writel(pmc, 0, PMC_SW_WAKE2_STATUS); >> + >> + tegra_pmc_writel(pmc, 0, PMC_WAKE_STATUS); >> + tegra_pmc_writel(pmc, 0, PMC_WAKE2_STATUS); >> + >> + /* enable PMC wake */ >> + if (data->hwirq >= 32) >> + offset = PMC_WAKE2_MASK; >> + else >> + offset = PMC_WAKE_MASK; >> + >> + value = tegra_pmc_readl(pmc, offset); >> + >> + if (on) >> + value |= 1 << bit; >> + else >> + value &= ~(1 << bit); >> + >> + tegra_pmc_writel(pmc, value, offset); > > Why the latching is done *before* writing into the WAKE registers? What > it is latching then? I'm looking at the TRM doc and it says that latching should be done *after* writing to the WAKE_MASK / LEVEL registers. Secondly it says that it's enough to do: value = tegra_pmc_readl(pmc, PMC_CNTRL); value |= PMC_CNTRL_LATCH_WAKEUPS; tegra_pmc_writel(pmc, value, PMC_CNTRL); in order to latch. There is no need for the delay and to remove the "LATCHWAKE_EN" bit, it should be a oneshot action. >> + return 0; >> +} >> + >> static int tegra186_pmc_irq_set_wake(struct irq_data *data, unsigned int on) >> { >> struct tegra_pmc *pmc = irq_data_get_irq_chip_data(data); >> @@ -1954,6 +2014,49 @@ static int tegra186_pmc_irq_set_wake(struct irq_data *data, unsigned int on) >> return 0; >> } >> >> +static int tegra210_pmc_irq_set_type(struct irq_data *data, unsigned int type) >> +{ >> + struct tegra_pmc *pmc = irq_data_get_irq_chip_data(data); >> + unsigned int offset, bit; >> + u32 value; >> + >> + if (data->hwirq == ULONG_MAX) >> + return 0; >> + >> + offset = data->hwirq / 32; >> + bit = data->hwirq % 32; >> + >> + if (data->hwirq >= 32) >> + offset = PMC_WAKE2_LEVEL; >> + else >> + offset = PMC_WAKE_LEVEL; >> + >> + value = tegra_pmc_readl(pmc, offset); >> + >> + switch (type) { >> + case IRQ_TYPE_EDGE_RISING: >> + case IRQ_TYPE_LEVEL_HIGH: >> + value |= 1 << bit; >> + break; >> + >> + case IRQ_TYPE_EDGE_FALLING: >> + case IRQ_TYPE_LEVEL_LOW: >> + value &= ~(1 << bit); >> + break; >> + >> + case IRQ_TYPE_EDGE_RISING | IRQ_TYPE_EDGE_FALLING: >> + value ^= 1 << bit; >> + break; >> + >> + default: >> + return -EINVAL; >> + } >> + >> + tegra_pmc_writel(pmc, value, offset); > > Shouldn't the WAKE_LEVEL be latched as well? > >> + return 0; >> +} >> + >> static int tegra186_pmc_irq_set_type(struct irq_data *data, unsigned int type) >> { >> struct tegra_pmc *pmc = irq_data_get_irq_chip_data(data); >> @@ -2540,6 +2643,10 @@ static const struct pinctrl_pin_desc tegra210_pin_descs[] = { >> TEGRA210_IO_PAD_TABLE(TEGRA_IO_PIN_DESC) >> }; >> >> +static const struct tegra_wake_event tegra210_wake_events[] = { >> + TEGRA_WAKE_IRQ("rtc", 16, 2), >> +}; >> + >> static const struct tegra_pmc_soc tegra210_pmc_soc = { >> .num_powergates = ARRAY_SIZE(tegra210_powergates), >> .powergates = tegra210_powergates, >> @@ -2557,10 +2664,14 @@ static const struct tegra_pmc_soc tegra210_pmc_soc = { >> .regs = &tegra20_pmc_regs, >> .init = tegra20_pmc_init, >> .setup_irq_polarity = tegra20_pmc_setup_irq_polarity, >> + .irq_set_wake = tegra210_pmc_irq_set_wake, >> + .irq_set_type = tegra210_pmc_irq_set_type, >> .reset_sources = tegra210_reset_sources, >> .num_reset_sources = ARRAY_SIZE(tegra210_reset_sources), >> .reset_levels = NULL, >> .num_reset_levels = 0, >> + .num_wake_events = ARRAY_SIZE(tegra210_wake_events), >> + .wake_events = tegra210_wake_events, >> }; >> >> #define TEGRA186_IO_PAD_TABLE(_pad) \ >> >