Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp5778555ybx; Sun, 10 Nov 2019 21:28:08 -0800 (PST) X-Google-Smtp-Source: APXvYqzy0Kjc2mapFBR3uPO8dCFnY1fQtyNtfxBBD9zF6KXKBZARNr0ozi34A198hP/G8byjcsFf X-Received: by 2002:a50:9254:: with SMTP id j20mr25521611eda.0.1573450088083; Sun, 10 Nov 2019 21:28:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573450088; cv=none; d=google.com; s=arc-20160816; b=vncI8OCi9BixFWMd83Q88nUoOdNKSulUmfnIQgYTpZoA2oC0b5SWBUdELKlIhSruuY WIjMf+y0KW8YpmKi24lv0FCVSCCZuRetXXPHcgyDVmXxF5bsyZiBNHNPyF3gXnfXtoLk 3dgqqlKJycuo0u2RGqF7Qdk+TiGBQeaTMeyiGyTWNbioob2QK9791iVq5bc2pypfiCXQ WwoP9G42X0a2X+jvmSHSnFPp/sxdWpg9RhWFxLpskWK0EhYVVPXWWLlQDRUGD2RpivLO KDyoSHAgioFdFOOsEsUVQIs0NSyJQBJZfCeM9fei1MyDBSTVtwtIpQVKrUetQK4gS+fS GWlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=DXwG7Htt8xNu0lrk1CpbOO5TmV59fWwZQbJzjoVIM78=; b=VRqaIWK/7Kry7gyVKkCbfEEK/6NVkXaKhmHNJL0XpAZ10Upw3sQKVj5Tcf77oOMx6S 6hGV/MeeTgWmAMLHttWWVtgmbfABH3pV9l2bag97+jChlykQgRPSOF6AWNifCYEJTHIq pLJ+wT3N3511bFUJwsv/HmJyflU7HNQuK50To/SnskAX20IYR5zXNOyhYGYIWaTpxUSi 8GVUgDKKU0ys8h38zlsCaQglrdS65ut2uMExYgFqCuVAToUXx+Zwr5sIjJ8dOmYgIt6+ M37BTU2ppYXRfMo3/rVwi0n9Se9VqglobggOBeaKy6lDR29j3hHynFg6YXJNjs/hCwAq 8WUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@verdurent-com.20150623.gappssmtp.com header.s=20150623 header.b=h8lrbRMr; 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 e5si8773095edn.370.2019.11.10.21.27.45; Sun, 10 Nov 2019 21:28:08 -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; dkim=pass header.i=@verdurent-com.20150623.gappssmtp.com header.s=20150623 header.b=h8lrbRMr; 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 S1726924AbfKKF0s (ORCPT + 99 others); Mon, 11 Nov 2019 00:26:48 -0500 Received: from mail-vk1-f196.google.com ([209.85.221.196]:44476 "EHLO mail-vk1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726908AbfKKF0s (ORCPT ); Mon, 11 Nov 2019 00:26:48 -0500 Received: by mail-vk1-f196.google.com with SMTP id o198so2857890vko.11 for ; Sun, 10 Nov 2019 21:26:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verdurent-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DXwG7Htt8xNu0lrk1CpbOO5TmV59fWwZQbJzjoVIM78=; b=h8lrbRMrrhVlG6DWJGLEMzVAA3RZl2r6zZCSH8Buo45xvL6NfgvfUszEX1y9lILLGN V8mlpV90yp5XtQmkx1Q9RteWm9G1IL5Fj5+d1ZiO16Dm4IQ0oi4H7iJxttg49FfFIFEu 4o3XmqaUvlKymwS514aX4+oaXdsEuBuAnWQt3ofclnGD340pPa8BqmX0cMTcMuEtlHb/ ZuPtFOpOJcKDMLhgLXTPCk959aHIeQWOPpNInWwdWDCijdZJGKZCZ88DhFDpFbTKBYa8 CfBi0wPSBklojiNhead9uXF5ha7uIcwFiQozmx5fsG2wgSyNfyipe2u0og2QTv4B9+tZ pW3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DXwG7Htt8xNu0lrk1CpbOO5TmV59fWwZQbJzjoVIM78=; b=BoRHPQPKbaNWGuYSmpuLJO741yGfq0HFU4X6dL1lTMoAiJKvIELN71Lb3eEdEGqRzi vvyPPrBYdIxsuS3/QkTFkbKmXS3NTfmkuB6HSrU40BUrzdIH3cSPUi7JnWVDvogWmMxj cUeJB0E2ajpHUQ5mZM36SnvOBOuibsnvRZK8G5ldSOq1auU//+eqNEkBG3uERDcby1gP LIlxmkIoq1/ZfdJxPzzQAt5inTvlh2+HZMa7qys6NJFtV7snTbQZ25+RaR9QErs+iGaU 9Yz+zmLDjdqT8knCRgPEHgAN8IrRr8kFz+CX5ryhIA5vL9ceHbrY0NYRfVeAdPCbNUbo bbJg== X-Gm-Message-State: APjAAAWYxj3hab1x2cUKp8y4R7m9wfBIHw12JM5LzhIcUxENMT04PgH6 Kw+Ynj7V0xQRoypyxOMzNSYyWoO9hpkMfFEuxpedmg== X-Received: by 2002:a1f:7387:: with SMTP id o129mr16986118vkc.73.1573450005202; Sun, 10 Nov 2019 21:26:45 -0800 (PST) MIME-Version: 1.0 References: <20191015061349.141448-1-wvw@google.com> In-Reply-To: From: Amit Kucheria Date: Mon, 11 Nov 2019 10:56:34 +0530 Message-ID: Subject: Re: [PATCH] thermal: create softlink by name for thermal_zone and cooling_device To: Wei Wang Cc: Wei Wang , Zhang Rui , Eduardo Valentin , Daniel Lezcano , Linux PM list , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 17, 2019 at 3:04 AM Wei Wang wrote: > > On Wed, Oct 16, 2019 at 10:16 AM Amit Kucheria > wrote: > > > > On Wed, Oct 16, 2019 at 10:20 PM Amit Kucheria > > wrote: > > > > > > On Tue, Oct 15, 2019 at 11:43 AM Wei Wang wrote: > > > > > > > > The paths thermal_zone%d and cooling_device%d are not intuitive and the > > > > numbers are subject to change due to device tree change. This usually > > > > leads to tree traversal in userspace code. > > > > The patch creates `tz-by-name' and `cdev-by-name' for thermal zone and > > > > cooling_device respectively. > > > > > > I like this. > > > > > > > Signed-off-by: Wei Wang > > > > --- > > > > drivers/thermal/thermal_core.c | 23 +++++++++++++++++++++-- > > > > 1 file changed, 21 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c > > > > index d4481cc8958f..0ff8fb1d7b0a 100644 > > > > --- a/drivers/thermal/thermal_core.c > > > > +++ b/drivers/thermal/thermal_core.c > > > > @@ -22,6 +22,7 @@ > > > > #include > > > > #include > > > > #include > > > > +#include > > > > > > > > #define CREATE_TRACE_POINTS > > > > #include > > > > @@ -46,6 +47,8 @@ static DEFINE_MUTEX(poweroff_lock); > > > > > > > > static atomic_t in_suspend; > > > > static bool power_off_triggered; > > > > +static struct kobject *cdev_link_kobj; > > > > +static struct kobject *tz_link_kobj; > > > > > > > > static struct thermal_governor *def_governor; > > > > > > > > @@ -954,7 +957,7 @@ __thermal_cooling_device_register(struct device_node *np, > > > > struct thermal_zone_device *pos = NULL; > > > > int result; > > > > > > > > - if (type && strlen(type) >= THERMAL_NAME_LENGTH) > > > > + if (!type || !type[0] || strlen(type) >= THERMAL_NAME_LENGTH) > > > > return ERR_PTR(-EINVAL); > > > > > > This should be a separate fix, if needed. > Agree, but the link now requires that "" as invalid _type_. I'm not sure I understand. What does this change have to do with adding symlinks below? > > > > > > > if (!ops || !ops->get_max_state || !ops->get_cur_state || > > > > @@ -989,9 +992,15 @@ __thermal_cooling_device_register(struct device_node *np, > > > > return ERR_PTR(result); > > > > } > > > > > > > > - /* Add 'this' new cdev to the global cdev list */ > > > > + /* Add 'this' new cdev to the global cdev list and create link*/ > > > > mutex_lock(&thermal_list_lock); > > > > list_add(&cdev->node, &thermal_cdev_list); > > > > + if (!cdev_link_kobj) > > > > + cdev_link_kobj = kobject_create_and_add("cdev-by-name", > > > > + cdev->device.kobj.parent); > > > > + if (!cdev_link_kobj || sysfs_create_link(cdev_link_kobj, > > > > + &cdev->device.kobj, cdev->type)) > > > > + dev_err(&cdev->device, "Failed to create cdev-by-name link\n"); > > > > > > Any reason not to use the following form instead? It seems easier to read. > > > > > > if (!cdev_link_kobj) { > > > cdev_link_kobj = kobject_create_and_add("cdev-by-name", > > > cdev->device.kobj.parent); > > > ret = sysfs_create_link(cdev_link_kobj, > > > &cdev->device.kobj, cdev->type)) > > > if (ret) > > > dev_err(&cdev->device, "Failed to create > > > cdev-by-name link\n"); > > > } > > > > I can now see why you had to do that - none of the other links would > > get created after the first one. > > > > Perhaps create the directories in the __init functions and only create > > the links here? > > > AFAICT, this is no such API except the private get_device_parent() > under driver/base/. Also the lazy initialization makes sense in such > case when there is no thermal device attached. Looks like the class > dir is also lazy-initialized when first device registered > https://elixir.bootlin.com/linux/v5.3.5/source/drivers/base/core.c#L1790. OK. > > > > > > mutex_unlock(&thermal_list_lock); > > > > > > > > /* Update binding information for 'this' new cdev */ > > > > @@ -1157,6 +1166,8 @@ void thermal_cooling_device_unregister(struct thermal_cooling_device *cdev) > > > > } > > > > } > > > > } > > > > + if (cdev_link_kobj) > > > > + sysfs_remove_link(cdev_link_kobj, cdev->type); > > > > > > > > mutex_unlock(&thermal_list_lock); > > > > > > > > @@ -1340,6 +1351,12 @@ thermal_zone_device_register(const char *type, int trips, int mask, > > > > > > > > mutex_lock(&thermal_list_lock); > > > > list_add_tail(&tz->node, &thermal_tz_list); > > > > + if (!tz_link_kobj) > > > > + tz_link_kobj = kobject_create_and_add("tz-by-name", > > > > + tz->device.kobj.parent); > > > > + if (!tz_link_kobj || sysfs_create_link(tz_link_kobj, > > > > + &tz->device.kobj, tz->type)) > > > > + dev_err(&tz->device, "Failed to create tz-by-name link\n"); > > > > > > Same as above. > > > > > > > mutex_unlock(&thermal_list_lock); > > > > > > > > /* Bind cooling devices for this zone */ > > > > @@ -1411,6 +1428,8 @@ void thermal_zone_device_unregister(struct thermal_zone_device *tz) > > > > } > > > > } > > > > } > > > > + if (tz_link_kobj) > > > > + sysfs_remove_link(tz_link_kobj, tz->type); > > > > > > > > mutex_unlock(&thermal_list_lock); > > > > > > > > -- > > > > 2.23.0.700.g56cf767bdb-goog > > > >