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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EB651C4167B for ; Wed, 29 Nov 2023 09:08:56 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 4440710E1A1; Wed, 29 Nov 2023 09:08:56 +0000 (UTC) Received: from gofer.mess.org (gofer.mess.org [88.97.38.141]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0D9F610E18D; Wed, 29 Nov 2023 09:08:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mess.org; s=2020; t=1701248932; bh=Xv3LVDjykwD/IOkFuRPxIVNxFelutLAZSXS7jeSQqIE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=BAZ/6qGNguReQ4NFwPXT8Bi2uaQNZ0Q93gRgXJPFRYxINiE+0NAHwqYEo8gcRktTI g5OWo09C5jJHok3S1c3vfX72MgTtnOlRCfK/TqM9Rhw5IHY9zlrMU0Lm6ESMeYefR5 o0o+IWUBwaImm3Ew7Uz5W7jNB5PpjVR/Xzp9G3VEMAH3MPFJnFwTN5A/JF0jvSM53H TD72MGqWdop+SC6I4X83nrxxAJKPcPymeSSvEn8ptLrmEICedV7+oDpdhH/aFgVPau +Aaz/bRn6yA421udzBxvVtiTPtc21WHM3jUynkqXosp+xZ5HbIh4FPd2hzKqYs08uU fPTAj/lk7FXSA== Received: by gofer.mess.org (Postfix, from userid 1000) id CB5B0100100; Wed, 29 Nov 2023 09:08:52 +0000 (GMT) Date: Wed, 29 Nov 2023 09:08:52 +0000 From: Sean Young To: Thierry Reding Message-ID: References: <2b973840d800ffb71c2683c37bc996e0cf90a140.1700323916.git.sean@mess.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Intel-gfx] [PATCH v5 1/4] pwm: rename pwm_apply_state() to pwm_apply_cansleep() X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-fbdev@vger.kernel.org, linux-doc@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Pavel Machek , David Airlie , linux-leds@vger.kernel.org, Daniel Thompson , Ivaylo Dimitrov , Jonathan Corbet , Helge Deller , Lee Jones , Javier Martinez Canillas , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , Ilpo =?iso-8859-1?Q?J=E4rvinen?= , Guenter Roeck , linux-media@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-pwm@vger.kernel.org, Jean Delvare , Daniel Vetter , Jani Nikula , intel-gfx@lists.freedesktop.org, linux-input@vger.kernel.org, Mark Gross , Hans de Goede , Mark Brown , Maxime Ripard , Rodrigo Vivi , Mauro Carvalho Chehab , linux-arm-kernel@lists.infradead.org, linux-hwmon@vger.kernel.org, Support Opensource , Jingoo Han , Dmitry Torokhov , Liam Girdwood , Thomas Zimmermann Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Fri, Nov 24, 2023 at 02:31:18PM +0100, Thierry Reding wrote: > On Sat, Nov 18, 2023 at 04:16:17PM +0000, Sean Young wrote: > > In order to introduce a pwm api which can be used from atomic context, > > we will need two functions for applying pwm changes: > > > > int pwm_apply_cansleep(struct pwm *, struct pwm_state *); > > int pwm_apply_atomic(struct pwm *, struct pwm_state *); > > > > This commit just deals with renaming pwm_apply_state(), a following > > commit will introduce the pwm_apply_atomic() function. > > Sorry, I still don't agree with that _cansleep suffix. I think it's the > wrong terminology. Just because something can sleep doesn't mean that it > ever will. "Might sleep" is much more accurate because it says exactly > what might happen and indicates what we're guarding against. Sorry, I forgot about this in the last round. I've renamed it _might_sleep in v6 which I'll post shortly. Sean