Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp119751rwb; Wed, 18 Jan 2023 15:05:49 -0800 (PST) X-Google-Smtp-Source: AMrXdXut2/uSYmUWbt42emkkplzFihq1Bp8i0s+CZdoPIpnHGYBK2XAgdb+OChtUCRSoAQM4+CoM X-Received: by 2002:a17:90a:4e4c:b0:228:cf57:32c1 with SMTP id t12-20020a17090a4e4c00b00228cf5732c1mr9470073pjl.0.1674083149721; Wed, 18 Jan 2023 15:05:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674083149; cv=none; d=google.com; s=arc-20160816; b=g/YrWJQWSTWZCbN0U+mBXs6l4xp0C3wVf4UYf3Qp9B2gSsDcpgA7KR5F4ZiREVJLRN d2It27rGTRl9Gvj1Jo/AtsC5aD9YRsj44UHku+cieR4ricAyhNtAti2FwMrBfgg76B3M v3iBeRwqVZHpjURxcFiBS7VFOZHSdTe+l34wbTGl/WicU7N/oaXiKpCN2Nbfm6WEsYu5 3Yl88h/BdQkNkaPFcvmrQIm97mmzT+4aShh0DcWtL7zrrvUnb4o19QPO9sNdJhg5As8k WkWtPXJpNxFwM6xxFiGvV9rgJ0mFkZOrNYyK8Ta7oNAMNXA8z0acvw5SLALA1E9KkabN p3Ng== 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=uJRlUJgto8uB5cGkRdE7zVVbQyEtoN07TyJzGKXUrGM=; b=ddb5QKWrbv7uo6ANxSk/+7F//X5bIlZP0XVBWeg1v6tOl8tih7q3rpgf6ymNL58bnn Lrnnzg9H5UW2vU08MR8lo/1eyncAzGArVs73e1IGbnlb7CAN3KP/hN7X4/5hIMCozNSu 8UvvyDkB15qsgI/b1Jd26t6tX5/Tvum545ekykJpuiGsDj/uaRVqUpr9Jut15ZEGitIy kE/moEKjyMhy+vqU//v66QIVmCPumj0GdhlmJA4P1b64Fn3LVNcgLCi7DET7JJ3RGLfM nCKmbDHxuV7/2xOZnNBbsKfR3OocD1DH3dogGSLclgv7bUy8yQCw8ZfA79c/aqoPQGsA abxw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=cOiYLD26; 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=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 39-20020a17090a0faa00b00212e2e1b626si3283472pjz.164.2023.01.18.15.05.44; Wed, 18 Jan 2023 15:05:49 -0800 (PST) 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=@linaro.org header.s=google header.b=cOiYLD26; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229770AbjARWZo (ORCPT + 46 others); Wed, 18 Jan 2023 17:25:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229446AbjARWZm (ORCPT ); Wed, 18 Jan 2023 17:25:42 -0500 Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0059863081 for ; Wed, 18 Jan 2023 14:25:39 -0800 (PST) Received: by mail-yb1-xb34.google.com with SMTP id p188so301216yba.5 for ; Wed, 18 Jan 2023 14:25:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.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=uJRlUJgto8uB5cGkRdE7zVVbQyEtoN07TyJzGKXUrGM=; b=cOiYLD26GMRo0sNZd8nju2ANkQ+n3qs8Xjf5D7XTwBgaPEvmZz9M1Z27xdRO85T2FM xExT7Rjf7Y6CNd8+OAZrG6hsCG8G+r+uQZx/eAXNCCaYYfC1z+pp99Ld0GcOx+rlL3ve TzfoVnhIYEHpZwVXwdbdWcuFLOeJUWSWTHdULy/DKVTs30/a4k+cZFX/EIdVAOik7NfT 581mEfAXBvXkZm66DT0dp2web4Si4t34BPfC1T6H/p5xSYTAYQS6+uZXKY7okji3z55v kj2sBaQcK9Rd/aSl2v98RAzHqUQ5rx2TAeo+1Arm1Hp5LAxaygH/kQyKZjfUSz+lhHjl QWjQ== 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=uJRlUJgto8uB5cGkRdE7zVVbQyEtoN07TyJzGKXUrGM=; b=DrfiE/gH99KiqmJvQhvo+67+SO3IKlHzkdFEl4Qy2f8bsT3ET5pB4ttL+EeZwcVaKV YwW1Z3/VvZO5xqTrDYYKY4z+4r/aPQZDuqxpYTk5oenwmh6jBBjsdLKo6q5bPG0T2zWW BzaO2jEFF5zTrc70pCYzfHg311UqGG8k5ddz5txhp2Zkz999+EkDK3gwB8R1cnVHZpD+ egFnnTuKVp2uBh6oirMm70bqb3Vi9TWlNlgRNlp7JojlPPyqFji1rmnK/v9MdHGCC/wl kFQExzk+8lqQDvzq5Kmq46vG5Z6M6WCjRGaWwQIwloti6wb23toi+BihyuxTpFmnNfWR XCoA== X-Gm-Message-State: AFqh2kq5qwJTN296FILb/Cyndh+Oj7zSSoUNmEpMXuuWMIDm4Lypszrd rYjm7Glr4muzsltq2dmw8dPN5B6emEkg8B3VLUTAqw== X-Received: by 2002:a25:8746:0:b0:70b:87d5:4a73 with SMTP id e6-20020a258746000000b0070b87d54a73mr772093ybn.584.1674080739210; Wed, 18 Jan 2023 14:25:39 -0800 (PST) MIME-Version: 1.0 References: <20230118154817.97364-1-u.kleine-koenig@pengutronix.de> In-Reply-To: <20230118154817.97364-1-u.kleine-koenig@pengutronix.de> From: Linus Walleij Date: Wed, 18 Jan 2023 23:25:28 +0100 Message-ID: Subject: Re: [PATCH 0/2] pwm: ab8500: Fix .apply() and implement .get_state() To: =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= Cc: Thierry Reding , linux-pwm@vger.kernel.org, kernel@pengutronix.de, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham 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 Hi Uwe, On Wed, Jan 18, 2023 at 4:48 PM Uwe Kleine-K=C3=B6nig wrote: > during review of my previous pwm-ab8500 patch I learned that there is a > (somewhat) publically available reference manual. Reading in it showed > that .apply() is still more broken that I assumed by just reading the > code. > > This series first fixes .apply() to not be off by a factor of ~3000 and > then adds a .get_state() callback. > > Note this is only compile tested as I don't have the hardware. > Also note this breaks all consumers that relied on the previously broken > behaviour. I looked over the patch and I can't find anything to comment on it just seems well researched and correct so: Reviewed-by: Linus Walleij Yours, Linus Walleij