From: Maxim Levitsky <mlevitsk@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, andriy.shevchenko@linux.intel.com,
rafael.j.wysocki@intel.com, sakari.ailus@linux.intel.com,
heikki.krogerus@linux.intel.com
Subject: Re: kernel oops in 'typec_ucsi' due to commit 'drivers property: When no children in primary, try secondary'
Date: Thu, 16 Jul 2020 11:47:09 +0300 [thread overview]
Message-ID: <fdbc12dc79ed73c00d37d5b60c00afc3d7e3f556.camel@redhat.com> (raw)
In-Reply-To: <20200716082807.GA1335446@kroah.com>
On Thu, 2020-07-16 at 10:28 +0200, Greg KH wrote:
> On Thu, Jul 16, 2020 at 11:17:03AM +0300, Maxim Levitsky wrote:
> > Hi!
> >
> > Few days ago I bisected a regression on 5.8 kernel:
> >
> > I have nvidia rtx 2070s and its USB type C port driver (which is open source)
>
> Is that driver merged into the tree? If not, do you have a pointer to
> it somewhere?
>
> thanks,
>
> greg k-h
>
It is in the tree.
CONFIG_TYPEC_UCSI selectes the generic UCSI driver
CONFIG_UCSI_CCG selects the hardware driver,
which is an i2c driver which binds to an i2c device (I think with address 0x8)
on an i2c controller, which is exposed by function 3 of the NVIDIA card, and uses the
CONFIG_I2C_NVIDIA_GPU driver.
We also have CONFIG_TYPEC_NVIDIA_ALTMODE which I haven't researched
what it does.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2020-07-16 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 8:17 kernel oops in 'typec_ucsi' due to commit 'drivers property: When no children in primary, try secondary' Maxim Levitsky
2020-07-16 8:28 ` Greg KH
2020-07-16 8:47 ` Maxim Levitsky [this message]
2020-07-16 14:34 ` Andy Shevchenko
2020-07-16 17:59 ` Maxim Levitsky
2020-07-16 15:47 ` Andy Shevchenko
2020-07-16 18:00 ` Maxim Levitsky
2020-07-16 18:21 ` Andy Shevchenko
2020-07-16 18:22 ` Maxim Levitsky
2020-07-16 18:33 ` Andy Shevchenko
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=fdbc12dc79ed73c00d37d5b60c00afc3d7e3f556.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sakari.ailus@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;
as well as URLs for NNTP newsgroup(s).