Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp416216pxb; Fri, 16 Apr 2021 08:42:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyQvvdwY+XxGBQow+jDvHRmSem0CXrCeK3Nx+MG5LgwMZbab6sTyK7YGITd19LuoNh+RGEO X-Received: by 2002:aa7:998d:0:b029:247:74a8:e552 with SMTP id k13-20020aa7998d0000b029024774a8e552mr8217045pfh.66.1618587775909; Fri, 16 Apr 2021 08:42:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618587775; cv=none; d=google.com; s=arc-20160816; b=c9WVXXCUITtB2zXdpjgdVNxRm1e7L4wV8ne7gInqhgCVPK1xPrb1ZbFnoc1ZE1gX6B LJlEF2snZ1C8Dtxj+fTr/4Mrj93lUbSATr/wOoiz2GbXvXyviWyqbdAZAHO3NrOqEdQ+ nPVkUzfgXvShtCoCqrjZuFeW/LnBGVHA+KS7Wh3bU4Y/PeKSUJ6sHnkiq9Mo5ZB9/x1E ngSpdtTn1DdFr3QCRUBTilQv6l07o86dXIe4v5XBwuGZcoBiZnGgo9oFJ81Vp4um28+p 67zjHzN6VIeUIOj/QSiR7mzTFal5gXyQR46dLSU587L4aq+x+v1nwIEy1JB1KQYl/oCY 2Ozg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=KDk3amLs0Zl+rRoVpfXZhI0atBu/zQbhsj1RfUtselA=; b=Cc7nIt/7sLZdko+P7STaH++8ffRa41oxXH/7EilgX4MT2GSm6LrFzUioTeNWz92dnK LmCJnIl3xCl+D6n31wBO/aQ/iVUQO2+1d8l0k+GcsH236hjytOiceyaXTB/1Jmg3HxWZ JW0tnCL/0IHv23pe6fUuOT2fpVf7zHuE6vXkK3CV41kazs6rCc8YiMQATAGkaAau11JR xHxkem0lFp0rTZ4V9PoSXKpau7+e8OPHUc/g/UBlSpiFmQ75lrN0vI25qhv1mWrhFYaE TVak98sivCELGEu9Ff9ErBeMhwWCg5Zr7V9asVwS3ZtvAz6v4hSbqLEYtAXrRQaTQqVS 20Rw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lKlNd6Bb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id d15si7052369pji.84.2021.04.16.08.42.44; Fri, 16 Apr 2021 08:42:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lKlNd6Bb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S235666AbhDPNy6 (ORCPT + 99 others); Fri, 16 Apr 2021 09:54:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35564 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235478AbhDPNy5 (ORCPT ); Fri, 16 Apr 2021 09:54:57 -0400 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3CC00C061574; Fri, 16 Apr 2021 06:54:31 -0700 (PDT) Received: by mail-ej1-x632.google.com with SMTP id r9so42270665ejj.3; Fri, 16 Apr 2021 06:54:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=KDk3amLs0Zl+rRoVpfXZhI0atBu/zQbhsj1RfUtselA=; b=lKlNd6BbkPwTyNkHOTZRnX0iDbb2TgVGLzu55+YftgoNzLJSSJGaYPoyg8E0dZ8xR0 rYsnThJY3dl2H62jYsA+2E8//nx/yafkJUec1BohIIwhEhuONmNkTCM8VD/JrLX6FX7q tYD1tvwGKkV3CNzzNRWTsDtMya7adSbsx7eI4S56Wfc9WVkdiUtdUHcE3+FEIwNl8xuv MRUsygSswlXwxmDVno4FB3/rLGn3tKlibgZX6LL57aLX3WQYnwv6pV3tNgdNdAGj3gBl bwsvPdcQNwUA201LiM7ulpeb40D8T6eryJeZ7b0GMx4/Gz0V2HwOHNT4PQPAWFfZ66jQ 7jJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=KDk3amLs0Zl+rRoVpfXZhI0atBu/zQbhsj1RfUtselA=; b=OHtwKcuFxjPYgdsfI9SYQ6E5HQ39N8KYmurVWijflqUmWSgYScoW+r2fgBPW2KpDCs 2R685b5hieSEPvMrzRZ8MBRNNqA3jIWKY5e9ORHVIye9tvG4HFVzzxUp/ABDLfPTfmnt XOYMtsJnRe4b/TuNDXY2Yo+LvZ7QmFmTZS8VgQkdlLT08N0iu5zuS5iKU3H52zd3LtnH wgdzCaFYhSb4VWTKxXYJRMLbF859OAsGeod93VxS9JngTPl4Win446TASp0sGT4aPkoJ Ch8P1oJryRMnY4GqqsaM6UOpSgTBKVW2WZY+B7pxyA4x5ze8b4/3+2En0JAnehacDIBD 456A== X-Gm-Message-State: AOAM532waVK6MveGk5xadzCwjXSFV9NvFoc/stidq6kv/fCMnL8JwGzf 5nGoyNVbX/CiD8Ou0WVyNNQ= X-Received: by 2002:a17:906:85cb:: with SMTP id i11mr8075474ejy.311.1618581269965; Fri, 16 Apr 2021 06:54:29 -0700 (PDT) Received: from localhost ([62.96.65.119]) by smtp.gmail.com with ESMTPSA id c12sm5968623edx.54.2021.04.16.06.54.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 16 Apr 2021 06:54:28 -0700 (PDT) Date: Fri, 16 Apr 2021 15:55:11 +0200 From: Thierry Reding To: Rob Herring Cc: Clemens Gruber , linux-pwm@vger.kernel.org, Sven Van Asbroeck , Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v8 4/8] dt-bindings: pwm: Support new PWM_USAGE_POWER flag Message-ID: References: <20210412132745.76609-1-clemens.gruber@pqgruber.com> <20210412132745.76609-4-clemens.gruber@pqgruber.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XbFHZBPVqfivajiW" Content-Disposition: inline In-Reply-To: <20210412132745.76609-4-clemens.gruber@pqgruber.com> User-Agent: Mutt/2.0.6 (98f8cb83) (2021-03-06) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --XbFHZBPVqfivajiW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 12, 2021 at 03:27:41PM +0200, Clemens Gruber wrote: > Add the flag and corresponding documentation for PWM_USAGE_POWER. >=20 > Cc: Rob Herring > Signed-off-by: Clemens Gruber > --- > Documentation/devicetree/bindings/pwm/pwm.txt | 3 +++ > include/dt-bindings/pwm/pwm.h | 1 + > 2 files changed, 4 insertions(+) Rob, what are your thoughts on this? I've been thinking about this some more and I'm having second thoughts about putting this into device tree because it doesn't actually describe a property of the PWM hardware but rather a use-case specific hint. It's a bit of a gray area because this is just part of the PWM specifier which already has use-case specific "configuration", such as the period and the polarity. Perhaps a better place for this is within the PWM API? We could add the same information into struct pwm_state and then consumers that don't care about specifics of the signal (such as pwm-backlight) can set that flag when they request a state to be applied. Thierry --XbFHZBPVqfivajiW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAmB5lzwACgkQ3SOs138+ s6EIRBAAopZq0WA+PGKaCMBdc3iqIKquJL4ZtHYLNy7PIFmUgxNw2bn/B3IRihS1 WKd0Tvt9OYiP9vMhVKdUUm2W0How6aUWgACYAfj1O8LZU5Xa44ENeXSCkACBN6mW A+ff1QrfNZqxE9BtFPChjTKsm2ty+2ybzT9Z5RcwcmWoZn2/rioZGsx79QzuO02Y D1fk3L7jkPa7sZsqwkJOdBgSb31hgMzPSOxm3VZaJoxIxr+uIEqJVHNG5vpw/cY0 EStGp0wZc5uROb/zFFlHTi5JuAV+Mxrk/2A6vUU+IL6OwFQ3o1toTQToIW+oK1Ul 1gh/Ts3lFj3O6ALj/8n7pW6eN6JAnE0ZZo75ccWHmaNmzypPNiePA0Vit1WDklZM KtdIHdCTC0i55R90wFQNPZBhYIfk72hNUJGWjHQV5AwmjwmsXGPLY6q0qvl11kzy kzDg7CSF2E1BuIb4VGAg+fdJzsoaVQa4pbNT1TYB94eQvPZXUvJ7urNBOntKWH6T IpDp/DJd5btx+qsXLFKF3fqyEwYlpfQkZlCqhEBM8Qivwa7pMrCLp8YpsDBXGwPK 36GJAzwDQRRx2Efgugk898nZ60dCllaJyt+rMs8HpCkkb6P8OsRuXrrgEcOVLtzl MkQ1FhpXZOjiIcCh1tqcfjv/7KXCbkam1O2i7d1JSpiHbAzL/Cc= =GQic -----END PGP SIGNATURE----- --XbFHZBPVqfivajiW--