Hey,
On Mon, 2015-10-12 at 18:24 +0300, Irina Tirdea wrote:
> v9 only adds GPIOLIB dependency in Kconfig for patch 2:
> "Input: goodix - reset device at init". There are no other code
> changes from v8.
>
> Thanks for testing these changes, Bastien and Aleksei!
>
> Karsten, there is no need to r
In the case of memory error injection, einj_error_inject() checks
if a target address is regular RAM. Update this check to add a call
to region_intersects_pmem() to verify if a target address range is
NVDIMM. This allows injecting a memory error to both RAM and NVDIMM
for testing.
Also, the curr
> 2015-09-13 23:52 GMT+09:00 Yaniv Gardi :
>> We put the UFS device in sleep state & UFS link in hibern8 state during
>> runtime suspaned. After this we put all the UFS rails in low power
>> modes immediately but it seems some devices may still draw more than
>> sleep current from UFS rails (especi
On 10/25/2015 5:37 AM, Borislav Petkov wrote:
On Fri, Oct 23, 2015 at 06:18:33AM -0500, Aravind Gopalakrishnan wrote:
CLZERO instruction introduced in AMD Fam17h processors
zero's out a 64 byte cache line specified in RAX.
Add the bit here to allow /proc/cpuinfo to list the feature
Signed-off-
On Mon, 2015-10-26 at 14:55 +0100, Vitaly Kuznetsov wrote:
> Add a couple of simple tests for string_get_size().
>
In linux-next this one (or similar?) is commit 29f3d140.
I don't think you need it in the series since it's in Andrew's patch
set already.
> Signed-off-by: Vitaly Kuznetsov
> ---
(removing peter.p.waskiewicz...@intel.com as email bounced)
On 10/25/2015 5:37 AM, Borislav Petkov wrote:
On Fri, Oct 23, 2015 at 06:18:33AM -0500, Aravind Gopalakrishnan wrote:
CLZERO instruction introduced in AMD Fam17h processors
zero's out a 64 byte cache line specified in RAX.
Add the bit
Andy Shevchenko writes:
> On Mon, 2015-10-26 at 14:55 +0100, Vitaly Kuznetsov wrote:
>> Add a couple of simple tests for string_get_size().
>>
>
> In linux-next this one (or similar?) is commit 29f3d140.
> I don't think you need it in the series since it's in Andrew's patch
> set already.
>
Ah,
Dereference was modified to dereferenced, as it made more sense.
Signed-off-by: Muhammad Falak R Wani
---
scripts/coccinelle/null/deref_null.cocci | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/coccinelle/null/deref_null.cocci
b/scripts/coccinelle/null/deref_null.co
On Mon, 2015-10-26 at 16:18 +0100, Vitaly Kuznetsov wrote:
> Andy Shevchenko writes:
>
> > On Mon, 2015-10-26 at 14:55 +0100, Vitaly Kuznetsov wrote:
> > > Add a couple of simple tests for string_get_size().
> > >
> >
> > In linux-next this one (or similar?) is commit 29f3d140.
> > I don't thin
On 09/12/2015 11:59 AM, Ingo Molnar wrote:
>
> * Davidlohr Bueso wrote:
>
>> I think we should leave it as is.
>
> But ... given that these are shared-cached values (cached on all CPUs), this
> change would only be measurable in such a benchmark if the cache footprint of
> the
> test is just
The type of ntp static variant "time_reftime" and the type of get_seconds()'s
return value are both unsign long now, which may cause y2038 problem on 32bit
systems.
So change time_reftime' type to time64_t, and replace get_seconds with
ktime_get_real_seconds() in ntp.
ktime_get_real_seconds() doe
In order to fix Y2038 issues in the ntp code we will need replace
get_seconds() with ktime_get_real_seconds() but as the ntp code uses
the timekeeping lock which is also used by ktime_get_real_seconds(),
we need a version without locking.
Add a new function __ktime_get_real_seconds() in timekeepin
Acked-by: Julia Lawall
Thanks for the correction!
On Mon, 26 Oct 2015, Muhammad Falak R Wani wrote:
> Dereference was modified to dereferenced, as it made more sense.
>
> Signed-off-by: Muhammad Falak R Wani
> ---
> scripts/coccinelle/null/deref_null.cocci | 2 +-
> 1 file changed, 1 insertio
On Sun, Oct 25, 2015 at 03:50:59PM -0700, Guenter Roeck wrote:
> Function get_cmos_time() was removed with commit 657926a83df9 ("cris:
> time: Cleanup of persistent clock stuff"). The remaining reference to
> it may cause the following build error.
>
> arch/cris/kernel/built-in.o:(___ksymtab+get_c
The type of static variant "time_reftime" and the call of get_seconds
in ntp are both not y2038 safe.
So change the type of time_reftime to time64_t and replace get_seconds
with __ktime_get_real_seconds.
The local variant "secs" in ntp_update_offset represents seconds between
now and last ntp adjus
On Fri, Oct 23, 2015 at 04:59:33PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Move the running/noise printing into printout to avoid
> duplicated code in the callers.
>
> v2: Merged with other patches. Remove unnecessary hunk.
> Readd hunk that ended in earlier patch.
> Signed-off-by: Andi
A race condition exists between request requeueing and scsi layer
error handling:
When UFS driver queuecommand returns a busy status for a request,
it will be requeued and its tag will be freed and set to -1.
At the same time it is possible that the request will timeout and
scsi layer will start er
When control reaches to Linux UFS driver during UFS boot mode, UFS host
controller interrupt status/enable registers may have left over
settings.
In order to avoid any spurious interrupts due to these left overs,
it's important to clear these interrupt status/enable registers before
enabling UFS in
UFS driver's error handler forcefully tries to clear all the pending
requests. For each pending request in the queue, it waits 1 sec for it
to get cleared. If we have multiple requests in the queue then it's
possible that we might end up waiting for those many seconds before
resetting the host. But
Currently we use the host quirks mechanism in order to
handle both device and host controller quirks.
In order to support various of UFS devices we should separate
handling the device quirks from the host controller's.
Signed-off-by: Raviv Shvili
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs
We are seeing that some devices are raising the urgent bkops exception
events even when BKOPS status doesn't indicate performace impacted or
critical. Handle these device by determining their urgent bkops status
at runtime.
Signed-off-by: Subhash Jadavani
Signed-off-by: Yaniv Gardi
---
drivers
Currently when we try to put the link in off/disabled state during
suspend, it seems link is not being kept in low power mode.
This patch fixes the issue by putting the link in hibern8 first
(so device also puts the link in low power mode) and then stop the
host controller.
Signed-off-by: Subhash
Some UFS devices (and may be host) have issues if LCC is
enabled. So we are setting PA_Local_TX_LCC_Enable to 0
before link startup which will make sure that both host
and device TX LCC are disabled once link startup is
completed.
This change also:
- enables the device ref clock before changing to
Tnis patch fixes the following compilation warnings:
...ufs-qcom.c:1201:40:
warning: incorrect type in argument 1 (different address spaces)
...ufs-qcom.c:1201:40:
expected void const *ptr
...ufs-qcom.c:1201:40:
got void [noderef] *dev_ref_clk_ctrl_mmio
...ufs-qcom.c:1207:53
We put the UFS device in sleep state & UFS link in hibern8 state during
runtime suspaned. After this we put all the UFS rails in low power
modes immediately but it seems some devices may still draw more than
sleep current from UFS rails (especially from VCCQ rail) atleast for
500us.
To avoid this s
Some vendor's UFS device sends back to back NACs for the DL data frames
causing the host controller to raise the DFES error status. Sometimes
such UFS devices send back to back NAC without waiting for new
retransmitted DL frame from the host and in such cases it might be
possible the Host UniPro go
Optimal values of local UniPro parameters like PA_Hibern8Time &
PA_TActivate can help reduce the hibern8 exit latency. If both host and
device supports UniPro ver1.6 or later, these parameters will be
automatically tuned during link startup itself. But if either host or
device doesn't support UniPr
Query commands have 100ms timeout and it may timeout if they are
issued in parallel to ongoing read/write SCSI commands, this change
adds the retry (max: 10) in case command timeouts.
Signed-off-by: Subhash Jadavani
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufshcd.c | 55
UFS device and link can be put in multiple different low power modes
hence UFS driver supports multiple different low power modes.
By default UFS driver selects the default (optimal) low power mode
(which gives moderate power savings and have relatively less enter
and exit latencies) but we might h
Consider following sequence of events:
1. UFS is runtime suspended, link_state = Hibern8, device_state = sleep
2. System goes into system suspend, ufshcd_system_suspend() brings both
link and device to active state and then puts the device in
Power_Down state and link in OFF state.
3. System
Some UFS devices don't require VCCQ rail for device operations hence
this change adds support to recognize such devices and remove vote for
the unused VCCQ rail.
Signed-off-by: Subhash Jadavani
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs.h| 1 +
drivers/scsi/ufs/ufshcd.c | 60
Sometimes due to hw issues it takes some time to the
host controller register to update. In order to verify the register
has updated, a polling is done until its value is set.
In addition the functions ufshcd_hba_stop() and
ufshcd_wait_for_register() was updated with an additional input
parameter,
Different platform may have different number of lanes
for the UFS link.
Add parameter to device tree specifying how many lanes
should be configured for the UFS link.
Signed-off-by: Gilad Broner
Signed-off-by: Yaniv Gardi
---
.../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 3 ++
drivers/s
Correct `arch_check_elf's description, mistakenly copied and pasted from
`arch_elf_pt_proc'.
Signed-off-by: Maciej W. Rozycki
---
Hi,
This is obviously correct, any chance to have it included in 4.4?
Maciej
linux-arch-check-elf-doc-fix.diff
Index: linux-org-test/fs/binfmt_elf.c
===
Do not clobber the buffer space passed from `search_binary_handler' and
originally preloaded by `prepare_binprm' with the executable's file
header by overwriting it with its interpreter's file header. Instead
keep the buffer space intact and directly use the data structure locally
allocated fo
On 10/25/2015 07:43 PM, Mark Brown wrote:
On Sun, Oct 25, 2015 at 03:45:43PM -0500, Andrew F. Davis wrote:
On 10/24/2015 05:14 PM, Mark Brown wrote:
Tbe binding document is buggy and doesn't reflect the code, there's no
compatible string in the driver.
Sure there is:
drivers/mfd/mt6397-
Andy Shevchenko writes:
> On Mon, 2015-10-26 at 16:18 +0100, Vitaly Kuznetsov wrote:
>> Andy Shevchenko writes:
>>
>> > On Mon, 2015-10-26 at 14:55 +0100, Vitaly Kuznetsov wrote:
>> > > Add a couple of simple tests for string_get_size().
>> > >
>> >
>> > In linux-next this one (or similar?) i
> -Original Message-
> From: Lijun Pan [mailto:lijun@freescale.com]
> Sent: Sunday, October 25, 2015 5:41 PM
> To: gre...@linuxfoundation.org; a...@arndb.de; de...@driverdev.osuosl.org;
> linux-kernel@vger.kernel.org
> Cc: Yoder Stuart-B08248; katz Itai-RM05202; Rivera Jose-B46482; L
V2:
This series should be pushed on top of 15 patches series:
"Big fixes, retries, handle a race condition"
fixed and few comments.
V1:
This series should be pushed on top of 15 patches series:
"Big fixes, retries, handle a race condition"
Yaniv Gardi (17):
scsi: ufs-qcom: add number of lanes p
On Fri, Oct 23, 2015 at 05:02:30PM -0400, Aristeu Rozanski wrote:
> One of the largest chunks of log messages in a OOM is from dump_stack() and in
> some cases it isn't even necessary to figure out what's going on. In
> systems with multiple tenants/containers with limited resources each
> OOMs can
Added platform-specific MSI support layer for FSL-MC devices.
Signed-off-by: J. German Rivera
---
drivers/staging/fsl-mc/bus/Makefile| 1 +
.../staging/fsl-mc/bus/irq-gic-v3-its-fsl-mc-msi.c | 127 +
drivers/staging/fsl-mc/include/mc-private.h| 4 +
Created an MSI domain for the fsl-mc bus-- including functions
to create a domain, find a domain, alloc/free domain irqs, and
bus specific overrides for domain and irq_chip ops.
Signed-off-by: J. German Rivera
---
drivers/staging/fsl-mc/bus/Kconfig | 1 +
drivers/staging/fsl-mc/bus/Ma
This patch series addresses the following item from the TODO list
for the MC bus driver to exit staging:
* Interrupt support. For meaningful driver support we need
interrupts, and thus need message interrupt support by the bus
driver.
MC Bus MSI Support Architecture
==
On Mon, Aug 31, 2015 at 06:13:03PM -0400, j.gli...@gmail.com wrote:
> From: Jérôme Glisse
>
> Fix amd_iommu_detect() to return positive value on success, like
> intended, and not zero. This will not change anything in the end
> as AMD IOMMU disable swiotlb and properly associate itself with
Not
Initialize/Cleanup ITS-MSI support for the MC bus driver at driver
init/exit time. Associate an MSI domain with each DPAA2 child device.
Signed-off-by: J. German Rivera
---
drivers/staging/fsl-mc/bus/mc-bus.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/staging/fsl-m
THE MSI domain associated with a root DPRC object is
obtained form the device tree. Child DPRCs inherit
the parent DPRC MSI domain.
Signed-off-by: J. German Rivera
---
drivers/staging/fsl-mc/bus/dprc-driver.c | 39
1 file changed, 39 insertions(+)
diff --git a/d
Scan the corresponding DPRC container to get total count
of IRQs needed by all its child DPAA2 objects. Then,
preallocate a set of MSI IRQs with the DPRC's ICID
(GIT-ITS device Id) to populate the the DPRC's IRQ pool.
Each child DPAA2 object in the DPRC and the DPRC object itself
will allocate thei
Destroy mc_io in error path in dprc_probe() only if the mc_io was
created in this function. Minor refactoring in error labels.
Signed-off-by: J. German Rivera
---
drivers/staging/fsl-mc/bus/dprc-driver.c | 21 -
1 file changed, 16 insertions(+), 5 deletions(-)
diff --git a/d
The interrupt handler for DPRC IRQs is added. DPRC IRQs are
generated for hot plug events related to DPAA2 objects in a given
DPRC. These events include, creating/destroying DPAA2 objects in
the DPRC, changing the "plugged" state of DPAA2 objects and moving
objects between DPRCs.
Signed-off-by: J.
All the IRQs for DPAA2 objects in the same DPRC must use
the ICID of that DPRC, as their device Id in the GIC-ITS.
Thus, all these IRQs must share the same ITT table in the GIC.
As a result, a pool of IRQs with the same device Id must be
preallocated per DPRC (fsl-mc bus instance). So, the fsl-mc
b
Since an FSL-MC bus is a new bus type that is neither PCI nor
PLATFORM, we need a new domain bus token to disambiguate the
IRQ domain for FSL-MC MSIs.
Signed-off-by: J. German Rivera
---
include/linux/irqdomain.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/irqdomain.h b/inc
The DPRC built-in portal's mc_io is used to send commands to the MC
to program MSIs for MC objects. This is done by the
fsl_mc_msi_write_msg() callback, which is invoked by the generic MSI
layer with interrupts disabled. As a result, the mc_io used in
fsl_mc_msi_write_msg needs to be an atomic mc_i
On Mon, 2015-10-26 at 14:55 +0100, Vitaly Kuznetsov wrote:
> string_get_size() loses precision when there is a remainder for
> blk_size / divisor[units] and size is big enough. E.g
> string_get_size(8192, 4096, STRING_UNITS_10, ...) returns "32.7 MB"
> while it is supposed to return "33.5 MB". For
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Sunday, October 25, 2015 7:13 PM
> To: Pan Lijun-B44306
> Cc: a...@arndb.de; de...@driverdev.osuosl.org; linux-
> ker...@vger.kernel.org; Yoder Stuart-B08248 ;
> katz Itai-RM05202 ; Rivera Jose-B46482
> ; Li
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Monday, October 26, 2015 1:20 AM
> To: Pan Lijun-B44306
> Cc: gre...@linuxfoundation.org; a...@arndb.de; de...@driverdev.osuosl.org;
> linux-kernel@vger.kernel.org; Yoder Stuart-B08248
> ; katz Itai-RM05
On 2015-10-25 05:20, Jonathan Cameron wrote:
> On 19/10/15 08:43, Sanchayan Maity wrote:
>> In case the fsl,adck-max-frequency property is not present in
>> the device tree, a division by zero error results during the
>> probe call on kernel boot (see below). This patch fixes it and
>> also restore
when checking for the value of the shunt resistor.
Signed-off-by: Marc Titinger
---
drivers/hwmon/ina2xx.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/drivers/hwmon/ina2xx.c b/drivers/hwmon/ina2xx.c
index 3edd163..1946433 100644
--- a/drivers/hwmon
Hi Guenter,
as requested, here's the regmap version as a separate patch. I've left out
the idea of separate show functions as it doesn't bring much indeed.
If you're interested in a before/after comparison, here are the plots of
of a usb key (DUT) power-cycle captured using either driver version.
Any sysfs "show" read access from the client app will result in reading
all registers (8 with ina226). Depending on the host this can limit the
best achievable read rate.
This changeset allows for individual register accesses through regmap.
Tested with BeagleBone Black (Baylibre-ACME) and ina226
- pfn = PFN_DOWN(param1 & param2);
- if (!page_is_ram(pfn) || ((param2 & PAGE_MASK) != PAGE_MASK))
+ base_addr = param1 & param2;
+ size = (~param2) + 1;
We expect the user will supply us with param2 in the form 0x[fec8]0
with various numbers of leading 'f' and
> -Original Message-
> From: Andrzej Hajda [mailto:a.ha...@samsung.com]
> Sent: Monday, September 21, 2015 9:34 AM
> To: linux-kernel@vger.kernel.org
> Cc: Andrzej Hajda; Bartlomiej Zolnierkiewicz; Marek Szyprowski; David Airlie;
> Deucher, Alexander; Koenig, Christian; dri-de...@lists.free
This patch moves the blk_integrity_payload definition outside the
CONFIG_BLK_DEV_INTERITY dependency and provides empty function
implementations when the kernel configuration disables integrity
extensions. This simplifies drivers that make use of these to map user
data so they don't need to repeat
On Mon, 2015-10-26 at 16:26 +, Luck, Tony wrote:
> - pfn = PFN_DOWN(param1 & param2);
> - if (!page_is_ram(pfn) || ((param2 & PAGE_MASK) != PAGE_MASK))
> + base_addr = param1 & param2;
> + size = (~param2) + 1;
>
> We expect the user will supply us with param2 in the form
> 0x
On Sat, Oct 24, 2015 at 08:50:54AM +0530, Viresh Kumar wrote:
> On 23-10-15, 15:10, Yunhong Jiang wrote:
> > I got this impression from Frederic's comments on
> > http://marc.info/?l=linux-kernel&m=139048415303210&w=2, "So you simply rely
> > on the next tick to see the new timer. This should wor
Fixed coding style issues
Signed-off-by: Bogicevic Sasa
---
drivers/staging/wlan-ng/hfa384x_usb.c | 189 +-
1 file changed, 95 insertions(+), 94 deletions(-)
diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c
b/drivers/staging/wlan-ng/hfa384x_usb.c
index e109a7f.
Signed-off-by: Sandy Harris
---
drivers/char/random.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/random.c b/drivers/char/random.c
index d0da5d8..90c472b 100644
--- a/drivers/char/random.c
+++ b/drivers/char/random.c
@@ -231,7 +231,7 @@
* not be attributed t
ping?
Is there a plan to fix it? should I send your fix? (kinda plagiarism)
next release? (which would mean the unnecessary warnings will exist in 4.3 :<)
On Tue, Sep 15, 2015 at 6:01 PM, Andy Whitcroft wrote:
> On Tue, Sep 15, 2015 at 05:50:40PM +0300, Tal Shorer wrote:
>
>> > Yes it feels like
Either of pskb_pull() or pskb_trim() may fail under low memory conditions.
If rds_tcp_data_recv() ignores such failures, the application will
receive corrupted data because the skb has not been correctly
carved to the RDS datagram size.
Avoid this by handling pskb_pull/pskb_trim failure in the sa
> + ((param2 & PAGE_MASK) != PAGE_MASK))
>return -EINVAL;
>
> The 3rd condition check makes sure that the param2 mask is the page size or
> less. So, I
> think we are OK on this.
Oops. The original was even on the screen as part of the diff (which I signed
off on just
On Tue, 27 Oct 2015, Javier Martinez Canillas wrote:
> Hello,
>
> On 10/27/2015 12:00 AM, Lee Jones wrote:
> > On Mon, 26 Oct 2015, Wolfram Sang wrote:
> >> On Mon, Oct 26, 2015 at 02:32:36PM +, Lee Jones wrote:
> >>> Regarding your address list -- it's too big. Most of your addressees
> >>>
Hi there,
Sorry for the late reply :-(
2015-10-21 2:48 GMT-06:00 Darren Hart :
> On Tue, Oct 20, 2015 at 12:32:45AM +0100, Ben Hutchings wrote:
>> On Sat, 2015-10-17 at 18:55 -0700, Greg Kroah-Hartman wrote:
>> > 4.2-stable review patch. If anyone has any objections, please let me know.
>> >
>>
On Mon, 2015-10-26 at 16:46 +, Luck, Tony wrote:
> > + ((param2 & PAGE_MASK) != PAGE_MASK))
> >return -EINVAL;
> >
> > The 3rd condition check makes sure that the param2 mask is the page size or
> > less. So,
> > I think we are OK on this.
>
> Oops. The original w
Remove unnecessary headers and variables.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/legacy/gmidi.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/usb/gadget/legacy/gmidi.c
b/drivers/usb/gadget/legacy/gmidi.c
index da19c48..055390b 100644
--- a/drivers/usb/g
This avoids duplication of USB requests for OUT endpoint and
re-enabling endpoints.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/drivers/usb/gadget/function/f_midi.c
index
On 10/26/2015 9:46 AM, Sowmini Varadhan wrote:
Either of pskb_pull() or pskb_trim() may fail under low memory conditions.
If rds_tcp_data_recv() ignores such failures, the application will
receive corrupted data because the skb has not been correctly
carved to the RDS datagram size.
Avoid this
On Fri, Oct 23, 2015 at 06:59:57AM -0700, David Miller wrote:
> From: Michal Hocko
> Date: Fri, 23 Oct 2015 15:19:56 +0200
>
> > On Thu 22-10-15 00:21:33, Johannes Weiner wrote:
> >> Socket memory can be a significant share of overall memory consumed by
> >> common workloads. In order to provide
This patch introduces pre-allocation of IN endpoint USB requests. This
improves on latency (requires no usb request allocation on transmit) and avoid
several potential probles on allocating too many usb requests (which involves
DMA pool allocation problems).
This implementation also handles better
This code is duplicated from f_midi_start_ep(midi, f, midi->out_ep).
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 20
1 file changed, 20 deletions(-)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/drivers/usb/gadget/function/f_midi.c
ind
This patch fixes a memory leak that occurs when an endpoint fails to enqueue
the request. If that happens the complete function will never be called, thus
never freeing the request.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 1 +
1 file changed, 1 insertion(+)
d
Patch 7 has changes on how to transmit IN USB requests. It implements a FIFO
of pre-allocated usb requests and uses then as needed, instead of allocating
then on demand. This is my initial implementation and is open for
suggestions and comments.
Patches 1-6 is pretty much straight forward.
change
This function is shared between gadget functions, so this avoid unnecessary
duplicated code and potentially avoid memory leaks.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 6 --
drivers/usb/gadget/function/f_sourcesink.c | 6 --
drivers/usb/gadget/fu
This makes sure f_midi doesn't try to enqueue data when the IN endpoint is
disabled, ie, USB cable is disconnected.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/f_mi
Hi Keith,
[auto build test ERROR on v4.3-rc7 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Keith-Busch/blk-integrity-empty-imlpementation-when-disabled/20151027-003330
config: i386-randconfig-r0-1025201
Use resource managed function devm_classdev_register to make
error path simpler. Also removed the redundant remove function.
Signed-off-by: Fida Mohammad
---
drivers/leds/leds-hp6xx.c | 15 ++-
1 file changed, 2 insertions(+), 13 deletions(-)
diff --git a/drivers/leds/leds-hp6xx.c b
This patch moves the blk_integrity_payload definition outside the
CONFIG_BLK_DEV_INTERITY dependency and provides empty function
implementations when the kernel configuration disables integrity
extensions. This simplifies drivers that make use of these to map user
data so they don't need to repeat
Hi Franklin,
On Mon, 26 Oct 2015, Franklin S Cooper Jr. wrote:
> On 10/23/2015 02:00 PM, Paul Walmsley wrote:
> > On Thu, 15 Oct 2015, Franklin S Cooper Jr wrote:
> >
> >> ELM address information is provided by device tree. No longer need
> >> to include this information within hwmod.
> >>
> >> S
> -Original Message-
> From: Ray Jui [mailto:r...@broadcom.com]
> Sent: 23 October 2015 21:38
> To: Laurent Pinchart; Rob Herring
> Cc: Pramod Kumar; Pawel Moll; Mark Rutland; Ian Campbell; Kumar Gala; Scott
> Branden; Russell King; Linus Walleij; linux-g...@vger.kernel.org; bcm-kernel-
>
Hi Pramod,
On 10/26/2015 10:08 AM, Pramod Kumar wrote:
-Original Message-
From: Ray Jui [mailto:r...@broadcom.com]
Sent: 23 October 2015 21:38
To: Laurent Pinchart; Rob Herring
Cc: Pramod Kumar; Pawel Moll; Mark Rutland; Ian Campbell; Kumar Gala; Scott
Branden; Russell King; Linus Wal
Em Sun, Oct 25, 2015 at 12:49:27AM +0900, Namhyung Kim escreveu:
> Now usage_with_options() setup a pager before printing message so normal
> printf() or pr_err() will not be shown. The usage_with_options_msg()
> can be used to print some help message before usage strings.
Haven't tested, but int
Hi Jisheng,
On 10/26/2015 4:02 AM, Jisheng Zhang wrote:
Inspired by Russell King's patch[1], I found current iproc also has the
same issue of "reading 32-bits from the command register, modifying the
command register, and then writing it back has the effect of clearing
any status bits that were
On Mon, Oct 26, 2015 at 08:54:52AM +0100, Geert Uytterhoeven wrote:
> Protect the calls to set_fixmap() and clear_fixmap() by #ifdef >
> CONFIG_MMU to fix this.
>
> Fixes: commit ab0615e2d6fb0747 ("arm: use fixmap for text patching when text
> is RO")
> Signed-off-by: Geert Uytterhoeven
Since b
On Fri 23-10-15 17:02:30, Aristeu Rozanski wrote:
> One of the largest chunks of log messages in a OOM is from dump_stack() and in
> some cases it isn't even necessary to figure out what's going on. In
> systems with multiple tenants/containers with limited resources each
> OOMs can be way more fre
On Thu, Oct 22, 2015 at 09:45:10PM +0300, Vladimir Davydov wrote:
> Hi Johannes,
>
> On Thu, Oct 22, 2015 at 12:21:28AM -0400, Johannes Weiner wrote:
> ...
> > Patch #5 adds accounting and tracking of socket memory to the unified
> > hierarchy memory controller, as described above. It uses the exi
Hi Rob,
On Mon, Oct 26, 2015 at 1:45 AM, Rob Herring wrote:
> On Sun, Oct 25, 2015 at 10:25 AM, Geert Uytterhoeven
> wrote:
>> Until commit 0166dc11be911213 ("of: make CONFIG_OF user selectable"),
>> CONFIG_OF=y implied CONFIG_USE_OF=y on ARM, as the former could solely
>> be enabled by being se
Em Sun, Oct 25, 2015 at 03:51:16PM +0100, Jiri Olsa escreveu:
> hi,
> sending another version of stat scripting.
>
> v5 changes:
> - several patches from v4 already taken
> - using u16 for cpu number in cpu_map_event
> - renamed PERF_RECORD_HEADER_ATTR_UPDATE to PERF_RECORD_EVENT_UPDATE
>
Hi Michal,
On Mon, Oct 26, 2015 at 06:20:12PM +0100, Michal Hocko wrote:
> I can see why you want to reduce the amount of information, I guess you
> have tried to reduce the loglevel but this hasn't helped because
> dump_stack uses default log level which is too low to be usable, right?
> Or are th
Em Sun, Oct 25, 2015 at 03:51:19PM +0100, Jiri Olsa escreveu:
> Adding thread_map event to pass/store thread maps
> as data in pipe/perf.data.
>
> Storing thread ID along with the standard comm[16]
> thread name string.
>
> Link: http://lkml.kernel.org/n/tip-2l07qyf3buhnt83q4ezqz...@git.kernel.or
Default the brightness to 2048 and add possibility to override this in
device tree.
Suggested-by: Rob Clark
Signed-off-by: Bjorn Andersson
---
Resend of v2, with updated backlight dt binding location.
Documentation/devicetree/bindings/leds/backlight/pm8941-wled.txt | 2 ++
drivers/video/backl
On Mon, Oct 26, 2015 at 02:42:06PM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
> > PERF_RECORD_AUXTRACE_ERROR = 72,
> > + PERF_RECORD_THREAD_MAP = 73,
> > PERF_RECORD_HEADER_MAX
> > };
> >
> > @@ -356,6 +357,17 @@ struct context_switch_event {
> > u3
On Mon, Oct 26, 2015 at 12:01:11PM -0400, Johannes Weiner wrote:
> I think this makes sense.
>
> The high volume log output is not just annoying, we have also had
> reports from people whose machines locked up as they tried to log
> hundreds of containers through a low-bandwidth serial console.
>
401 - 500 of 839 matches
Mail list logo
