All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Tso <kyletso@google.com>
To: Benson Leung <bleung@google.com>
Cc: Prashant Malani <pmalani@google.com>,
	USB <linux-usb@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [usb:usb-testing 155/155] drivers/platform/chrome/cros_ec_typec.c:778:8: error: 'CABLE_ATYPE' undeclared; did you mean
Date: Thu, 4 Feb 2021 00:47:56 +0800	[thread overview]
Message-ID: <CAGZ6i=0vdPoFCCJrk0a-ZDk7KaaKzHkv+V65T3RUaAgjAi7ZAg@mail.gmail.com> (raw)
In-Reply-To: <CANLzEktC3gL9vxsFOmQQ=0ymgPB+0AWQ+NL_tQVB3Jvr4B5LCw@mail.gmail.com>

On Thu, Feb 4, 2021 at 12:40 AM Benson Leung <bleung@google.com> wrote:
>
> Hi Kyle,
>
> On Wed, Feb 3, 2021 at 7:39 AM Kyle Tso <kyletso@google.com> wrote:
> >
> > Hi Prashant and Benson,
> >
> > I just got this notification that my patch "usb: pd: Update VDO
> > definitions" caused this build break.
> > The root cause is that I removed the definitions of Type-A and Type-B
> > in Product Type VDOs as they have already been deprecated.
> > And it's my bad that I didn't notice that someone else uses these definitions...
> >
> > I can fix it by simply removing them in the switch case but I am not
> > sure whether they need to be kept for some reason (compatibility ?)
> > What do you think?
>
> Strictly speaking, Type-A and Type-B definitions here are deprecated
> in PD 3.0, but PD 3.0 implementations have to be able to fall back to
> PD 2.0 protocol when the port partner or cable is PD 2.0 only.
>
> In the last version of the PD 2.0 specification released, the Type-A
> and Type-B definitions still remain, so we can't really remove them
> from the Kernel until all of PD 2.0 is deprecated.
>
> They're very rare cables, but I have seen a PD 2.0 cable with an
> e-marker that indicates Type-B here.
>
> Hope this helps,
> Benson
>
> --
> Benson Leung
> Staff Software Engineer
> Chrome OS Kernel
> Google Inc.
> bleung@google.com
> Chromium OS Project
> bleung@chromium.org

Thanks for the clarification! makes sense to me.
I will provide the fix as soon as possible.

thanks,
Kyle

  reply	other threads:[~2021-02-03 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 15:19 [usb:usb-testing 155/155] drivers/platform/chrome/cros_ec_typec.c:778:8: error: 'CABLE_ATYPE' undeclared; did you mean kernel test robot
2021-02-03 15:19 ` kernel test robot
2021-02-03 15:39 ` Kyle Tso
2021-02-03 16:40   ` Benson Leung
2021-02-03 16:47     ` Kyle Tso [this message]
2021-02-03 16:57       ` Benson Leung

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='CAGZ6i=0vdPoFCCJrk0a-ZDk7KaaKzHkv+V65T3RUaAgjAi7ZAg@mail.gmail.com' \
    --to=kyletso@google.com \
    --cc=bleung@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=pmalani@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.