From: Greg KH <gregkh@linuxfoundation.org>
To: Rajat Khandelwal <rajat.khandelwal@linux.intel.com>
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 10:44:48 +0100 [thread overview]
Message-ID: <2023053013-playhouse-dad-1444@gregkh> (raw)
In-Reply-To: <2da06c06-6617-bd02-f20a-a5ea7f9ae0b4@linux.intel.com>
On Tue, May 30, 2023 at 03:06:15PM +0530, Rajat Khandelwal wrote:
> 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 <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?
> > 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
One? I count a lot more:
$ git log --oneline main..usb-next | wc -l
143
> Anyways, do you want me to re-work the patch for the usb-next branch?
Given that I can not take the patch as-is, it's up to you to rebase it
if you wish to have it accepted.
Isn't this all covered in the Intel kernel developer training class?
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-30 9:45 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
2023-05-30 9:27 ` Greg KH
2023-05-30 9:36 ` Rajat Khandelwal
2023-05-30 9:44 ` Greg KH [this message]
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=2023053013-playhouse-dad-1444@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rajat.khandelwal@linux.intel.com \
/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