From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S970365AbdDTPHl (ORCPT ); Thu, 20 Apr 2017 11:07:41 -0400 Received: from mail-qk0-f196.google.com ([209.85.220.196]:36857 "EHLO mail-qk0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S970349AbdDTPHj (ORCPT ); Thu, 20 Apr 2017 11:07:39 -0400 MIME-Version: 1.0 In-Reply-To: References: <1492088291-5215-1-git-send-email-svenv@arcx.com> <1492088291-5215-2-git-send-email-svenv@arcx.com> <1492506852.24567.54.camel@linux.intel.com> From: Andy Shevchenko Date: Thu, 20 Apr 2017 18:07:37 +0300 Message-ID: Subject: Re: [PATCH v4 1/1] pwm: pca9685: fix gpio-only operation. To: Sven Van Asbroeck Cc: Andy Shevchenko , Thierry Reding , "Rafael J. Wysocki" , linux-pwm@vger.kernel.org, "linux-kernel@vger.kernel.org" , Mika Westerberg , Sven Van Asbroeck Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 20, 2017 at 5:12 PM, Sven Van Asbroeck wrote: >> Taking above into consideration perhaps sleep is not quite good word >> at all. By functional description it sounds like latency tolerance to >> me. > > That's true, but the bit description in the chip datasheet is 'SLEEP'. > (its real function is suspend/low power, but the chip designers called > it 'SLEEP') > > Calling the bit/function something else is likely to confuse someone > who's reading the driver in combination with the chip datasheet. Looking again into the patch I have noticed: 1) word 'sleep' is used as a part of a function name; 2) int sleep is used as binary value. Thus, I would suggest: int sleep -> bool enable (or alike). Would we agree on that? -- With Best Regards, Andy Shevchenko