This patch introduces the use of the function usb_endpoint_is_bulk_in().
Signed-off-by: Shraddha Barke
---
Changes in v3:
-Change in commit message and add use of function usb_endpoint_is_bulk_in().
drivers/staging/ft1000/ft1000-usb/ft1000_usb.c | 8 ++--
1 file changed, 2
gt;
> Tested on MIPS with and without EVA, and on x86_64.
>
The series causes several build failures with other architectures.
>From next-20150806:
Build results:
total: 152 pass: 138 fail: 14
Failed builds:
alpha:allmodconfig (*)
arm:allmodconfig (*)
On Wed, Aug 05, 2015 at 05:02:08PM +0100, Srinivas Kandagatla wrote:
> A recursive lockdep warning occurs if you call regulator_set_voltage()
> on a load switches that are modelled as regulators with a parent supply as
> there is no nesting annotation for the rdev->mutex.
> To avoid this warning,
On 8/6/2015 1:04 AM, Benjamin Tissoires wrote:
On Jul 30 2015 or thereabouts, Sivakumar Thulasimani wrote:
On 7/29/2015 8:52 PM, Benjamin Tissoires wrote:
On Jul 29 2015 or thereabouts, Sivakumar Thulasimani wrote:
why not detect reverse in intel_dp_detect/intel_hpd_pulse ? that way you
Am 06.08.2015 um 11:19 schrieb Boris Brezillon:
>> I think this needs more discussion.
>>
>> Boris, Brian, will you be at Embedded Linux Conference Europe in Dublin?
>> Maybe we can discuss these issues (data retention, ff-checks, etc...) in
>> person and figure out where to address them.
>> I
Hi Richard,
On Tue, 4 Aug 2015 09:21:27 +0200
Richard Weinberger wrote:
> Andrea,
>
> Am 04.08.2015 um 09:02 schrieb Andrea Scian:
> >> I'm not sure whether introducing a read-before-write check is the best
> >> solution.
> >> At least we need hard numbers for slow/old SLC NANDs too.
> >
> >
On Thu, 2015-08-06 at 11:30 +0300, Heikki Krogerus wrote:
> > >
> On Wed, Aug 05, 2015 at 05:07:29PM +0300, Andy Shevchenko wrote:
> > On Wed, 2015-08-05 at 16:39 +0300, Heikki Krogerus wrote:
> > > +static inline enum rfkill_type rfkill_find_type(const char
> > > *name)
> > > +{
> > > + return
Commit 37868fe113ff ("x86/ldt: Make modify_ldt synchronous") introduced
a new struct ldt_struct anchored at mm->context.ldt.
Adapt the x86 fpu emulation to use that new structure.
Cc: # 37868fe113ff: x86/ldt: Make modify_ldt
synchronous
Cc: # a5b9e5a2f14f: x86/ldt: Make modify_ldt optional
I will format a patch based on your diff file firstly. I will test this on my
side,
If any issue, like dma issue or performance issue, I will add some modification.
Then I will send the patch for review, and you can test the patch on your
platform.
Best Regards
Haibo Chen
> -Original
On Thu, Aug 6, 2015 at 5:00 PM, James Liao wrote:
> Hi Sascha,
>
> On Thu, 2015-08-06 at 10:53 +0200, Sascha Hauer wrote:
>> On Thu, Aug 06, 2015 at 04:23:51PM +0800, James Liao wrote:
>> > On Wed, 2015-08-05 at 08:46 +0200, Sascha Hauer wrote:
>> > > On Tue, Aug 04, 2015 at 04:16:56PM +0800,
Please ignore, V3 coming soon.
Juergen
On 08/06/2015 11:07 AM, Juergen Gross wrote:
Commit 37868fe113ff ("x86/ldt: Make modify_ldt synchronous") introduced
a new struct ldt_struct anchored at mm->context.ldt.
Adapt the x86 fpu emulation to use that new structure.
Cc: # 37868fe113ff:
Migrate EP93xx driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
Signed-off-by: Viresh Kumar
---
Linus,
Commit 37868fe113ff ("x86/ldt: Make modify_ldt synchronous") introduced
a new struct ldt_struct anchored at mm->context.ldt.
Adapt the x86 fpu emulation to use that new structure.
Cc: # 37868fe113ff: x86/ldt: Make modify_ldt
synchronous
Cc: # a5b9e5a2f14f: x86/ldt: Make modify_ldt optional
On 08/06/2015, 09:42 AM, Chen Bough wrote:
> I read your attached log and patch, yes, dma memory leak will happen when
> more than one pre_request execute. The method of ++next->cookie is not good,
> your patch seems good, but I still need some time to test the patch, because
> you unmap the dma
> -Original Message-
> From: Shawn Lin [mailto:shawn@rock-chips.com]
> Sent: 06 August 2015 07:45 AM
> To: jh80.ch...@samsung.com; ulf.hans...@linaro.org
> Cc: he...@sntech.de; diand...@chromium.org; vineet.gup...@synopsys.com;
> Wei Xu; Joachim Eastwood; Alexey Brodkin; Kukjin Kim;
On Wed, Aug 05, 2015 at 02:56:09PM +0200, Michal Suchanek wrote:
> On 5 August 2015 at 14:44, Mark Brown wrote:
> > On Wed, Aug 05, 2015 at 02:40:01PM +0200, Michal Suchanek wrote:
> >> I don't think sending 03 or other random byte as the first byte of a
> >> SPI transfer can be used as reliable
Hi Sascha,
On Thu, 2015-08-06 at 10:53 +0200, Sascha Hauer wrote:
> On Thu, Aug 06, 2015 at 04:23:51PM +0800, James Liao wrote:
> > On Wed, 2015-08-05 at 08:46 +0200, Sascha Hauer wrote:
> > > On Tue, Aug 04, 2015 at 04:16:56PM +0800, James Liao wrote:
> > > > static const struct mtk_fixed_clk
On Thu, Aug 06, 2015 at 04:35:32PM +0800, James Liao wrote:
> Hi Sascha,
>
> On Wed, 2015-08-05 at 08:53 +0200, Sascha Hauer wrote:
> > On Tue, Aug 04, 2015 at 04:16:54PM +0800, James Liao wrote:
> > > -static const struct mtk_fixed_factor root_clk_alias[] __initconst = {
> > > -
On Wed, Aug 05, 2015 at 10:34:58AM +0900, Kamezawa Hiroyuki wrote:
> Reading discussion, I feel storing more data is difficult, too.
Yep, even with the current 16-bit memcg id. Things would get even worse
if we wanted to extend it one day (will we?)
>
> I wonder, rather than collecting more
Incoming packets in high speed are randomly corrupted by h/w
resulting in multiple errors. This workaround makes FS as
default mode in all affected socs by disabling HS chirp
signalling.This errata does not affect FS and LS mode.
Forces all HS devices to connect in FS mode for all socs
affected
On Thu, 2015-07-30 at 09:58 -0700, Jörn Engel wrote:
> On Thu, Jul 30, 2015 at 05:22:55PM +0200, Mike Galbraith wrote:
> >
> > I piddled about with the thought that it might be nice to be able to
> > sprinkle cond_resched() about to cut rt latencies without wrecking
> > normal load throughput,
This should have been removed by: 604cbe1de254 ("MIPS: loongson64/timer:
Migrate to new 'set-state' interface") commit, but it wasn't.
Remove it now.
Fixes: 604cbe1de254 ("MIPS: loongson64/timer: Migrate to new 'set-state'
interface")
Signed-off-by: Viresh Kumar
---
Ralf:
Not sure how it was
On Thu, Aug 06, 2015 at 04:23:51PM +0800, James Liao wrote:
> Hi Sascha,
>
> On Wed, 2015-08-05 at 08:46 +0200, Sascha Hauer wrote:
> > On Tue, Aug 04, 2015 at 04:16:56PM +0800, James Liao wrote:
> > > static const struct mtk_fixed_clk fixed_clks[] __initconst = {
> > >
* Kishon Vijay Abraham I [150805 07:28]:
> Hi Roger,
>
> On Wednesday 05 August 2015 01:38 PM, Roger Quadros wrote:
> > On 05/08/15 11:02, Roger Quadros wrote:
> >> Kishon,
> >>
> >> On 04/08/15 18:30, Kishon Vijay Abraham I wrote:
> >>> Add "syscon-otghs" property and remove the deprecated
* Kishon Vijay Abraham I [150805 07:10]:
> On Wednesday 05 August 2015 01:31 PM, Tony Lindgren wrote:
> >
> > We don't have syscon-otghs and to me it seems we need a PHY driver
> > as I pointed out at:
>
> If *syscon-otghs* is not present, then it'll fall-back to using the
> *ctrl-module*.
OK
Hi Olof,
On 05/08/15 10:59, Sudeep Holla wrote:
Hi Olof,
On 31/07/15 18:43, Sudeep Holla wrote:
Hi ARM-SoC guys,
It has been on the list for a while and have got all the necessary
ACKs. Can you please pull this series for v4.3 ?
Can you pull this patch series directly from the mail or do
Hi Guys,
There are about 3 advantages to use direct I/O and AIO on
read/write loop's backing file:
1) double cache can be avoided, then memory usage gets
decreased a lot
2) not like user space direct I/O, there isn't cost of
pinning pages
3) avoid context switch for obtaining good throughput
-
When direct read IO is submitted from kernel, it is often
unnecessary to dirty pages, for example of loop, dirtying pages
have been considered in the upper filesystem(over loop) side
already, and they don't need to be dirtied again.
So this patch doesn't dirtying pages for ITER_BVEC/ITER_KVEC
This patches provides one interface for enabling direct IO
from user space:
- userspace(such as losetup) can pass 'file' which is
opened/fcntl as O_DIRECT
Also __loop_update_dio() is introduced to check if direct I/O
can be used on current loop setting.
The last big change is to
It doesn't make sense to enable merge because the I/O
submitted to backing file is handled page by page.
Signed-off-by: Ming Lei
---
drivers/block/loop.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index f9889b6..eee7510 100644
---
If loop block is mounted via 'mount -o loop', it isn't easy
to pass file descriptor opened as O_DIRECT, so this patch
introduces a new command to support direct IO for this case.
Cc: linux-...@vger.kernel.org
Signed-off-by: Ming Lei
---
drivers/block/loop.c | 19 +++
The compatible "atmel,sama5d4-wdt" supports the SAMA5D4 watchdog driver
and the watchdog's WDT_MR register can be written more than once.
Signed-off-by: Wenyou Yang
---
.../bindings/watchdog/atmel-sama5d4-wdt.txt| 35
1 file changed, 35 insertions(+)
create mode
There are about 3 advantages to use direct I/O and AIO on
read/write loop's backing file:
1) double cache can be avoided, then memory usage gets
decreased a lot
2) not like user space direct I/O, there isn't cost of
pinning pages
3) avoid context switch for obtaining good throughput
- in
>From SAMA5D4, the watchdog timer is upgrated with a new feature,
which is describled as in the datasheet, "WDT_MR can be written
until a LOCKMR command is issued in WDT_CR".
That is to say, as long as the bootstrap and u-boot don't issue
a LOCKMR command, WDT_MR can be written more than once in
The following patch will use dio/aio to submit IO to backing file,
then it needn't to schedule IO concurrently from work, so
use kthread_work for decreasing context switch cost a lot.
For non-AIO case, single thread has been used for long long time,
and it was just converted to work in v4.0,
Hello,
Because the watchdog WDT_MR register can be written more than once,
its work mechanism is different from the at91sam9260 watchdog driver.
Open the device file to enable the watchdog hardware, close to disable it,
and ping it from the user space directly to keep it alive.
Changes from v4.0
Hi Sascha,
On Wed, 2015-08-05 at 08:53 +0200, Sascha Hauer wrote:
> On Tue, Aug 04, 2015 at 04:16:54PM +0800, James Liao wrote:
> > -static const struct mtk_fixed_factor root_clk_alias[] __initconst = {
> > - FACTOR(CLK_TOP_CLKPH_MCK_O, "clkph_mck_o", "clk_null", 1, 1),
> > -
On Wed, Aug 05, 2015 at 05:07:29PM +0300, Andy Shevchenko wrote:
> On Wed, 2015-08-05 at 16:39 +0300, Heikki Krogerus wrote:
> > Helper for finding the type based on name. Useful if the
> > type needs to be determined based on device property.
> >
> > Signed-off-by: Heikki Krogerus
> > ---
> >
Hello,
On Thu, Aug 06, 2015 at 10:31:00AM +0200, Uwe Kleine-König wrote:
> From: Uwe Kleine-König
grumpf, I forgot to fix the author, only adapted the s-o-b-line. Greg,
can you fix this on application?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König
On Wed, 5 Aug 2015 13:51:21 -0700
Greg Kroah-Hartman wrote:
> On Thu, Jul 30, 2015 at 08:35:51PM +0200, Michael Holzheu wrote:
> > Hello Greg,
> >
> > Is it possible to use "from_nid = cpu->node_id"?
> >
> > Background:
> >
> > I am currently working on (fake) NUMA support for s390. At
From: Uwe Kleine-König
When a platform driver doesn't provide a .remove callback the function
platform_drv_remove isn't called and so the call to dev_pm_domain_attach
called at probe time isn't paired by dev_pm_domain_detach at remove
time.
To fix this (and similar issues if different callbacks
On Wed, Aug 05, 2015 at 07:49:41PM +0100, Eduardo Valentin wrote:
> On Wed, Aug 05, 2015 at 09:35:39AM -0700, Dmitry Torokhov wrote:
> > On Wed, Aug 05, 2015 at 09:37:55AM +0100, Javi Merino wrote:
> > > On Tue, Aug 04, 2015 at 05:39:21PM +0100, Dmitry Torokhov wrote:
> > > > As it currently
* Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
> > On Aug 6, 2015 10:15 AM, "Ingo Molnar" wrote:
> > >
> > > What sense does it make to have a blob we don't know the exact layout of?
> > > How
> > > will debuggers or user-space in general be able to print (and change) the
> > >
On Wednesday 05 August 2015 11:05:39 Andrew F. Davis wrote:
> Add support for additional devices and register equivalent family devices
> including the bq27010, bq27210, bq27500, bq27510, bq27520, bq27530,
> bq27531, bq27541, bq27542, bq27546, bq27545, bq27441, bq27421, and the
> bq27641.
>
> To
Hi Greg
A set of fixes for kdbus-next. Nothing critical, just small improvements. See
each commit for a detailed description. No API changes apart from a modified
error code to improve debug features. All user-space has been already audited
for that.
Thanks
David
David Herrmann (9):
kdbus:
If you send a reply without an active reply slot, we used to return EPERM.
However, this makes it impossible to distinguish this case from a real
permission-denied error (eg., LSM). Hence, make sure we return a unique
error-code if the reply-slot is missing.
With this patch, you get EBADSLT
This reduces the stack-buffer for small ioctl payloads to 256 bytes. As
seen during real workloads, this is more than enough. And we really
should reduce stack pressure. Hence, lets limit the stack buffers to 256
bytes.
Reported-by: Dan Carpenter
Reviewed-by: Daniel Mack
Signed-off-by: David
* Linus Torvalds wrote:
> On Aug 6, 2015 10:15 AM, "Ingo Molnar" wrote:
> >
> > What sense does it make to have a blob we don't know the exact layout of?
> > How
> > will debuggers or user-space in general be able to print (and change) the
> > register values if they don't know the layout?
On Mon, Aug 03, 2015 at 09:24:45PM +0200, Sebastian Hesselbarth wrote:
> From: Jisheng Zhang
>
> This patch introduces ARCH_BERLIN to enable Marvell Berlin SoC family in
> Kconfig.
>
> Signed-off-by: Jisheng Zhang
> Signed-off-by: Sebastian Hesselbarth
> ---
> As discussed with Olof on IRC,
On Mon, Aug 03, 2015 at 09:24:46PM +0200, Sebastian Hesselbarth wrote:
> From: Jisheng Zhang
>
> Enable Marvell Berlin SoC family in arm64 defconfig.
>
> Signed-off-by: Jisheng Zhang
> Signed-off-by: Sebastian Hesselbarth
> ---
> Also discussed with Olof on IRC, this is the defconfig changes
If a connection proxies a uid, we should make sure to perform accounting
on that passed uid. Otherwise, limits will be shared across all proxied
users (or we'd require the proxy to run setuid() and thus require
CAP_SETUID).
However, this is only allowed if the proxy is privileged on the bus. That
Am Donnerstag, 6. August 2015, 10:04:57 schrieb David Herrmann:
> > Given that all existing prototype userspace that I'm aware of
> >
> > (systemd and its consumers) apparently opts in, I don't really care
> > that the feature is opt-in.
>
> This is just plain wrong. Out of the dozens of
Instead of relying on handle.c to perform privilege evaluation and
passing information along, move this into kdbus_conn_new(). This has the
benefit that we can now split 'owner' level and 'privileged' levels
apart. This will be required for following extensions that need to
distinguish both cases.
Move the file-credential checkers into kdbus_ep_*() helper functions to
avoid hard-coding the same behavior in multiple places.
Signed-off-by: David Herrmann
---
ipc/kdbus/connection.c | 20 ++--
ipc/kdbus/endpoint.c | 28
ipc/kdbus/endpoint.h |
Hi Sascha,
On Wed, 2015-08-05 at 08:46 +0200, Sascha Hauer wrote:
> On Tue, Aug 04, 2015 at 04:16:56PM +0800, James Liao wrote:
> > static const struct mtk_fixed_clk fixed_clks[] __initconst = {
> > FIXED_CLK(CLK_TOP_CLKPH_MCK_O, "clkph_mck_o", "clk26m", 400 * MHZ),
> >
Instead of caching privilege information in 'kdbus_handle' (and thus
increasing the size of each handle by 8 byte), perform privilege checks
on the cached creds in file->f_cred inline. None of the functions that
need those checks is a fast path (in fact, it's just EP_MAKE that needs
it right now),
On Tue, 2015-08-04 at 18:12 +0100, David Vrabel wrote:
> On 04/08/15 17:41, Jason A. Donenfeld wrote:
> > Hi folks,
> >
> > Paul McKenney and I had an offline discussion about some rcu questions
> > that eventually lead into me investigating a strange full lock-up I'm
> > experiencing as a
There is no reason to assume the information returned by KDBUS_CMD_LIST
contains only a single KDBUS_ITEM_OWNED_NAME. Parse each of them properly
and don't bail out early.
Reviewed-by: Daniel Mack
Signed-off-by: David Herrmann
---
tools/testing/selftests/kdbus/kdbus-util.c | 9 +
We require __NR_memfd_create for the kdbus samples. Make sure we skip
compilation if the target architecture and kernel do not support memfds.
Reported-by: Paul Gortmaker
Reviewed-by: Daniel Mack
Signed-off-by: David Herrmann
---
samples/kdbus/kdbus-workers.c | 5 +++--
1 file changed, 3
For each kdbus domain, we maintain an ID-counter to guarantee unique IDs
across all objects. We also used to use it for message IDs. However, this
requires touching a shared cacheline on each message transaction, even
though we never guaranteed global ordering across buses, anyway.
Introduce a
Hi Guenter,
Thank you for your correct.
> -Original Message-
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: 2015年8月6日 16:05
> To: Yang, Wenyou; w...@iguana.be; robh...@kernel.org; pawel.m...@arm.com;
> mark.rutl...@arm.com; ijc+devicet...@hellion.org.uk; ga...@codeaurora.org
>
On 31/07/15 19:03, Stephen Boyd wrote:
> We're removing struct clk from the clk provider API, so switch
> this code to using the clk_hw based provider APIs.
>
> Cc: Chanwoo Choi
> Cc: Sylwester Nawrocki
> Cc: Krzysztof Kozlowski
> Cc: Kukjin Kim
> Signed-off-by: Stephen Boyd
Acked-by:
Hi Toshi,
Does this patch work for you?
There are things I am not sure. When jump to kexec/kdump kernel is this
PMEM still needed by system? And what's the difference between PRAM and
PMEM? I saw in kernel commit ec776ef6 it introduced E820_PRAM for the
non-standard protected e820 type, then in
After try to drain pages from pagevec/pageset, we try to get reference
count of the page again, however, the reference count of the page is
not reduced if the page is still not on LRU list. This patch fix it by
adding the put_page() to drop the page reference which is from
__get_any_page().
On 31/07/15 19:03, Stephen Boyd wrote:
> diff --git a/drivers/clk/mmp/clk-mix.c b/drivers/clk/mmp/clk-mix.c
> index 665cb6794639..8653e555c920 100644
> --- a/drivers/clk/mmp/clk-mix.c
> +++ b/drivers/clk/mmp/clk-mix.c
> @@ -63,7 +63,7 @@ static unsigned int _get_div(struct mmp_clk_mix *mix,
>
On Thu, Aug 06, 2015 at 02:02:30AM +0800, Daniel Kurtz wrote:
>
> > +
> > +#define THERMAL_NAME"mtk-thermal"
> > +
> > +struct mtk_thermal;
> > +
> > +struct mtk_thermal_bank {
> > + struct mtk_thermal *mt;
> > + struct thermal_zone_device *tz;
>
> A better name for this field is
> Take a look at linkwatch_urgent_event at net/core/link_watch.c, and all
>of
> link_watch.c in general. That's where the 1s delay comes from.
Thanks for the diagnosis, I¹ll take a look.
-Shaun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
* Josh Poimboeuf wrote:
> This is v8 of the compile-time stack validation patch set, based on the
> tip/master branch.
>
> The frame pointer macros are still called FRAME and ENDFRAME because I
> don't think we converged on anything else yet. Otherwise I tried to
> address all the other
On Wed, Aug 05, 2015 at 05:17:13PM -0700, Joshua Clayton wrote:
> I posted v4 of this patch set a week ago and there have been no
> comments. I hope this is a good sign that the patches are good.
> However, I have noticed that I managed to use the same message id
> for the coverletter of v4 as
On 05/08/15 18:07, nick wrote:
>
>
> On 2015-08-05 12:59 PM, Paolo Bonzini wrote:
>>
>>
>> On 05/08/2015 18:48, Nicholas Krause wrote:
>>> This fixes the error handling in the function vgic_v3_probe
>>> for when calling the function kvm_register_device_ops to check
>>> if the call to this
Commit 37868fe113ff ("x86/ldt: Make modify_ldt synchronous") introduced
a new struct ldt_struct anchored at mm->context.ldt.
convert_ip_to_linear() was changed to reflect this, but indexing into
the ldt has to be changed as the pointer is no longer void *.
Cc: # 37868fe113ff: x86/ldt: Make
On 08/05/2015 09:59 PM, Wenyou Yang wrote:
From SAMA5D4, the watchdog timer is upgrated with a new feature,
which is describled as in the datasheet, "WDT_MR can be written
until a LOCKMR command is issued in WDT_CR".
That is to say, as long as the bootstrap and u-boot don't issue
a LOCKMR
Hi
On Wed, Aug 5, 2015 at 10:11 PM, Andy Lutomirski wrote:
> On Wed, Aug 5, 2015 at 12:10 AM, David Herrmann wrote:
>> Hi
>>
>> On Tue, Aug 4, 2015 at 4:47 PM, Andy Lutomirski wrote:
>>> On Tue, Aug 4, 2015 at 7:09 AM, David Herrmann
>>> wrote:
This is a bug in the proxy (which is
Add callback that is called by epautoconf to allow UDC driver match the
best endpoint for specific descriptor. It's intended to supply mechanism
which allows to get rid of chip-specific endpoint matching code from
epautoconf.
If gadget has set 'ep_match' callback we prefer to call it first, and
Move find_ep() to udc-core and rename it to gadget_find_ep_by_name().
It can be used in UDC drivers, especially in 'match_ep' callback after
moving chip-specific endpoint matching logic from epautoconf to UDC
drivers.
Replace all calls of find_ep() function with gadget_find_ep_by_name().
This header file contains helpers for quirks based on UDC controller name.
Since we have generic quirk bitfields in usb_gadget structure for all of
these quirks we don't need to have this header any longer.
This patch removes gadget_chips.h file and makes sure that it's no longer
included
Add 'match_ep' callback to utilize chip-specific knowledge in endpoint matching
process. Function does the same that was done by chip-specific code inside
of epautoconf. Now this code can be removed from there to separate generic code
from platform specific logic.
Signed-off-by: Robert Baldyga
Add 'match_ep' callback to utilize chip-specific knowledge in endpoint matching
process. Function does the same that was done by chip-specific code inside
of epautoconf. Now this code can be removed from there to separate generic code
from platform specific logic.
Signed-off-by: Robert Baldyga
Move ep_matches() function to udc-core and rename it to
usb_gadget_ep_match_desc(). This function can be used by UDC drivers
in 'match_ep' callback to avoid writing lots of repetitive code.
Replace all calls of ep_matches() with usb_gadget_ep_match_desc().
Signed-off-by: Robert Baldyga
---
Hi Felipe,
These are remaining patches of my series plus one which remained from
series [1].
In this version of this patch set I have changed gadget_find_ep_by_name()
to exported symbol, as Alan suggested.
[1] usb: gadget: get rid of UDC name-based quirks
https://lkml.org/lkml/2015/7/28/29
Add 'match_ep' callback to utilize chip-specific knowledge in endpoint matching
process. Function does the same that was done by chip-specific code inside
of epautoconf. Now this code can be removed from there to separate generic code
from platform specific logic.
Signed-off-by: Robert Baldyga
Rework ep_matches() function to make it shorter and more readable.
Signed-off-by: Robert Baldyga
---
drivers/usb/gadget/epautoconf.c | 81 -
1 file changed, 32 insertions(+), 49 deletions(-)
diff --git a/drivers/usb/gadget/epautoconf.c
On 05/08/15 17:51, Mark Rutland wrote:
> Rob,
>
> Do you have any objections to this, or are you happy to take this patch?
>
> There's a user of this binding (the GICv3 ITS) queued for v4.3 already in
> the tip tree, so either we either need to be ok with this binding or we
> need to rework that
On 08/06/2015 06:24 AM, Dave Chinner wrote:
> On Wed, Aug 05, 2015 at 09:42:54PM -0400, Linda Knippers wrote:
>> On 08/05/2015 06:01 PM, Dave Chinner wrote:
>>> On Wed, Aug 05, 2015 at 04:19:08PM -0400, Jeff Moyer wrote:
<>
I sat down with Linda to look into it, and the problem is that
2015-08-06 16:35 GMT+09:00 Krzysztof Kozlowski :
> On 06.08.2015 16:29, Srinivas Kandagatla wrote:
>> Thanks Krzysztof
>>
>> On 06/08/15 02:39, Krzysztof Kozlowski wrote:
--- a/drivers/regulator/core.c
>+++ b/drivers/regulator/core.c
>@@ -2919,7 +2919,7 @@ static int
On Wed, Aug 05, 2015 at 05:02:18PM +0300, Andy Shevchenko wrote:
> On Wed, 2015-08-05 at 16:39 +0300, Heikki Krogerus wrote:
> > Marcos for easier creation of build-in property entries.
> >
> > Signed-off-by: Heikki Krogerus
> > ---
> > include/linux/property.h | 35
On Wed, Aug 05, 2015 at 07:18:44PM -0700, David Rientjes wrote:
...
> Hmm, wouldn't this be confusing since VmRSS in /proc/pid/status doesn't
> match the rss shown in smaps, since hugetlb mappings aren't accounted in
> get_mm_rss()?
>
> Not sure this is a good idea, I think consistency amongst
Hi Js,
I read your attached log and patch, yes, dma memory leak will happen when
more than one pre_request execute. The method of ++next->cookie is not good,
your patch seems good, but I still need some time to test the patch, because
you unmap the dma in sdhci_finish_data rather than the
On 06.08.2015 16:26, Shawn Lin wrote:
> 在 2015/8/6 15:08, Krzysztof Kozlowski 写道:
>> On 06.08.2015 15:44, Shawn Lin wrote:
>>> DesignWare MMC Controller can supports two types of DMA
>>> mode: external dma and internal dma. We get a RK312x platform
>>> integrated dw_mmc and ARM pl330 dma
On 06.08.2015 16:29, Srinivas Kandagatla wrote:
> Thanks Krzysztof
>
> On 06/08/15 02:39, Krzysztof Kozlowski wrote:
>>> --- a/drivers/regulator/core.c
>>> >+++ b/drivers/regulator/core.c
>>> >@@ -2919,7 +2919,7 @@ static int _regulator_get_voltage(struct
>>> regulator_dev *rdev)
>>> > }
+ linux-iio.
On Wed, Aug 5, 2015 at 8:09 PM, Cristina Opriceana
wrote:
> This patch adds an entry in the ABI Documentation for the
> name attribute issued when a trigger is created.
>
> Signed-off-by: Cristina Opriceana
> ---
> Documentation/ABI/testing/sysfs-bus-iio-trigger-sysfs | 9
On 08/06/2015 04:31 PM, Shawn Lin wrote:
> 在 2015/8/6 15:08, Jaehoon Chung 写道:
>> Hi, Shawn.
>>
>> I remembered that Krzysztof has mentioned "Fix the title of cover letter."
>> Your cover letter's title is nothing.. "[RFC PATCH v4 0/9] " ??
>> [RFC PATCH v4 0/9] your title...
> Sorry, I forgot
在 2015/8/6 15:08, Jaehoon Chung 写道:
Hi, Shawn.
I remembered that Krzysztof has mentioned "Fix the title of cover letter."
Your cover letter's title is nothing.. "[RFC PATCH v4 0/9] " ??
[RFC PATCH v4 0/9] your title...
Sorry, I forgot it, and will fix in next version...
Best Regards,
Thanks Krzysztof
On 06/08/15 02:39, Krzysztof Kozlowski wrote:
--- a/drivers/regulator/core.c
>+++ b/drivers/regulator/core.c
>@@ -2919,7 +2919,7 @@ static int _regulator_get_voltage(struct regulator_dev
*rdev)
> } else if (rdev->desc->fixed_uV && (rdev->desc->n_voltages == 1)) {
>
Hi all,
Changes since 20150805:
The slave-dma tree gained a build failure so I used the version from
next-20150805.
The crypto tree lost its build failure.
The akpm-current tree gained a conflict against the char-misc tree and
a build failure for which I reverted a commit.
Non-merge commits
在 2015/8/6 15:08, Krzysztof Kozlowski 写道:
On 06.08.2015 15:44, Shawn Lin wrote:
DesignWare MMC Controller can supports two types of DMA
mode: external dma and internal dma. We get a RK312x platform
integrated dw_mmc and ARM pl330 dma controller. This patch add
edmac ops to support these
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
allyesconfig) failed like this:
lib/test_user_copy.c: In function 'test_user_copy_init':
lib/test_user_copy.c:111:2: error: implicit declaration of function
'csum_partial_copy_from_user'
On Wed, 5 Aug 2015, Sergey Senozhatsky wrote:
>
> Hi,
>
> Cc Julia Lawall
>
> On (08/04/15 13:06), Brian Norris wrote:
> > On Tue, Aug 04, 2015 at 08:46:30PM +0100, Salah Triki wrote:
> > > kmem_cache_destroy can be called with NULL values. Thus, the checks that
> > > precede the calls are
On Wed, Aug 05, 2015 at 05:15:28PM +0300, Andy Shevchenko wrote:
> On Wed, 2015-08-05 at 16:39 +0300, Heikki Krogerus wrote:
> > No more users for it.
> >
> > Signed-off-by: Heikki Krogerus
> > ---
> > include/linux/rfkill-gpio.h | 37 ---
> > --
> >
When occur i2c ack error, i2c controller generate two interrupts,
first is the ack error interrupt, then the complete interrupt.
i2c interrupt handler should keep the two interrupt value, and only
call complete() for the complete interrupt.
Signed-off-by: Liguo Zhang
Signed-off-by: Eddie Huang
701 - 800 of 1714 matches
Mail list logo
