From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AE4E9C433FE for ; Thu, 13 Oct 2022 19:50:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229863AbiJMTuZ (ORCPT ); Thu, 13 Oct 2022 15:50:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33764 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229821AbiJMTuW (ORCPT ); Thu, 13 Oct 2022 15:50:22 -0400 Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A497960CBB for ; Thu, 13 Oct 2022 12:50:17 -0700 (PDT) Received: by mail-il1-x132.google.com with SMTP id 8so1524035ilj.4 for ; Thu, 13 Oct 2022 12:50:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=WJtUgMyknP4m6ys7U3PstctWgnf/qk6Z7L91/ntX78Y=; b=WwkyeeUjwcHXf2Vy1OXp7GfUN1jTId+7Svgh+SNa0GwV2l4+49ATkI9Y+pXz3w4dZZ bKI1zGvMjRq0Hu9tRXndWR2X84VisTSzl32ySRyuVa5936+YEcBi7pcTvYyVOMa0PAo3 PGBGwYeWRwafPuJGf8JxofTX1gUQENo4G/MYI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=WJtUgMyknP4m6ys7U3PstctWgnf/qk6Z7L91/ntX78Y=; b=Jr8DcTrY3V6R4wHXbklxYgz7GdRGigFIdvl3mmpWp3PmdjD/lS2oi+wrM0GnZA36mn jmjYtFjE5ymYpSO+zyd1pghyjkfi+fPR1Oq3tinz3uRPuNFxihPf81cVZA3f1xGg8482 Oc/WlKi9GdhNhKFdMQtIXydABVNxxSl1PFDSFpz8HEZoxmN+O1Jrk7RbCyUXXsYdwyLo 9AdqwkLFH3jVzHRWARgn06Ph+JGsstOnTwQcKcS8bPXmP3BufO2ISCDa9ZVpWZUqJHvr dz4IBJtBTL+W4hQZuhilOTtz3Wih0fUdVV0vmB81zB1zDhVC4GOcPcfBmC4dt00mLMTZ u9TA== X-Gm-Message-State: ACrzQf3DUwRBiRGui9PnEhMKyBuy95zz0GsGhS82V+2YJX6nx/xo6Gpv HUaGQiT3VGHfk2RfbaOJXJLINQ== X-Google-Smtp-Source: AMsMyM7lvMIch7u+CSSvr4aiO2Kb9grrpoWlHGADoAvjJtjDhqNPId/axnO4uvfzhHRdAFDnCZvtVw== X-Received: by 2002:a05:6e02:1bc4:b0:2fc:2d47:9abf with SMTP id x4-20020a056e021bc400b002fc2d479abfmr809263ilv.246.1665690617052; Thu, 13 Oct 2022 12:50:17 -0700 (PDT) Received: from localhost (30.23.70.34.bc.googleusercontent.com. [34.70.23.30]) by smtp.gmail.com with UTF8SMTPSA id q27-20020a02b05b000000b00363c852c779sm308754jah.61.2022.10.13.12.50.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Oct 2022 12:50:16 -0700 (PDT) Date: Thu, 13 Oct 2022 19:50:13 +0000 From: Matthias Kaehlcke To: Dmitry Baryshkov Cc: Andy Gross , Bjorn Andersson , Ulf Hansson , Marcel Holtmann , Johan Hedberg , Luiz Augusto von Dentz , Kalle Valo , "David S. Miller" , Jakub Kicinski , Stanimir Varbanov , linux-arm-msm@vger.kernel.org, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org, ath10k@lists.infradead.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH v1 00/15] create power sequencing subsystem Message-ID: References: <20211006035407.1147909-1-dmitry.baryshkov@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20211006035407.1147909-1-dmitry.baryshkov@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Hi Dmitry, Do you still plan to refresh this series? I know there have been multiple attempts to get something similar landed in the past 10 year or so. Your series didn't seem to get much pushback from maintainers, might be worth sending a refresh :) Thanks Matthias On Wed, Oct 06, 2021 at 06:53:52AM +0300, Dmitry Baryshkov wrote: > This is a proposed power sequencer subsystem. This is a > generification of the MMC pwrseq code. The subsystem tries to abstract > the idea of complex power-up/power-down/reset of the devices. > > The primary set of devices that promted me to create this patchset is > the Qualcomm BT+WiFi family of chips. They reside on serial+platform > or serial + SDIO interfaces (older generations) or on serial+PCIe (newer > generations). They require a set of external voltage regulators to be > powered on and (some of them) have separate WiFi and Bluetooth enable > GPIOs. > > The major drawback for now is the lack of proper PCIe integration > At this moment support for PCIe is hacked up to be able to test the > PCIe part of qca6390. Proper PCIe support would require automatically > powering up the devices before the scan basing on the proper device > structure in the device tree. This two last patches are noted as WIP and > are included into the patchset for the purpose of testing WiFi on newer > chips (like qca6390/qca6391). > > Changes since RFC v2: > - Add documentation for the pwrseq code. Document data structures, > macros and exported functions. > - Export of_pwrseq_xlate_onecell() > - Add separate pwrseq_set_drvdata() function to follow the typical API > design > - Remove pwrseq_get_optional()/devm_pwrseq_get_optional() > - Moved code to handle old mmc-pwrseq binding to the MMC patch > - Split of_pwrseq_xlate_onecell() support to a separate patch > > Changes since RFC v1: > - Provider pwrseq fallback support > - Implement fallback support in pwrseq_qca. > - Mmove susclk handling to pwrseq_qca. > - Significantly simplify hci_qca.c changes, by dropping all legacy > code. Now hci_qca uses only pwrseq calls to power up/down bluetooth > parts of the chip. > > > > > _______________________________________________ > ath10k mailing list > ath10k@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/ath10k