Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp8965989rwi; Tue, 25 Oct 2022 13:16:11 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4Gw03IkBNhtv6IH6WVd0WyY7v8KkUoq3hwx6lz9yizEdhLj1WqiyYsSxxalPsX5peniQ2A X-Received: by 2002:a63:814a:0:b0:460:9253:bf8e with SMTP id t71-20020a63814a000000b004609253bf8emr33515481pgd.469.1666728971209; Tue, 25 Oct 2022 13:16:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666728971; cv=none; d=google.com; s=arc-20160816; b=Mp4n5Qn9qIsvkgEFV7UTsuSPNMXOog4jeXE8LVXRFH+0HcaYdjjHMyAk7FVVqU5XUA bdzpaMO2BnuIsUOFkvfBEUV3jgXBzad63GdN1T0pgftYnYA4hKZfYJnHoftB/kjz1uh1 SiMic/a8p9Jx6ydrgSUAWSGmFPG65GGLLC18hewlWw9mgbwv9FK8057X1XSVWLQr+Eh8 +6S1oJVYhqCcjkYxfbYjL6IJ0IIHRGW+TdTWIpxAYhbsQJWLaBhEpEzPtVw4PB56l06X 1QzYzgR2iIJh7GxCW6BvxzFCK/Q2iAbsLYAtpM+n5GPLdH7UleQ4B2E/bOInsu0FDxN6 mVdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=1CDt1y7e7BIyTnclLO8/l8wF0JXVZnj5kZesVA/eyFg=; b=s/7KonCxtY9oqViDD1pMzcf6W1G8iCT6UcSz9kdAMX2CCTzMDf7Jnoqrtencs1gDKL UZD2BiNYo9n1BzhnPC8u3sJz4HRIKJcBHfxXzuVzHOoMQYDZJCyrnCcU0o04RmqviCnd QrCnS4FyKouTruLYhmiu9Wu+FKCe630WGEdGk2hMQkA/kXHx87d799Y/xRS1HRER76Sx gTDnUw64IvwdhZV4DLbUDLn01XgwpZqCSRSh0VfkIgTg8K4fcbKtEF9SYTKa+Yh1oFlk 2hegjkxVv+zDDL36vBbqSX0bBw9TR4nbirelGcQWDK9nmQJ11BCoWr9MQjRnOZ/TTeag qaIQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="K3/2yhlJ"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id oa9-20020a17090b1bc900b001fb706e96afsi16170255pjb.182.2022.10.25.13.15.56; Tue, 25 Oct 2022 13:16:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="K3/2yhlJ"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232332AbiJYUNV (ORCPT + 99 others); Tue, 25 Oct 2022 16:13:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232331AbiJYUND (ORCPT ); Tue, 25 Oct 2022 16:13:03 -0400 Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7ABBB7E03B for ; Tue, 25 Oct 2022 13:13:01 -0700 (PDT) Received: by mail-vs1-xe36.google.com with SMTP id a2so12257625vsc.13 for ; Tue, 25 Oct 2022 13:13:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=1CDt1y7e7BIyTnclLO8/l8wF0JXVZnj5kZesVA/eyFg=; b=K3/2yhlJoAiQZi9EIf9ab9ebsvLBXlapY9+VwvPvvaVRJdx5Qh7HaDiz2pbdxMyjy6 7O0o8Vn/BmDMXgzxWGyev/NBW9V/cCjmYxXMKeQtMV/TakUujFewAyvj3sGn29sXYTwy HJUaeg9EChZ2sMJxySltPYCDU+/TXDc57BhfM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1CDt1y7e7BIyTnclLO8/l8wF0JXVZnj5kZesVA/eyFg=; b=fBWq1w6l94N0ybL7uzXGnuw1SOZkfhvIFJR6SQMBauN1mIQRa6W6OPq9agjKOg390a yqOxlJELtJT10CsZn2mE+fAWfCyu11DlDx7mkajrGOa8LzMqSCkJWEXp6/QTsWf2wVg1 dmpmHSemCqvEfLgqIIgcpLS3JhXnYQ7oupN6QTPcAyLmdYaHX1qHqttK/KQGJqz2H4Ce geuTdTTdDvxDBhrFwj5r5B8FrcxLSMf5zDW9pGoJXI/Rqos8hm29c6H6Tsn7IThTzn3I d7csIKgyF6x2NlALb0rcKcP9oBzUg8F0H6PK1xQ1OPiHHkadumE/m3xSl+lWTxUQlOI+ SS3Q== X-Gm-Message-State: ACrzQf0MXY13XmxpOPTaCKmA92sHPMH9+EoBH6KIjq4sqxMem75CZNZk /5MA17avb4kET/t0Ylhv4cqHyPpy0J9VhSZr7283rQ== X-Received: by 2002:a67:f106:0:b0:3aa:efc:8610 with SMTP id n6-20020a67f106000000b003aa0efc8610mr8867914vsk.65.1666728780555; Tue, 25 Oct 2022 13:13:00 -0700 (PDT) MIME-Version: 1.0 References: <20221024220015.1759428-1-nfraprado@collabora.com> <20221024220015.1759428-3-nfraprado@collabora.com> In-Reply-To: <20221024220015.1759428-3-nfraprado@collabora.com> From: Chen-Yu Tsai Date: Tue, 25 Oct 2022 13:12:49 -0700 Message-ID: Subject: Re: [PATCH v2 2/4] ASoC: dt-bindings: realtek, rt5682s: Add AVDD and MICVDD supplies To: =?UTF-8?B?TsOtY29sYXMgRi4gUi4gQS4gUHJhZG8=?= , Krzysztof Kozlowski , Rob Herring Cc: Mark Brown , devicetree@vger.kernel.org, alsa-devel@alsa-project.org, Liam Girdwood , linux-kernel@vger.kernel.org, Derek Fang , kernel@collabora.com, AngeloGioacchino Del Regno Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 24, 2022 at 3:01 PM N=C3=ADcolas F. R. A. Prado wrote: > > The rt5682s codec can have two supplies: AVDD and MICVDD. They are The actual chip also has LDO1_IN (for digital core and charge pump) and DBVDD (for I/O). However in the Chromebook designs these two and AVDD are all provided from the same power rail, through separate filter banks. Neither does the datasheet specify the ordering of AVDD, DBVDD, and LDO1_IN for power sequencing, just that three should be toggled together. Should we model these? Or wait until some design actually splits these? ChenYu > already used by sc7180-trogdor-kingoftown.dtsi, so document them in the > binding. > > Signed-off-by: N=C3=ADcolas F. R. A. Prado > > --- > > Changes in v2: > - Added mention that property is already used in a DT to the commit > message > > Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml= b/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml > index 1c0b06d82369..ac1dea5b4450 100644 > --- a/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml > +++ b/Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml > @@ -90,6 +90,10 @@ properties: > "#sound-dai-cells": > const: 1 > > + AVDD-supply: true > + > + MICVDD-supply: true > + > additionalProperties: false > > required: > -- > 2.38.1 >