Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp4766780rwb; Mon, 21 Nov 2022 11:35:52 -0800 (PST) X-Google-Smtp-Source: AA0mqf70/nH94QgG66qNO/IewONQAXu4FPK2lGS5vqLUgYS5tGrFhESagpuzFe9oPCOLbYVyV2Wi X-Received: by 2002:a17:906:b12:b0:7ac:baef:730e with SMTP id u18-20020a1709060b1200b007acbaef730emr16269433ejg.691.1669059352672; Mon, 21 Nov 2022 11:35:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669059352; cv=none; d=google.com; s=arc-20160816; b=HCTi7TA7E4msY+oFchAgU/7phrdzvFFMBbFzbe66+lzXt3dICkyhTBZONrRu4gwR6e 2r1j14C/EVGVffDxUJyebtOqlrDg3Qq1lbZulPri45yKR1ykhpfIZT8qxI1bWSPoWSxo zh4sLUxaecnbDBL63BnzZGTmz/y8VnvXkdv0F8PhU6G7wqzKkY5MAbGBx01JjUP0H2Kf gLHYlplpVtC+eKajX3T2wcToe/bvVuSnW5ceGlcCXHGRMIVOwmzhevlcw14qC9Pmpztk CsirKbE1fBy8uszZYRVX7fP7Jb2NqsTwi7DM8kWPgTA6T45MF4Li1D0FxfOm/x/GRRZ6 qhEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=hdSzcHhKeQkatk8bqFSxlstBSa5XO6OBdkERXfzMdrQ=; b=ChR4G70JXVDe9wl4kt/aysD3Df00akP+BW51qNCp5d0LGb3VVgwVKGC6m/6A6SRYQh x3b+0wm3v2h8WQtNOUxtU8qldePOpox0y1PYz8Bc5HzUmzjRr8l1MG0r/B2z4E7vm2zH ATqnpHQB9bZoHznxc1bbCBfAKLBfr3BhXl25Q879I1wGHv7ALX5yewjlXWZwYPwPmFTE lG4WMowOnoVYTyDxSwio4QCBjfE10+nhIgV+4oTfPXr31OXfKTffV54wT6LgOiVeXNn3 plUxImv/HoeG82ZwVvUPHweoz8GunMpq8kHgk6KFKQWTPSeeBVdzp6CAT5F5TksNZQ/R gZSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=YGs7CAMj; 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=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j14-20020a05640211ce00b00456eaa4fb1fsi10384756edw.223.2022.11.21.11.35.22; Mon, 21 Nov 2022 11:35:52 -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=@chromium.org header.s=google header.b=YGs7CAMj; 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=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231185AbiKUTLh (ORCPT + 92 others); Mon, 21 Nov 2022 14:11:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41818 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229981AbiKUTLf (ORCPT ); Mon, 21 Nov 2022 14:11:35 -0500 Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 84F27D3293 for ; Mon, 21 Nov 2022 11:11:34 -0800 (PST) Received: by mail-pj1-x102d.google.com with SMTP id b11so11264078pjp.2 for ; Mon, 21 Nov 2022 11:11:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=hdSzcHhKeQkatk8bqFSxlstBSa5XO6OBdkERXfzMdrQ=; b=YGs7CAMjf7UgX7lcenztkRFgVOI230bleLaIy5LovzqlyiR9XCz4k2qMKO0sygpFJe Bf2agTCFLpf3NxaMMQ5s0NqqhvdD1k4HXKYcz8sWgLeL8VRFnqI37ka/iRNPeYEvIjf/ PHnBZ/FMt7rwbh/N/an8dqadyk6OTNqU5JM8I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=hdSzcHhKeQkatk8bqFSxlstBSa5XO6OBdkERXfzMdrQ=; b=7STZcEb13xfYskweG/1JcmUHBEk6SyNdQ84ztRtuEJ7sw25WKYipFo6aX8blMOSm9m dKX4SI6qL/QuYp3ayjcivViuPrSWHh1lgF4Yx+KQLlJ4M1MGp6m8ReErIt44k3HR6EPc pRNWgBB6+PGA10YeXDCmZryU8ncIUwm3UrsQ3a129z97rT0RaDhQ1euu0S9UfNFEfs9L HdZGthTZdnraU5qIzM9kdS8dZWGZHWDyBVJ8YrkMmPOUZdxzIJtaoNAOuFekj1ihgSVk 5DpYd+IUbT7+Bn6iqXngElBtiSeJKgg+Url2Dfjupn9zmGnVQNmbznilP8UdTnaKdzms 2Qbw== X-Gm-Message-State: ANoB5pmQdMT6XbsXPTP/wYz8vjTF1xRLFr3NwmfB0PZdItkQHvJNcMmW 13x3foEQqc+HOj9e2kVb3abifw== X-Received: by 2002:a17:902:ce04:b0:187:3a54:9b93 with SMTP id k4-20020a170902ce0400b001873a549b93mr8785475plg.2.1669057894040; Mon, 21 Nov 2022 11:11:34 -0800 (PST) Received: from chromium.org (33.5.83.34.bc.googleusercontent.com. [34.83.5.33]) by smtp.gmail.com with ESMTPSA id n15-20020a170902e54f00b0017f73dc1549sm10176867plf.263.2022.11.21.11.11.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Nov 2022 11:11:33 -0800 (PST) Date: Mon, 21 Nov 2022 19:11:32 +0000 From: Prashant Malani To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, Heikki Krogerus , Benson Leung Subject: Re: [PATCH] usb: typec: pd: Add symlink to linked device Message-ID: References: <20221121062106.2569297-1-pmalani@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, 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 Greg, On Nov 21 08:36, Greg Kroah-Hartman wrote: > On Mon, Nov 21, 2022 at 07:16:03AM +0000, Prashant Malani wrote: > > On Nov 21 07:35, Greg Kroah-Hartman wrote: > > > On Mon, Nov 21, 2022 at 06:20:39AM +0000, Prashant Malani wrote: > > Why either? What exactly is this "device" that you are trying to link > to? And why not just use the real device symlink instead? It's the Type-C port partner device, created here [1] > > > > > > > > What in userspace wants to see this symlink? > > > > ChromeOS's userspace Type-C daemon. It listens for Type-C partner uevents, but the PD objects > > can be created later (and destroyed and then recreated again, for PD chargers which dynamically > > change their source caps), and this helps determine which partner does those events apply to. > > Then set up the proper device symlink like the driver model supports, > then you don't have to create a new one, and you don't have to add the > documentation entry as it's implied. Sounds good. I'll submit a new series (or single patch) which follows this approach. Thanks again! -Prashant [1] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/tree/drivers/usb/typec/class.c?h=usb-next#n885