This driver registers a restart handler to set a GPIO line high/low
to reset a board based on devicetree bindings.
Signed-off-by: David Riley davidri...@chromium.org
---
.../devicetree/bindings/gpio/gpio-restart.txt | 54
drivers/power/reset/Kconfig| 8 ++
This driver builds upon Guenter Roeck's kernel restart handler patchset
to add a driver which registers a GPIO-based restart handler which restarts
the system by toggling a GPIO.
Changes are based off 3.17-rc2 with the following patches from v7 of
Guenter's patchset:
On 27 August 2014 23:08, Andrew Bresticker abres...@chromium.org wrote:
On Mon, Aug 25, 2014 at 12:01 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
I'm not even sure if it's appropriate for the low-level mailbox driver to
know about the semantics of the message, rather than simply sending
On Wed, Aug 27, 2014 at 03:00:29PM +0200, Ricardo Ribalda Delgado wrote:
Defining the vendor and the product id should be enough to discriminate
the device.
The reason for this patch is that there is a missmatch betweed the
modalias showed by sysfs and the modalias generated by file2alias.
Hi,
On Fri, Aug 22, 2014 at 06:59:05PM +0200, Bartlomiej Zolnierkiewicz wrote:
drivers/usb/phy/phy-samsung-usb[2,3] drivers got replaced by
drivers/phy/phy-samsung-usb[2,3] ones and the old common Samsung
USB PHY code is no longer used.
Signed-off-by: Bartlomiej Zolnierkiewicz
On 08/27/14 12:19, Ian Abbott wrote:
Currently, to select the comedi_bond driver, the kcomedilib support
has to be selected first. It seems more natural to allow the
comedi_bond driver to be selected on its own and to automatically
select the kcomedilib module as a result of that. Change the
On Wed, Aug 27, 2014 at 03:03:45PM +0200, Michal Sojka wrote:
With this patch, USB activity can be signaled by blinking a LED. There
are two triggers, one for activity on USB host and one for USB gadget.
Both trigger should work with all host/device controllers. Tested only
with musb.
Hi,
On Wed, Aug 27, 2014 at 11:42:25PM +0530, Vivek Gautam wrote:
On Wed, Aug 27, 2014 at 1:22 PM, Bartlomiej Zolnierkiewicz
b.zolnier...@samsung.com wrote:
dwc3 driver is using the new Exynos5 SoC series USB DRD PHY driver
(PHY_EXYNOS5_USBDRD which selects GENERIC_PHY) as can be seen by
On Wed, Aug 27, 2014 at 12:27:51PM -0700, Greg Kroah-Hartman wrote:
On Wed, Aug 27, 2014 at 03:03:45PM +0200, Michal Sojka wrote:
With this patch, USB activity can be signaled by blinking a LED. There
are two triggers, one for activity on USB host and one for USB gadget.
Both trigger
On 08/27/2014 11:30 AM, Andrew Bresticker wrote:
On Mon, Aug 25, 2014 at 8:17 AM, Jonas Gorski j...@openwrt.org wrote:
On Sat, Aug 23, 2014 at 9:50 PM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
On Sat, Aug 23, 2014 at 8:31 AM, Olof Johansson o...@lixom.net wrote:
On Wed, Aug 27, 2014 at 2:13 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
+ Daniel (cpuidle maintainer)
[...]
+static int omap_enter_idle_smp(struct cpuidle_device *dev,
+struct cpuidle_driver *drv,
+int index)
+{
+ struct
On 08/27/14 11:12, José Manuel Alarcón Roldán wrote:
The example code provided with the i2c device interface documentation
won't compile since it uses the reserved word register to name a
variable.
The compiler fails with this error message:
error: expected identifier or '(' before '='
On 08/27/2014 09:18 PM, Stephen Hemminger wrote:
Something in man page format similar to FreeBSD man page:
http://www.freebsd.org/cgi/man.cgi?bpf(4)
would be more readable and reviewable.
I think at some point, we could perhaps do a section 7 page
with a general overview of the engine and
On Wed, Aug 27, 2014 at 12:18 PM, Stephen Hemminger
step...@networkplumber.org wrote:
Something in man page format similar to FreeBSD man page:
http://www.freebsd.org/cgi/man.cgi?bpf(4)
would be more readable and reviewable.
Ok. will chop it into smallest diff possible and will add a doc
for
Currently, to select the comedi_bond driver, the kcomedilib support
has to be selected first. It seems more natural to allow the
comedi_bond driver to be selected on its own and to automatically
select the kcomedilib module as a result of that. Change the
dependency/select relationship between
Hello Greg
On Wed, Aug 27, 2014 at 9:25 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Wed, Aug 27, 2014 at 03:00:29PM +0200, Ricardo Ribalda Delgado wrote:
Defining the vendor and the product id should be enough to discriminate
the device.
The reason for this patch is that
Building with the attached random configuration file,
warning: (SND_SOC_FSL_ASOC_CARD) selects SND_SOC_WM8962 which has
unmet direct dependencies (SOUND !M68K !UML SND SND_SOC
I2C INPUT)
ERROR: input_event [sound/soc/codecs/snd-soc-wm8962.ko] undefined!
ERROR: input_register_device
* Nishanth Menon n...@ti.com [140827 12:05]:
On 08/27/2014 01:58 PM, Kevin Hilman wrote:
Nishanth Menon n...@ti.com writes:
From: Rajendra Nayak rna...@ti.com
On OMAP5 / DRA7, prevent a CPU powerdomain OFF and resulting MPU OSWR
and instead attempt a CPU RET and side effect, MPU RET
On Wednesday 27 August 2014 03:35 PM, Nishanth Menon wrote:
On Wed, Aug 27, 2014 at 2:13 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
+ Daniel (cpuidle maintainer)
[...]
+static int omap_enter_idle_smp(struct cpuidle_device *dev,
+struct cpuidle_driver
On Wednesday 27 August 2014 03:41 PM, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [140827 12:05]:
On 08/27/2014 01:58 PM, Kevin Hilman wrote:
Nishanth Menon n...@ti.com writes:
From: Rajendra Nayak rna...@ti.com
On OMAP5 / DRA7, prevent a CPU powerdomain OFF and resulting MPU OSWR
On Wed, Aug 27, 2014 at 09:21:02PM +0200, Tomasz Figa wrote:
On 27.08.2014 21:15, Mark Brown wrote:
This is in the scenario where the previously running Linux changed the
mode to something other than normal and where the freshly booted Linux
can't figure out how to do that when it needs
2014-08-27 22:35 GMT+03:00 Randy Dunlap rdun...@infradead.org:
On 08/27/14 11:12, José Manuel Alarcón Roldán wrote:
The example code provided with the i2c device interface documentation
won't compile since it uses the reserved word register to name a
variable.
The compiler fails with this
On 08/27/2014 02:43 PM, Santosh Shilimkar wrote:
On Wednesday 27 August 2014 03:41 PM, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [140827 12:05]:
On 08/27/2014 01:58 PM, Kevin Hilman wrote:
Nishanth Menon n...@ti.com writes:
From: Rajendra Nayak rna...@ti.com
On OMAP5 / DRA7,
From: Tim Gardner tim.gard...@canonical.com
The gcc version 4.9.1 compiler complains Even though it isn't possible for
these variables to not get initialized before they are used.
fs/namespace.c: In function ‘SyS_mount’:
fs/namespace.c:2720:8: warning: ‘kernel_dev’ may be used uninitialized in
The example code provided with the i2c device interface documentation
won't compile since it uses the reserved word register to name a
variable.
The compiler fails with this error message:
error: expected identifier or '(' before '=' token
__u8 register = 0x20; /* Device register to access
On 08/21/2014 08:44 PM, Tony Lindgren wrote:
Also, with DMA enabled, looks like omap deeper idle states are
blocked as the DMA stays reserved. After I commented out the
DMA info for my console UART, PM started working.
Hmm. This would explain something. This would mean that I should cancel
On Wed, Aug 27, 2014 at 10:54:21PM +0300, José Manuel Alarcón Roldán wrote:
The example code provided with the i2c device interface documentation
won't compile since it uses the reserved word register to name a
variable.
The compiler fails with this error message:
error: expected
2014-08-27 22:54 GMT+03:00 José Manuel Alarcón Roldán
jose.alarcon.rol...@gmail.com:
The example code provided with the i2c device interface documentation
won't compile since it uses the reserved word register to name a
variable.
The compiler fails with this error message:
error: expected
On 27.08.2014 21:44, Mark Brown wrote:
On Wed, Aug 27, 2014 at 09:21:02PM +0200, Tomasz Figa wrote:
On 27.08.2014 21:15, Mark Brown wrote:
This is in the scenario where the previously running Linux changed the
mode to something other than normal and where the freshly booted Linux
can't
Heiko,
On Wed, Aug 27, 2014 at 12:53 PM, Heiko Stübner he...@sntech.de wrote:
Hi Chris,
Am Dienstag, 26. August 2014, 22:14:04 schrieb Chris Zhong:
The RK808 chip is a power management IC for multimedia and handheld
devices. It contains the following components:
- Regulators
- RTC
-
Dmitry,
On Wed, Aug 27, 2014 at 10:21 AM, Dmitry Torokhov d...@chromium.org wrote:
On Wednesday, August 27, 2014 02:39:36 PM Lee Jones wrote:
On Tue, 26 Aug 2014, Chris Zhong wrote:
+
+static struct of_device_id rk808_of_match[] = {
+ { .compatible = rockchip,rk808 },
+};
On Tue, 26 Aug 2014 23:45:20 -0400 Matthew Wilcox matthew.r.wil...@intel.com
wrote:
One of the primary uses for NV-DIMMs is to expose them as a block device
and use a filesystem to store files on the NV-DIMM. While that works,
it currently wastes memory and CPU time buffering the files in
Am Mittwoch, 27. August 2014, 12:59:35 schrieb Doug Anderson:
Heiko,
On Wed, Aug 27, 2014 at 12:53 PM, Heiko Stübner he...@sntech.de wrote:
Hi Chris,
Am Dienstag, 26. August 2014, 22:14:04 schrieb Chris Zhong:
The RK808 chip is a power management IC for multimedia and handheld
On Wed, Aug 27 2014, Michal Sojka wrote:
All USB peripheral controller drivers called completion routines
directly. This patch moves the completion call from drivers to
usb_gadget_giveback_request(), in order to have a place where common
functionality can be added.
All places in drivers/usb/
Based on original work by pchid...@codeaurora.org.
QoS requests that need to track an IRQ can be set to apply only on the
cpus to which the IRQ's smp_affinity attribute is set to. The PM QoS
framework will automatically track IRQ migration between the cores. The
QoS is updated to be applied only
From: Praveen Chidambaram pchid...@codeaurora.org
QoS request can be better optimized if the request can be set only for
the required cpus and not all cpus. This helps save power on other
cores, while still guaranteeing the quality of service on the desired
cores.
Add a new enumeration to
This patchset helps in listing dtrace style markers(SDT) present in user space
applications through perf.
SDT Notes/markers are placed at important places by the
developers. They have a negligible overhead when not enabled.
We can enable them and probe at these places and find some important
PM QoS and other idle frameworks can do a better job of addressing power
and performance requirements for a cpu, knowing the IRQs that are
affine to that cpu. If a performance request is placed against serving
the IRQ faster and if the IRQ is affine to a set of cpus, then setting
the performance
Changes since v2:
[ http://marc.info/?l=linux-pmm=140794570012619w=2 ]
- Amend commit texts
This patchset enables drivers to set per-cpu PM QoS. PM QoS requests currently
apply to all cpus. However, drivers may be interested in only a few cpu(s) that
need to gaurantee the QoS requirement. The
From: Praveen Chidambaram pchid...@codeaurora.org
QoS add requests uses a handle to the priority list that is used
internally to save the request, but this does not extend well. Also,
dev_pm_qos structure definition seems to use a list object directly.
The 'derivative' relationship seems to be
This patch serves as the initial support to identify and list SDT events in
binaries.
When programs containing SDT markers are compiled, gcc with the help of
assembler
directives identifies them and places them in the section .note.stapsdt. To
find these
markers from the binaries, one needs to
On Wednesday 27 August 2014 07:41:43 Caesar Wang wrote:
+- clock-names : Shall be tsadc_clk for the transfer-clock, and
tsadc_pclk for
+the peripheral clock.
Why not just name them clk and pclk? The tsadc part seems highly
redundant.
Alternatively, how about transfer and peripheral?
On Wed, Aug 27, 2014 at 03:03:44PM +0200, Michal Sojka wrote:
All USB peripheral controller drivers called completion routines
directly. This patch moves the completion call from drivers to
usb_gadget_giveback_request(), in order to have a place where common
functionality can be added.
All
This patch enables perf to look for SDT markers in a single file.
An individual file argument must be given to perf list to find out the SDT
markers
present in that file.
Usage is as below :
# perf list sdt /home/hemant/tmp
/home/hemant/tmp:
%user : foo
%user : bar
On using this command, perf
Adds documentation for perf support to SDT events.
Signed-off-by : Hemant Kumar hem...@linux.vnet.ibm.com
---
tools/perf/Documentation/SDT-support.txt | 48 ++
tools/perf/Documentation/perf-list.txt |4 ++-
2 files changed, 51 insertions(+), 1 deletion(-)
On Wed, Aug 27, 2014 at 09:39:43PM +0200, Ricardo Ribalda Delgado wrote:
Hello Greg
On Wed, Aug 27, 2014 at 9:25 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Wed, Aug 27, 2014 at 03:00:29PM +0200, Ricardo Ribalda Delgado wrote:
Defining the vendor and the product id
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Wednesday 27 August 2014 03:35 PM, Nishanth Menon wrote:
On Wed, Aug 27, 2014 at 2:13 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
+ Daniel (cpuidle maintainer)
[...]
+static int omap_enter_idle_smp(struct cpuidle_device *dev,
+
On Wed, Aug 27, 2014 at 02:57:57PM +0200, Ricardo Ribalda Delgado wrote:
There is a missmatch between the way file2alias generates the modalias
and the way the pci driver generates it.
Some implementations of modprobe will fail to load the driver for a pci
device automatically when the pci
* Sebastian Andrzej Siewior bige...@linutronix.de [140827 12:54]:
On 08/21/2014 08:44 PM, Tony Lindgren wrote:
Also, with DMA enabled, looks like omap deeper idle states are
blocked as the DMA stays reserved. After I commented out the
DMA info for my console UART, PM started working.
Nishanth Menon n...@ti.com writes:
powerdomain configuration in OMAP is done using PWRSTCTRL register for
each power domain. However, PRCM lets us write any value we'd like to
the logic and power domain target states, however the SoC integration
tends to actually function only at a few
On Wed, Aug 27, 2014 at 09:58:55PM +0200, Tomasz Figa wrote:
On 27.08.2014 21:44, Mark Brown wrote:
The point is that if anything was setting the mode to something other
than normal it was almost certainly a previously running copy of Linux
and one would expect that if the mode does need
Dan Aloni d...@kernelim.com writes:
I like your extension to the test program. I have a suggestion for
the integration inside libaio's harness, since the original issue
depended on the size of the ring buffer, let's have max_ios be picked
from {ring-nr + 1, ring-nr - 1, ring-nr}*{1,2,3,4} for
Hi Chris,
Am Dienstag, 26. August 2014, 22:14:04 schrieb Chris Zhong:
The RK808 chip is a power management IC for multimedia and handheld
devices. It contains the following components:
- Regulators
- RTC
- Clkout
The RK808 core driver is registered as a platform driver and provides
On 08/27/14 12:57, José Manuel Alarcón Roldán wrote:
2014-08-27 22:54 GMT+03:00 José Manuel Alarcón Roldán
jose.alarcon.rol...@gmail.com:
The example code provided with the i2c device interface documentation
won't compile since it uses the reserved word register to name a
variable.
The
On Wed, 27 Aug 2014, Rafael J. Wysocki wrote:
The line of reasoning leading to that is as follows.
The way suspend_device_irqs() works and the existing code in
check_wakeup_irqs(), called by syscore_suspend(), imply that:
(1) Interrupt handlers are not invoked for wakeup interrupts
Arnd,
在 2014年08月28日 04:17, Arnd Bergmann 写道:
On Wednesday 27 August 2014 07:41:43 Caesar Wang wrote:
+- clock-names : Shall be tsadc_clk for the transfer-clock, and tsadc_pclk
for
+the peripheral clock.
Why not just name them clk and pclk? The tsadc part seems highly
redundant.
Hi David,
I've been thinking on the minimum first patch set.
Came up with the following two:
1st patch adds 'load 64-bit immediate' instruction which by itself
is harmless and used to load constants only. In the future we may
add pseudo variants of this insn, so user space can request
internal
add BPF_LD_IMM64 instruction to load 64-bit immediate value into a register.
All previous instructions were 8-byte. This is first 16-byte instruction.
Two consecutive 'struct bpf_insn' blocks are interpreted as single instruction:
insn[0].code = BPF_LD | BPF_DW | BPF_IMM
insn[0].dst_reg =
allow user space to generate eBPF programs
uapi/linux/bpf.h: eBPF instruction set definition
linux/filter.h: the rest
This patch only moves macro definitions, but practically it freezes existing
eBPF instruction set, though new instructions can still be added in the future.
These eBPF
On 27.08.2014 22:25, Mark Brown wrote:
On Wed, Aug 27, 2014 at 09:58:55PM +0200, Tomasz Figa wrote:
On 27.08.2014 21:44, Mark Brown wrote:
The point is that if anything was setting the mode to something other
than normal it was almost certainly a previously running copy of Linux
and one
The nocb callbacks generated before the nocb kthreads are spawned are
enqueued in the nocb queue for later processing. Commit fbce7497ee5af (rcu:
Parallelize and economize NOCB kthread wakeups) introduced nocb leader kthreads
which checked the nocb_leader_wake flag to see if there were any such
Oleg, this is unacceptable.
Last week was Kernel Summit and that was right on the heels of a merge window.
We are backlogged like crazy and being rude doesn't help one iota.
On August 27, 2014 11:51:38 AM PDT, Oleg Nesterov o...@redhat.com wrote:
Hello,
Who can review this? And where should I
Gmail. I just had a look at Documentation/email-clients.txt I thought
that selected unformatted text mode would be enough, but obviously it
wasn't. My bad :-(
Will be more careful next time I send a patch. I will use something else.
--
Jose
2014-08-27 23:30 GMT+03:00 Randy Dunlap
On Wed, Aug 27, 2014 at 10:03:10AM +0200, Stefan Bader wrote:
On 26.08.2014 18:01, Konrad Rzeszutek Wilk wrote:
On Fri, Aug 22, 2014 at 11:20:50AM +0200, Stefan Bader wrote:
On 21.08.2014 18:03, Kees Cook wrote:
On Tue, Aug 12, 2014 at 2:07 PM, Konrad Rzeszutek Wilk
konrad.w...@oracle.com
On Wed, Aug 27, 2014 at 01:23:01PM -0700, Greg KH wrote:
On Wed, Aug 27, 2014 at 02:57:57PM +0200, Ricardo Ribalda Delgado wrote:
There is a missmatch between the way file2alias generates the modalias
and the way the pci driver generates it.
Some implementations of modprobe will fail to
On Sun, 24 Aug 2014 23:56:02 +0900 Akinobu Mita akinobu.m...@gmail.com wrote:
Replace memblock_find_in_range() and memblock_reserve() with
memblock_alloc_range() or memblock_alloc_base().
Please spend a little more time preparing the changelogs?
Why are we making this change? Because
On Wed, 27 Aug 2014, Lina Iyer wrote:
PM QoS and other idle frameworks can do a better job of addressing power
and performance requirements for a cpu, knowing the IRQs that are
affine to that cpu. If a performance request is placed against serving
the IRQ faster and if the IRQ is affine to a
No worries,
I have to mark for stable it or Bjorn? It it is me, how :) ?
Regards!
ps: For other people reading this thread, the kmod/modprobe is in
http://anonscm.debian.org/cgit/users/md/kmod.git/tree/libkmod/libkmod-index.c
and handles all the modalias as strings without differing the type.
All USB peripheral controller drivers called completion routines
directly. This patch moves the completion call from drivers to
usb_gadget_giveback_request(), in order to have a place where common
functionality can be added.
All places in drivers/usb/ matching [-.]complete( were replaced with a
In the next commit, we will want the usb-common module to be composed of
two object files. Since Kbuild cannot append another object to an
existing one, we need to rename usb-common.c to something
else (common.c) and create usb-common.o by linking the wanted objects
together. Currently,
With this patch, USB activity can be signaled by blinking a LED. There
are two triggers, one for activity on USB host and one for USB gadget.
Both trigger should work with all host/device controllers. Tested only
with musb.
Signed-off-by: Michal Sojka so...@merica.cz
---
drivers/usb/Kconfig
This adds LED triggers for USB host and device. First patch refactors
UDC drivers as requested by Felipe Balbi, second is a preparation for
the third, which adds the LED triggers.
Changes from v3:
- usb_gadget_giveback_request() moved outside of CONFIG_HAS_DMA
conditioned block.
- Added
On Wed, Aug 27, 2014 at 01:51:05PM -0600, rtg.canoni...@gmail.com wrote:
From: Tim Gardner tim.gard...@canonical.com
The gcc version 4.9.1 compiler complains Even though it isn't possible for
these variables to not get initialized before they are used.
Blanket NAK, at that - any patches
On Wed, Aug 27, 2014 at 12:23:39PM -0700, Greg KH wrote:
On Wed, Aug 27, 2014 at 03:11:10PM +0300, Roger Quadros wrote:
If user specifies that USB autosuspend must be disabled by module
parameter usbcore.autosuspend=-1 then we must prevent
autosuspend of USB hub devices as well.
commit
On Tue, 2014-08-26 at 09:58 -0700, Laura Abbott wrote:
On 8/26/2014 3:05 AM, James Hogan wrote:
On 12 August 2014 00:40, Laura Abbott lau...@codeaurora.org wrote:
For architectures without coherent DMA, memory for DMA may
need to be remapped with coherent attributes. Factor out
the the
On Wed, 27 Aug 2014, Michal Sojka wrote:
+/**
+ * usb_gadget_giveback_request - give the request back to the gadget layer
+ * Context: in_interrupt()
+ *
+ * This is called by device controller drivers in order to return the
+ * completed request back to the gadget layer.
+ */
+void
This is a bug fix for using physical arch timers when
the arch_timer_use_virtual boolean is false. It restores the
arch_counter_get_cntpct() function after removal in
0d651e4e clocksource: arch_timer: use virtual counters
and completes the implementation of memory mapped access for physical
Hello Greg
Not many drivers define the pci interface and there is no other driver
that has the same vendor and product id. Therefore I see no hurt in
adding both patches, one to make the driver broader, and another to
fix pci-sysfs.
Also, the change on pci-sysfs might affect more stuff
On Wed, Aug 27, 2014 at 10:41:42PM +0200, Tomasz Figa wrote:
On 27.08.2014 22:25, Mark Brown wrote:
Well, presumably the bootloader is going to run again even for a warm
reboot?
This is strange, but apparently it's not the case for the hardware which
this patch is supposed to fix or at
On 27.08.2014 22:41, Tomasz Figa wrote:
On 27.08.2014 22:25, Mark Brown wrote:
On Wed, Aug 27, 2014 at 09:58:55PM +0200, Tomasz Figa wrote:
On 27.08.2014 21:44, Mark Brown wrote:
The point is that if anything was setting the mode to something other
than normal it was almost certainly a
From: Yang Wei wei.y...@windriver.com
While loading g_mass_storage module, the following warning
is triggered.
WARNING: at drivers/usb/gadget/composite.c:
usb_composite_setup_continue: Unexpected call
Modules linked in: fat vfat minix nls_cp437 nls_iso8859_1 g_mass_storage
[800179cc]
From: Andi Kleen a...@linux.intel.com
On Broadwell INST_RETIRED.ALL cannot be used with any period
that doesn't have the lowest 6 bits cleared. And the period
should not be smaller than 128.
Add a new callback to enforce this, and set it for Broadwell.
This is erratum BDM57 and BDM11.
v2: Use
From: Andi Kleen a...@linux.intel.com
Add Broadwell support for Broadwell Client to perf.
This is very similar to Haswell. It uses a new cache event table,
because there were various changes there.
The constraint list has one new event that needs to be handled over Haswell.
The PEBS event list
On Mon, Aug 25, 2014 at 10:47:51AM +0200, Geert Uytterhoeven wrote:
Signed-off-by: Geert Uytterhoeven geert+rene...@glider.be
Applied, thanks.
signature.asc
Description: Digital signature
If ffs-test is used with a kernel prior to 3.14, which do not
support the new descriptors format, it will fail when trying to
write the descriptors. Add a function that converts the new
descriptors to the legacy ones and use it to retry writing the
descriptors using the legacy format.
Also add
From: Julia Lawall julia.law...@lip6.fr
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
// smpl
@@
identifier lbl;
identifier rc;
constant c;
@@
- GOTO(lbl,\(rc\|c\));
+ goto lbl;
@@
identifier lbl;
expression rc;
@@
- GOTO(lbl,rc);
+ rc;
+ goto lbl;
//
On Fri, 22 Aug 2014, Benjamin Tissoires wrote:
We can do once the test of the validity of the dj_device, which removes
some duplicated code in various functions.
Queued for 3.18, thanks Benjamin.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe
The structure can be used with user space tools that use the new
functionfs description format, for example as follows:
static const struct {
struct usb_functionfs_descs_head_v2 header;
__le32 fs_count;
__le32 hs_count;
struct {
…
} fs_desc;
Apparently I've slept over 3.17 merge window, so I guess this is
for 3.18. Rebased on top of balbi/usb.git next.
Michal Nazarewicz (4):
usb: gadget: f_fs: add usb_functionfs_descs_head_v2 structure
tools: ffs-test: convert to new descriptor format
tools: ffs-test: add compatibility code
From: Andi Kleen a...@linux.intel.com
71 is a Broadwell, not a Haswell. The model number was added
by mistake earlier.
Remove it for now, until it can be re-added later with
real Broadwell support.
In practice it does not cause a lot of issues because the Broadwell
PMU is very similar to
Since commit [ac8dde11: “Add flags to descriptors block”] functionfs
supports a new, more powerful and extensible, descriptor format.
Since ffs-test is probably the first thing users of the functionfs
interface see when they start writing functionfs user space daemons,
convert it to use the new
Only minor changes to the last version. The Broadwell model number
patch now has a more expansive change log and does not
reorder case statements anymore.
Some minor updates to commit logs.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Wed, Aug 27, 2014 at 10:58:00PM +0200, Michal Sojka wrote:
With this patch, USB activity can be signaled by blinking a LED. There
are two triggers, one for activity on USB host and one for USB gadget.
Both trigger should work with all host/device controllers. Tested only
with musb.
On Wed, Aug 27, 2014 at 03:14:21PM +0200, Geert Uytterhoeven wrote:
This morning I was greeted by some crashes, as your spi/for-next branch
has just pulled in spi/topic/fsl-dspi, which contains regmap/dt-endian, but
not the fixes :-(
Yes, probably.
signature.asc
Description: Digital
On Wed, Aug 27, 2014 at 10:56:57PM +0200, Ricardo Ribalda Delgado wrote:
No worries,
I have to mark for stable it or Bjorn? It it is me, how :) ?
Bjorn can when he applies it, for details on the process, see the kernel
file Documentation/stable_kernel_rules.txt
ps: For other people reading
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
On Wed, Aug 27, 2014 at 09:39:43PM +0200, Ricardo Ribalda Delgado wrote:
return sprintf(buf, pci:v%08Xd%08Xsv%08Xsd%08Xbc%02Xsc%02Xi%02x\n,
That final 'x' does look like a typo, doesn't it? We are otherwise
consistently using upper-case
From: Andi Kleen a...@linux.intel.com
Use the newly added Broadwell cache event list for Haswell too.
All Haswell and Broadwell events and offcore masks used in these lists
are identical.
However Haswell is very different from the Sandy Bridge
list that was used previously. That fixes a wide
From: Andi Kleen a...@linux.intel.com
Add names for each Haswell model as requested by Peter.
v2: Remove Crystall Well name.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
arch/x86/kernel/cpu/perf_event_intel.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Thomas,
The latest btrfs code uses rwsem_is_contended() in the function
caching_thread(). On RT systems, include/linux/rwsem.h is replaced with
include/linux/rwsem_rt.h which does not provide a definition for
rwsem_is_contended(). This commit provides a definition that should
work on RT (where
On Wed, Aug 27, 2014 at 10:57:58PM +0200, Michal Sojka wrote:
All USB peripheral controller drivers called completion routines
directly. This patch moves the completion call from drivers to
usb_gadget_giveback_request(), in order to have a place where common
functionality can be added.
All
501 - 600 of 1630 matches
Mail list logo
