public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajat Khandelwal <rajat.khandelwal@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] usb: typec: intel_pmc_mux: Expose IOM port status to debugfs
Date: Tue, 30 May 2023 14:45:03 +0530	[thread overview]
Message-ID: <0367a134-cb04-8a1c-bb46-bb5553df6f8a@linux.intel.com> (raw)
In-Reply-To: <2023052917-juicy-calamity-4b35@gregkh>

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 <rajat.khandelwal@linux.intel.com>
>> Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> 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?
Can you please confirm once and come back?

Thanks
Rajat


  reply	other threads:[~2023-05-30  9:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 10:47 [PATCH v5] usb: typec: intel_pmc_mux: Expose IOM port status to debugfs Rajat Khandelwal
2023-05-29 14:18 ` Greg KH
2023-05-30  9:15   ` Rajat Khandelwal [this message]
2023-05-30  9:27     ` Greg KH
2023-05-30  9:36       ` Rajat Khandelwal
2023-05-30  9:44         ` Greg KH
2023-05-30 16:58           ` Rajat Khandelwal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0367a134-cb04-8a1c-bb46-bb5553df6f8a@linux.intel.com \
    --to=rajat.khandelwal@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox