From: 啟原黃 <u0084500@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
cy_huang <cy_huang@richtek.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
gene_chen@richtek.com, shufan_lee@richtek.com
Subject: Re: [PATCH] From: cy_huang <cy_huang@richtek.com> Subject: usb: add more vendor defined ops in tcpci
Date: Thu, 15 Aug 2019 16:04:35 +0800 [thread overview]
Message-ID: <CADiBU3__gnBfab2DDPGudBjOiAW2xmGCYF-c2fLx9PyqQzA84w@mail.gmail.com> (raw)
In-Reply-To: <20190815071402.GA25906@kroah.com>
Greg KH <gregkh@linuxfoundation.org> 於 2019年8月15日 週四 下午3:14寫道:
>
> On Thu, Aug 15, 2019 at 12:19:13PM +0800, cy_huang wrote:
> > diff --git a/drivers/usb/typec/tcpm/tcpci.h b/drivers/usb/typec/tcpm/tcpci.h
> > index 303ebde..a6754fb 100644
> > --- a/drivers/usb/typec/tcpm/tcpci.h
> > +++ b/drivers/usb/typec/tcpm/tcpci.h
> > @@ -130,6 +130,11 @@ struct tcpci_data {
> > bool enable);
> > int (*start_drp_toggling)(struct tcpci *tcpci, struct tcpci_data *data,
> > enum typec_cc_status cc);
> > + int (*set_vbus)(struct tcpci *tcpci,
> > + struct tcpci_data *data, bool source, bool sink);
> > + int (*get_current_limit)(struct tcpci *tcpci, struct tcpci_data *data);
> > + int (*set_current_limit)(struct tcpci *tcpci,
> > + struct tcpci_data *data, u32 max_ma, u32 mv);
> > };
>
> You are adding callbacks here with no users of them, which isn't
> allowed. Please also submit the code that uses these callbacks at the
> same time so we can review it all together.
>
> thanks,
>
> greg k-h
Yes, I'm adding the callback for the sub-pmic (CHG/TCPC)
I'll push the mfd driver first. for the tcpc, it's just a sub device.
prev parent reply other threads:[~2019-08-15 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 4:19 [PATCH] From: cy_huang <cy_huang@richtek.com> Subject: usb: add more vendor defined ops in tcpci cy_huang
2019-08-15 7:08 ` Greg KH
2019-08-15 7:14 ` Greg KH
2019-08-15 8:04 ` 啟原黃 [this message]
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=CADiBU3__gnBfab2DDPGudBjOiAW2xmGCYF-c2fLx9PyqQzA84w@mail.gmail.com \
--to=u0084500@gmail.com \
--cc=cy_huang@richtek.com \
--cc=gene_chen@richtek.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=shufan_lee@richtek.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).