From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Oliver Neukum <oneukum@suse.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Roger Quadros <rogerq@ti.com>,
Rajaram R <rajaram.officemail@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCHv4 1/2] usb: USB Type-C connector class
Date: Tue, 5 Jul 2016 21:47:23 +0300 [thread overview]
Message-ID: <20160705184723.GA6976@kuha.fi.intel.com> (raw)
In-Reply-To: <577AA09E.3030909@roeck-us.net>
On Mon, Jul 04, 2016 at 10:45:02AM -0700, Guenter Roeck wrote:
> On 07/04/2016 10:11 AM, Heikki Krogerus wrote:
> [ ... ]
>
> > > > We should not forget also that the userspace can never rely on those
> > > > details because of the fact that they simply will not always be
> > > > available.
> > > >
> > > On the other side, not being able to rely on a well defined ABI makes the
> > > ABI much less useful.
> >
> > What do we do about this?
> >
> I'll have to think about it. Unfortunately, I'll have to put this on the
> back-burner for the time being. My primary problem is that I need
> a functional driver _now_ (ie by the end of this week), to meet an
> upcoming deadline. Due to to the locking problem, I can not rely on the
> typec infrastructure ... meaning I have to take two steps back and get
> my code working with the Android infrastructure (which, coincidentally,
> does not require locking and thus doesn't have all the resulting
> limitations and complexities).
That is unfortunate.
I added a commit where I remove the lock completely (at least for
now) to my github.
Cheers,
--
heikki
next prev parent reply other threads:[~2016-07-05 18:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 13:38 [PATCHv4 0/2] USB Type-C Connector class Heikki Krogerus
2016-06-29 13:38 ` [PATCHv4 1/2] usb: USB Type-C connector class Heikki Krogerus
2016-06-30 17:10 ` Guenter Roeck
2016-07-01 7:38 ` Heikki Krogerus
2016-07-01 14:41 ` Guenter Roeck
2016-06-30 22:02 ` Guenter Roeck
2016-07-01 7:13 ` Heikki Krogerus
2016-07-01 12:05 ` Heikki Krogerus
2016-07-01 14:33 ` Guenter Roeck
2016-07-03 19:38 ` Heikki Krogerus
2016-07-03 21:28 ` Guenter Roeck
2016-07-04 17:11 ` Heikki Krogerus
2016-07-04 17:45 ` Guenter Roeck
2016-07-05 18:47 ` Heikki Krogerus [this message]
2016-06-29 13:38 ` [PATCHv4 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY Heikki Krogerus
2016-08-09 14:01 ` [PATCHv4 0/2] USB Type-C Connector class Greg KH
2016-08-09 16:23 ` Guenter Roeck
2016-08-10 8:19 ` Oliver Neukum
2016-08-16 7:38 ` Heikki Krogerus
2016-08-16 16:40 ` Guenter Roeck
2016-08-17 7:44 ` Heikki Krogerus
2016-08-10 9:20 ` Felipe Balbi
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=20160705184723.GA6976@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oneukum@suse.com \
--cc=rajaram.officemail@gmail.com \
--cc=rogerq@ti.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
Powered by JetHome