Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp259226imj; Wed, 13 Feb 2019 07:55:26 -0800 (PST) X-Google-Smtp-Source: AHgI3Ia8DfCyVLC9sqfB1WND0U+3BkSBNkk9E+Nuk8Xu0lcWCH1esOWVAnES3xCjM/Fe99KNJ2lW X-Received: by 2002:a63:698a:: with SMTP id e132mr1086665pgc.136.1550073326433; Wed, 13 Feb 2019 07:55:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550073326; cv=none; d=google.com; s=arc-20160816; b=Xws1JYhAB2xUMjfHAE9BptBsNGkObyOhAOEQP99id77YeeB12ibCwyDDZ9fDB/GPL8 gUPDRA9kONOACYZsGc2UO2Q0TgY+YKTPgkZ6OhunEBpcs6mIPNPlkHPs05riMNfkX8Jf OtnRifAm2pzf2y+UTZBddmXi4t3ml3xjjJafB30/ksN+1tJd7OmT07i8LH/5mxnKG2gP z3NTjcNsJ9ESn8I/UK0olJMsMA820BTBnnoLPAzRtMWkSaj0PG+FDVrg/KaylKSaLLWi QLAyDaOw6oXe3gyz6sNLNUn3dhuF/myZ6e7z1pP8Oc8jDPal3O7wL8akIK8H6qZv/oFW L/9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=SJyoYTkklg6YX5aMWYxC2JL5apOFZ1x29KPe/mQNmRU=; b=X2mEmM2DQB7DpNGrNreTiWMvgYjJFmligXOIEalen4s0ZZnRB8W0FXG6oUhtqudLYu jL5DBxiICAT39aBa3jS9BrnxfgXluH0RZ8Z16Ldwd2CaPZiYDpE5hpOUfEavr64Fe3dN GRTFdEFGwVzrb/wkPNT2gJvFE8LdhVHDaF6f39biKSLtHMhvuNrZIzSOm21UEDVAHh5u SqHGwblPr0m691BuMwyX7gA2a6zQ/EYgwpXzC0gpAQS7vlU0X9RP+U8SoK9pWEtAEgfG lRSYE8FfCRzj9egi1435OIB5v1mylLwNJTwPMiBY4k1Cy6WrOV/wdY8JqaWhbu0/Ml9w aF+A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o12si10729410pgn.145.2019.02.13.07.54.47; Wed, 13 Feb 2019 07:55:26 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391601AbfBMPSE (ORCPT + 99 others); Wed, 13 Feb 2019 10:18:04 -0500 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:24878 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2389582AbfBMPSE (ORCPT ); Wed, 13 Feb 2019 10:18:04 -0500 Received: from pps.filterd (m0046660.ppops.net [127.0.0.1]) by mx08-00178001.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x1DFF6nQ024692; Wed, 13 Feb 2019 16:17:49 +0100 Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx08-00178001.pphosted.com with ESMTP id 2qhv0m7wea-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 13 Feb 2019 16:17:49 +0100 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id ACD1231; Wed, 13 Feb 2019 15:17:48 +0000 (GMT) Received: from Webmail-eu.st.com (sfhdag5node3.st.com [10.75.127.15]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 69DF3584D; Wed, 13 Feb 2019 15:17:48 +0000 (GMT) Received: from [10.48.0.167] (10.75.127.51) by SFHDAG5NODE3.st.com (10.75.127.15) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 13 Feb 2019 16:17:47 +0100 Subject: Re: [PATCH v3 3/3] pwm: core: add consumer device link To: Thierry Reding CC: , , , , , , , , , , References: <1550055012-23348-1-git-send-email-fabrice.gasnier@st.com> <1550055012-23348-4-git-send-email-fabrice.gasnier@st.com> <20190213125353.GI647@ulmo> From: Fabrice Gasnier Message-ID: Date: Wed, 13 Feb 2019 16:17:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190213125353.GI647@ulmo> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.75.127.51] X-ClientProxiedBy: SFHDAG5NODE2.st.com (10.75.127.14) To SFHDAG5NODE3.st.com (10.75.127.15) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-02-13_09:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/13/19 1:53 PM, Thierry Reding wrote: > On Wed, Feb 13, 2019 at 11:50:12AM +0100, Fabrice Gasnier wrote: >> Add a device link between the PWM consumer and the PWM provider. This >> enforces the PWM user to get suspended before the PWM provider. It >> allows proper synchronization of suspend/resume sequences: the PWM user >> is responsible for properly stopping PWM, before the provider gets >> suspended: see [1]. Add the device link in: >> - of_pwm_get() >> - pwm_get() >> - devm_ variants >> as it requires a reference to the device for the PWM consumer. >> >> [1] https://lkml.org/lkml/2019/2/5/770 >> >> Suggested-by: Thierry Reding >> Signed-off-by: Fabrice Gasnier >> --- >> Changes in v3: >> - add struct device to of_get_pwm() arguments to handle device link from >> there. >> --- >> drivers/pwm/core.c | 14 +++++++++++--- >> include/linux/pwm.h | 6 ++++-- >> 2 files changed, 15 insertions(+), 5 deletions(-) >> >> diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c >> index 1581f6a..8cb5d4bc 100644 >> --- a/drivers/pwm/core.c >> +++ b/drivers/pwm/core.c >> @@ -638,6 +638,7 @@ static struct pwm_chip *of_node_to_pwmchip(struct device_node *np) >> >> /** >> * of_pwm_get() - request a PWM via the PWM framework >> + * @dev: device for PWM consumer >> * @np: device node to get the PWM from >> * @con_id: consumer name >> * >> @@ -655,7 +656,8 @@ static struct pwm_chip *of_node_to_pwmchip(struct device_node *np) >> * Returns: A pointer to the requested PWM device or an ERR_PTR()-encoded >> * error code on failure. >> */ >> -struct pwm_device *of_pwm_get(struct device_node *np, const char *con_id) >> +struct pwm_device *of_pwm_get(struct device *dev, struct device_node *np, >> + const char *con_id) >> { >> struct pwm_device *pwm = NULL; >> struct of_phandle_args args; >> @@ -689,6 +691,9 @@ struct pwm_device *of_pwm_get(struct device_node *np, const char *con_id) >> if (IS_ERR(pwm)) >> goto put; >> >> + if (!device_link_add(dev, pwm->chip->dev, DL_FLAG_AUTOREMOVE_CONSUMER)) >> + pr_debug("%s(): device link not added\n", __func__); > > I think it's better to turn this into dev_dbg(dev, ...) and maybe > mention which supplier it failed to link to, something like: > > if (!device_link_add(...)) > dev_dbg(dev, "failed to create device link to %s\n", > pwm->chip->dev); Hi Thierry, Thanks for reviewing. I can update this: I used pr_debug() as there are pr_err() calls elsewhere in this routine. BTW, do you wish an additional patch to turn pr_err() into dev_err() in of_pwm_get()? > > Also, I wonder if this should perhaps be dev_err(). Under what > circumstances does this fail? Well, here is a comment from "device_link_add()" routine: " /* * If the supplier has not been fully registered yet or there is a * reverse dependency between the consumer and the supplier already in * the graph, return NULL. */ " => Here the PWM supplier is already registered. (It seems a probe defer can be returned few lines above otherwise.) Other possibilities: kzalloc() failed, no consumer or supplier has been provided (or invalid flags, but this is hardcoded here.). So, I see two case here: 1 - The caller provided a 'dev' for PWM consumer... So, NULL link is an error when consumer & supplier has been passed correctly. => I can add a check on 'dev' for PWM consumer and report an error here: return -EINVAL 2 - The caller can't provide a 'dev' for PWM consumer as you mention bellow: "to allow code to get at the PWM if they didn't have..." => We should probably add a dev_warn() here, with no error ? Please see here after. > >> + >> /* >> * If a consumer name was not given, try to look it up from the >> * "pwm-names" property if it exists. Otherwise use the name of >> @@ -771,7 +776,7 @@ struct pwm_device *pwm_get(struct device *dev, const char *con_id) >> >> /* look up via DT first */ >> if (IS_ENABLED(CONFIG_OF) && dev && dev->of_node) >> - return of_pwm_get(dev->of_node, con_id); >> + return of_pwm_get(dev, dev->of_node, con_id); >> >> /* >> * We look up the provider in the static table typically provided by >> @@ -851,6 +856,9 @@ struct pwm_device *pwm_get(struct device *dev, const char *con_id) >> pwm->args.period = chosen->period; >> pwm->args.polarity = chosen->polarity; >> >> + if (!device_link_add(dev, pwm->chip->dev, DL_FLAG_AUTOREMOVE_CONSUMER)) >> + pr_debug("%s(): device link not added\n", __func__); > > Same here. Also: not sure if we really need to include __func__ in the > message. > >> + >> return pwm; >> } >> EXPORT_SYMBOL_GPL(pwm_get); >> @@ -939,7 +947,7 @@ struct pwm_device *devm_of_pwm_get(struct device *dev, struct device_node *np, >> if (!ptr) >> return ERR_PTR(-ENOMEM); >> >> - pwm = of_pwm_get(np, con_id); >> + pwm = of_pwm_get(dev, np, con_id); >> if (!IS_ERR(pwm)) { >> *ptr = pwm; >> devres_add(dev, ptr); >> diff --git a/include/linux/pwm.h b/include/linux/pwm.h >> index d5199b5..895e074 100644 >> --- a/include/linux/pwm.h >> +++ b/include/linux/pwm.h >> @@ -406,7 +406,8 @@ struct pwm_device *of_pwm_xlate_with_flags(struct pwm_chip *pc, >> const struct of_phandle_args *args); >> >> struct pwm_device *pwm_get(struct device *dev, const char *con_id); >> -struct pwm_device *of_pwm_get(struct device_node *np, const char *con_id); >> +struct pwm_device *of_pwm_get(struct device *dev, struct device_node *np, >> + const char *con_id); > > I'm slightly concerned about this. I think one of the reasons why this > was introduced was to allow code to get at the PWM if they didn't have > a struct device * available. However, it doesn't seem like there are any > users of that function, so this seems fine. The git blame pointed out commit 8eb961279960: " pwm: core: Rename of_pwm_request() to of_pwm_get() and export it Allow client driver to use of_pwm_get() to get the PWM they need. This is needed for drivers which handle more than one PWM separately, like leds-pwm driver, which have: " ... For instance, I tested the leds-pwm driver. It uses the devm_* variant now (as others), there is a struct device * available. So yes, it seems fine. The only thing maybe out of tree code? This is where I have a doubt on having a mandatory struct device * to enforce consumer link creation... or make it optional (e.g. behave as a 'legacy' API) and warn the caller. Please let me know your feeling. Best regards, Fabrice > > Thierry > >> void pwm_put(struct pwm_device *pwm); >> >> struct pwm_device *devm_pwm_get(struct device *dev, const char *con_id); >> @@ -494,7 +495,8 @@ static inline struct pwm_device *pwm_get(struct device *dev, >> return ERR_PTR(-ENODEV); >> } >> >> -static inline struct pwm_device *of_pwm_get(struct device_node *np, >> +static inline struct pwm_device *of_pwm_get(struct device *dev, >> + struct device_node *np, >> const char *con_id) >> { >> return ERR_PTR(-ENODEV); >> -- >> 1.9.1 >>