From: Peter Chen <peter.chen@freescale.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Felipe Balbi <balbi@ti.com>,
David Cohen <david.a.cohen@linux.intel.com>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] usb: common and dwc3: converting to unified device property
Date: Thu, 27 Aug 2015 09:37:21 +0800 [thread overview]
Message-ID: <20150827013720.GA24001@shlinux2> (raw)
In-Reply-To: <20150826101322.GA12746@kuha.fi.intel.com>
On Wed, Aug 26, 2015 at 01:13:22PM +0300, Heikki Krogerus wrote:
> Hi Peter,
>
> On Wed, Aug 26, 2015 at 12:53:20PM +0800, Peter Chen wrote:
> > On Tue, Aug 25, 2015 at 02:04:30PM +0300, Heikki Krogerus wrote:
> > > Hi,
> > >
> > > While converting dwc3 to the unified device property interface, I
> > > noticed that there is really nothing preventing of_usb_get_dr_mode and
> > > of_usb_get_maximum_speed from being converted as well. Hope that's OK.
> > >
> >
> > Place the reference for usb_get_dr_mode and usb_get_maximum_speed
> > at otg.h and ch9.h may not be good, why not add a common.h which
> > is at include/linux/usb/ too.
>
> Why? I'm not going to introduce new header file for prototypes which
> depend on constants defined in other header files, unless there is a
> really good reason. Please note that the prototypes for the existing
> generic functions in common.c are defined in ch9.h and otg.h.
Ok, I just had considered host controller driver may also call
usb_get_maximum_speed to get platform available speed, so I am
wonder if it is suitable to place it at ch9.h.
>
> These functions are _generic_ helpers for dealing with definitions in
> ch9.h and otg.h, so I don't really see any reason for putting their
> prototypes anywhere else then into those same headers.
>
>
> Thanks,
>
> --
> heikki
--
Best Regards,
Peter Chen
prev parent reply other threads:[~2015-08-27 3:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 11:04 [PATCH 0/5] usb: common and dwc3: converting to unified device property Heikki Krogerus
2015-08-25 11:04 ` [PATCH 1/5] usb: common: of_usb_get_maximum_speed to usb_get_maximum_speed Heikki Krogerus
2015-09-18 19:42 ` Felipe Balbi
2015-09-21 7:06 ` Heikki Krogerus
2015-08-25 11:04 ` [PATCH 2/5] usb: dwc3: st: prepare the driver for generic usb_get_dr_mode function Heikki Krogerus
2015-08-25 11:04 ` [PATCH 3/5] usb: common: of_usb_get_dr_mode to usb_get_dr_mode Heikki Krogerus
2015-08-25 11:04 ` [PATCH 4/5] usb: dwc3: core: convert to unified device property interface Heikki Krogerus
2015-08-25 11:04 ` [PATCH 5/5] usb: dwc3: pci: passing forward the ACPI companion Heikki Krogerus
2015-08-26 4:53 ` [PATCH 0/5] usb: common and dwc3: converting to unified device property Peter Chen
2015-08-26 10:13 ` Heikki Krogerus
2015-08-27 1:37 ` Peter Chen [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=20150827013720.GA24001@shlinux2 \
--to=peter.chen@freescale.com \
--cc=balbi@ti.com \
--cc=david.a.cohen@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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