From: Felipe Balbi <balbi@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Baolin Wang <baolin.wang@linaro.org>,
gregkh@linuxfoundation.org, sre@kernel.org, dbaryshkov@gmail.com,
dwmw2@infradead.org, peter.chen@freescale.com,
stern@rowland.harvard.edu, r.baldyga@samsung.com,
yoshihiro.shimoda.uh@renesas.com, lee.jones@linaro.org,
ckeepax@opensource.wolfsonmicro.com,
patches@opensource.wolfsonmicro.com, linux-pm@vger.kernel.org,
linux-usb@vger.kernel.org,
device-mainlining@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/4] gadget: Introduce the usb charger framework
Date: Thu, 31 Mar 2016 09:21:59 +0300 [thread overview]
Message-ID: <87vb43goag.fsf@intel.com> (raw)
In-Reply-To: <20160330174458.GP2350@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
Mark Brown <broonie@kernel.org> writes:
> [ text/plain ]
> On Wed, Mar 30, 2016 at 01:09:00PM +0300, Felipe Balbi wrote:
>> Baolin Wang <baolin.wang@linaro.org> writes:
>
>> > +#include <linux/of.h>
>> > +#include <linux/of_device.h>
>> > +#include <linux/of_address.h>
>> > +#include <linux/platform_device.h>
>
>> not very nice to depend on either of or platform_device here. What about
>> PCI-based devices ?
>
> The header inclusion shouldn't be conditional though. But looking at
> the patch I can't immediately see any use of these in the code anyway.
fair enough, seems like removal is the way.
>> > +static DEVICE_ATTR_RW(sdp_limit);
>
>> why RW ? Who's going to use these ? Also, you're not documenting this
>> new sysfs file.
>
> If they end up not writeable should we just remove them entirely since
> they should just be the spec values?
if they are really just spec values, why would even let them be modified
to start with ? ;-)
But yeah, seems like this is not interesting to userland.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-03-31 6:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 11:46 [PATCH v7 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Baolin Wang
2016-03-16 11:46 ` [PATCH v7 1/4] gadget: Introduce the usb charger framework Baolin Wang
2016-03-16 12:09 ` Oliver Neukum
2016-03-17 1:58 ` Baolin Wang
2016-03-30 10:09 ` Felipe Balbi
[not found] ` <87h9foqnur.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-03-30 17:44 ` Mark Brown
2016-03-31 6:21 ` Felipe Balbi [this message]
2016-03-31 6:28 ` Baolin Wang
2016-03-31 6:42 ` Felipe Balbi
2016-03-22 11:30 ` Pavel Machek
2016-04-18 8:12 ` Felipe Balbi
2016-04-18 10:23 ` Pavel Machek
2016-04-18 10:30 ` Felipe Balbi
[not found] ` <877ffvgqe9.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-18 10:39 ` Pavel Machek
2016-04-18 10:49 ` Felipe Balbi
2016-04-18 10:55 ` Felipe Balbi
2016-04-18 11:13 ` Pavel Machek
2016-04-18 11:42 ` Felipe Balbi
2016-04-18 12:58 ` Pavel Machek
2016-04-18 13:34 ` Felipe Balbi
2016-04-18 10:59 ` David Laight
2016-04-18 11:23 ` Pavel Machek
2016-03-31 8:03 ` Baolin Wang
2016-03-22 11:29 ` Pavel Machek
2016-04-18 8:18 ` Felipe Balbi
2016-04-18 10:33 ` Pavel Machek
2016-04-18 10:45 ` Felipe Balbi
2016-04-18 11:03 ` Pavel Machek
2016-04-18 11:51 ` Felipe Balbi
2016-04-18 13:16 ` Pavel Machek
2016-04-18 13:30 ` Felipe Balbi
[not found] ` <CAMz4kuJwfWPEndmVMoDBQQFZ2X8BAzDgej_9qMKQq0xU3tC=5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-31 8:18 ` Felipe Balbi
2016-03-31 8:35 ` Baolin Wang
2016-03-31 10:06 ` Felipe Balbi
2016-03-31 11:12 ` Baolin Wang
2016-03-31 17:06 ` Mark Brown
2016-04-01 5:43 ` Felipe Balbi
2016-04-01 14:16 ` Mark Brown
2016-04-04 10:47 ` Felipe Balbi
[not found] ` <877fgd7iqx.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-04 16:04 ` Mark Brown
2016-04-04 18:44 ` Greg KH
2016-03-16 11:46 ` [PATCH v7 2/4] gadget: Support for " Baolin Wang
2016-03-16 12:50 ` kbuild test robot
2016-03-16 20:19 ` kbuild test robot
2016-03-16 11:46 ` [PATCH v7 3/4] gadget: Integrate with the usb gadget supporting for usb charger Baolin Wang
2016-03-16 11:46 ` [PATCH v7 4/4] power: wm831x_power: Support USB charger current limit management Baolin Wang
2016-03-16 11:48 ` [PATCH v7 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Felipe Balbi
2016-03-16 11:56 ` Baolin Wang
-- strict thread matches above, loose matches on Subject: below --
2016-01-04 3:04 Baolin Wang
2016-01-04 3:04 ` [PATCH v7 1/4] gadget: Introduce the usb charger framework Baolin Wang
2015-12-08 8:36 [PATCH v7 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Baolin Wang
2015-12-08 8:36 ` [PATCH v7 1/4] gadget: Introduce the usb charger framework Baolin Wang
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=87vb43goag.fsf@intel.com \
--to=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dbaryshkov@gmail.com \
--cc=device-mainlining@lists.linuxfoundation.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=peter.chen@freescale.com \
--cc=r.baldyga@samsung.com \
--cc=sre@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=yoshihiro.shimoda.uh@renesas.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).