From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Shah, Nehal-bakulchandra" <nbshah@amd.com>
Cc: ajayg@nvidia.com, linux-usb@vger.kernel.org
Subject: Re: UCSI:CCG: AMD Platform
Date: Mon, 3 Feb 2020 15:32:31 +0200 [thread overview]
Message-ID: <20200203133231.GB29050@kuha.fi.intel.com> (raw)
In-Reply-To: <20200203132808.GA29050@kuha.fi.intel.com>
On Mon, Feb 03, 2020 at 03:28:11PM +0200, Heikki Krogerus wrote:
> Hi,
>
> On Mon, Feb 03, 2020 at 10:52:52AM +0530, Shah, Nehal-bakulchandra wrote:
> > Currently i am working on enabling UCSI support
> > for CCGx based controller on AMD GPU Cards.
> >
> > Now i am observing the issue reported here when
> > i unplug the cable.
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1762031
> >
> > Also would like to know is there any way we can
> > get user level notifications for UCSI?
>
> If you want to see the actual UCSI notification in user space, then
> that is not possible, but the driver does produce trace output, and I
> would actually like to see what we got there. You need debugfs to be
> mounted. Then try the following:
>
> # Unload all UCSI modules
> modprobe -r ucsi_acpi
>
> # At this point you should plug-in the problematic device
>
> # Reload the UCSI core module
> modprobe typec_ucsi
>
> # Enable UCSI tracing
> echo 1 > /sys/kernel/debug/tracing/events/ucsi/enable
>
> # Now reload the ACPI glue driver
> modprobe ucsi_acpi
>
> # Unplug the problematic device so that you see the error
>
> # Finally dump the trace output
> cat /sys/kernel/debug/tracing/trace
>
> So if that works, please send the trace output to me.
Actually, first things first. Please share your dmesg output. Are you
using ucsi_acpi or ucsi_ccg glue driver?
thanks,
--
heikki
next prev parent reply other threads:[~2020-02-03 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 5:22 UCSI:CCG: AMD Platform Shah, Nehal-bakulchandra
2020-02-03 13:28 ` Heikki Krogerus
2020-02-03 13:32 ` Heikki Krogerus [this message]
2020-02-10 10:09 ` Shah, Nehal-bakulchandra
2020-02-13 12:00 ` Heikki Krogerus
2020-02-13 12:05 ` Heikki Krogerus
2020-02-14 14:28 ` Shah, Nehal-bakulchandra
2020-02-24 9:08 ` Shah, Nehal-bakulchandra
2020-02-27 12:23 ` Heikki Krogerus
2020-02-27 16:59 ` Shah, Nehal-bakulchandra
2020-02-29 3:25 ` Shah, Nehal-bakulchandra
2020-03-26 8:35 ` Heikki Krogerus
2020-03-26 13:41 ` Shah, Nehal-bakulchandra
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=20200203133231.GB29050@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=ajayg@nvidia.com \
--cc=linux-usb@vger.kernel.org \
--cc=nbshah@amd.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;
as well as URLs for NNTP newsgroup(s).