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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DF1BFC7EE32 for ; Tue, 30 May 2023 09:36:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230136AbjE3Jgg (ORCPT ); Tue, 30 May 2023 05:36:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50026 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230095AbjE3JgV (ORCPT ); Tue, 30 May 2023 05:36:21 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BE2B093; Tue, 30 May 2023 02:36:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1685439380; x=1716975380; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=3ckYj4cSZnQk9S/q4LoCZNhEtpmi9ONFZYxoANi2gzc=; b=MxBgq9Fms3EcgnCxqVt3/RqSY/bbuxeoPcf4f2QA54/fvy7Cgag4nWE5 GTQwZ9AGNIyX5D+oU3ZqmdYQ+/8zEdTQzxY4TssTy8nt6NWyNnPJdn8L6 UL/rgahajokQBY7EDHtN6p8OBngigOOFRmdr2rer3OiltJaBRfzYf/XOf mQsLGQ84rp2dwfFbbvtLLQeryoY+j6Cv6YK8LllTGfCL/qloS9Q2ujBQY DcDHnmZumMjCCzwfaVppBGSBbhbzDiBKD0SdH6/pf7itECggJjKzC8u9I xIA97sZumxI0yZHTEop7wVFC7a2lBFa+eccUU9kpuy1aoTzS/dFIWcNZ0 A==; X-IronPort-AV: E=McAfee;i="6600,9927,10725"; a="344367308" X-IronPort-AV: E=Sophos;i="6.00,203,1681196400"; d="scan'208";a="344367308" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 May 2023 02:36:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10725"; a="683884089" X-IronPort-AV: E=Sophos;i="6.00,203,1681196400"; d="scan'208";a="683884089" Received: from rajatkha-mobl.gar.corp.intel.com (HELO [10.67.146.41]) ([10.67.146.41]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 May 2023 02:36:18 -0700 Message-ID: <2da06c06-6617-bd02-f20a-a5ea7f9ae0b4@linux.intel.com> Date: Tue, 30 May 2023 15:06:15 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: [PATCH v5] usb: typec: intel_pmc_mux: Expose IOM port status to debugfs Content-Language: en-US To: Greg KH Cc: heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230524104754.4154013-1-rajat.khandelwal@linux.intel.com> <2023052917-juicy-calamity-4b35@gregkh> <0367a134-cb04-8a1c-bb46-bb5553df6f8a@linux.intel.com> <2023053049-dexterous-flatware-df04@gregkh> From: Rajat Khandelwal In-Reply-To: <2023053049-dexterous-flatware-df04@gregkh> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 5/30/2023 2:57 PM, Greg KH wrote: > On Tue, May 30, 2023 at 02:45:03PM +0530, Rajat Khandelwal wrote: >> Hi, >> >> On 5/29/2023 7:48 PM, Greg KH wrote: >>> On Wed, May 24, 2023 at 04:17:54PM +0530, Rajat Khandelwal wrote: >>>> IOM status has a crucial role during debugging to check the >>>> current state of the type-C port. >>>> There are ways to fetch the status, but all those require the >>>> IOM port status offset, which could change with platform. >>>> >>>> Make a debugfs directory for intel_pmc_mux and expose the status >>>> under it per port basis. >>>> >>>> Signed-off-by: Rajat Khandelwal >>>> Reviewed-by: Heikki Krogerus >>> Does not apply to my tree :( >> I have pushed the patch on top of the Linus's tree. >> Had a quick check with the USB Linux tree and seems like its a lot >> behind? > What branch did you use? > > Please use the usb-next branch of > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git, which as > of right now, is at 6.4-rc4 + a bunch of USB-specific patches. I see. There is one commit additional in the usb-next tree: ef0a3642b320 usb: typec: intel_pmc_mux: Convert to platform remove callback returning void Anyways, do you want me to re-work the patch for the usb-next branch? Thanks Rajat > > thanks, > > greg k-h