Received: by 10.223.185.116 with SMTP id b49csp1031641wrg; Wed, 21 Feb 2018 10:53:36 -0800 (PST) X-Google-Smtp-Source: AH8x2260XQn09sLIMoEp/qcn7c7tdeON1C2YaBxoc4KnE7T0e2d/rIDrJW5HFkPxRWBFMrIW3bHZ X-Received: by 10.98.0.67 with SMTP id 64mr4161917pfa.63.1519239216703; Wed, 21 Feb 2018 10:53:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519239216; cv=none; d=google.com; s=arc-20160816; b=ESTCZNs09v644joLKKftHD15MeMLbWQGE5Xh9hSmtWoJwIg33zJifNibs/gZSffacX 3409icMDwiZTFCB7PLqCxEQmHVClPRB/alga+eYM/QR7XTGMYf+pyFEqSUonFzSfIp49 jqlrvj2SWfS3pWkLPWo9eFMMA+dIlPhqNS2no/P8wg4g+7lnNYDpK2sE+zjf2kN37oXb N/HsuZeBvkcATWAGuB4KMSDQFnXb4qgVFPsUQJ/gNXl+JQ2OndvyYH7dvrbc5eeI9K/s 7NdswA66dg2dJqjynoBWBelEIcN6lfD17gnQZEtABE0bnw+YLxxCcKc2Vml5+KZ4ULXA 0Blw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=bYRWJ25cZWIXypXLf5QJ+8AYVGBQns5/h3ypAEdjep8=; b=BYjrBzwYPQuc/hbEK5LgFVt95Y4adViUTUbv9kO4h5A3NSCyzsj1QY5xB/hzhm9CJH Pgc/iUkjGKdnr4FT37YniUgi85C/FRP/R6VaZLKEmEeSl8hW9y6uN/F099Ud1GWBQcHr SdzKLZalbDA/E2L6JlA6NMossYdi2OgthVJTcC8OCE/tfO5D6CtVVU+qfzoEIv/uTvjG kaw3fG2+K+8FD9klKVVtCaPC51gnGDQqKEY9MnnFWI8LAC1XFTxPkxbaSOc/9s791tp0 h3DI3IouwgwUhjf8XFOF+D/S4v3/HKT6m25RaXv0FWuR5ZulNS89i9qBmM8UtkkD8bHW WT5Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=K44vHiiF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q14si1955225pfa.215.2018.02.21.10.53.22; Wed, 21 Feb 2018 10:53:36 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=K44vHiiF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S937833AbeBUOjO (ORCPT + 99 others); Wed, 21 Feb 2018 09:39:14 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:33511 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934187AbeBUOjM (ORCPT ); Wed, 21 Feb 2018 09:39:12 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 2C5F920F2B; Wed, 21 Feb 2018 09:39:11 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 21 Feb 2018 09:39:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=bYRWJ25cZWIXypXLf5QJ+8AYVGBQn s5/h3ypAEdjep8=; b=K44vHiiF68HAuegg3TwiHI7b3VTMdIye5ENqITVl/Ok+S vw9+1tlp2JLkx2TMg4gD9VGnRbEEGc5S+bE2TinvRD+crTN2myze/26ykqVzbcQl Fdq+H2ONnhuDa+DQVUdZ/pD4Sh68No++v2vzukKNBJGQ+Z23EQkxI1U58NwF42y/ W7/517r6CD5CwivwykBvQheLXyp3sxc87slJ4hbYbkZ1UgaMwj7WcNuimoGF2WoX gyq5AorU1O79SILYxM6ZOLPk7k1dD6t4wIU9o3xvFrVDUOpf0IxgsrDC4fBltiNz EnxLSa7tcCNjpXpdSbUQC9LX2r+MzhmpWdmufggeQ== X-ME-Sender: Received: from localhost (lfbn-1-12258-90.w90-92.abo.wanadoo.fr [90.92.71.90]) by mail.messagingengine.com (Postfix) with ESMTPA id B8C917E3C9; Wed, 21 Feb 2018 09:39:10 -0500 (EST) Date: Wed, 21 Feb 2018 15:39:09 +0100 From: Greg KH To: ShuFanLee Cc: heikki.krogerus@linux.intel.com, linux@roeck-us.net, shufan_lee@richtek.com, cy_huang@richtek.com, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Subject: Re: [PATCH v3] Handle vendor defined behavior in tcpci_init, tcpci_set_vconn and export tcpci_irq. More operations can be extended in tcpci_data if needed. According to TCPCI specification, 4.4.5.2 ROLE_CONTROL, TCPC shall not start DRP toggling until subsequently the TCPM writes to the COMMAND register to start DRP toggling. DRP toggling flow is chagned as following: - Write DRP = 0 & Rd/Rd - Write DRP = 1 - Set LOOK4CONNECTION command Message-ID: <20180221143909.GA29620@kroah.com> References: <1519223434-7396-1-git-send-email-leechu729@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519223434-7396-1-git-send-email-leechu729@gmail.com> User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 21, 2018 at 10:30:34PM +0800, ShuFanLee wrote: > From: ShuFanLee > > Signed-off-by: ShuFanLee Something went really wrong with your subject line :( Please fix and try again. thanks, greg k-h