From: Geert Uytterhoeven
The documentation for spi_master.set_cs() says:
assert or deassert chip select, true to assert
i.e. its "enable" parameter uses assertion-level logic.
This does not match the implementation of spi_set_cs(), which calls
spi_master.set_cs() with the wanted logical
This patch
- removes the fields of the platform data which are of no use to the
non-DT platform callers,
- uses a new private structure to handle all the sound card information,
- simplifies the code and make easier a possible multi-DAI links extension.
Signed-off-by: Jean-Francois Moine
---
From: Geert Uytterhoeven
Signed-off-by: Geert Uytterhoeven
---
include/linux/spi/spi.h | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index 21a7251d85ee..5319a8510921 100644
--- a/include/linux/spi/spi.h
+++
Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw()
chain, decode it in zram_bvec_rw() instead. Besides, this is the place
where we distinguish READ (+READ AHEAD) and WRITE bio data directions, so
account zram RW stats here, instead of __zram_make_request(). This also
allows
On Tue, 2014-01-14 at 08:47 +0200, Jack Morgenstein wrote:
> On Tue, 07 Jan 2014 14:01:18 +0100
> Paul Bolle wrote:
>
> > + } else {
> > + /* state == RES_CQ_HW */
> > + if (r->com.state != RES_CQ_ALLOCATED)
>
> if (state != RES_CQ_HW || r->com.state != RES_CQ_ALLOCATED)
>
On (01/14/14 12:02), Jerome Marchand wrote:
> > static int zram_bvec_rw(struct zram *zram, struct bio_vec *bvec, u32 index,
> > - int offset, struct bio *bio, int rw)
> > + int offset, struct bio *bio)
> > {
> > int ret;
> > + int rw = bio_data_dir(bio);
On 13 January 2014 17:23, Nishanth Menon wrote:
> On 01/13/2014 09:03 AM, Taras Kondratiuk wrote:
>> From: Victor Kamensky
>>
>> Assembler functions defined in sleep44xx.S need to byteswap values
>> after read / before write from h/w register if code compiled in big
>> endian mode. Simple change
On (01/14/14 11:38), Jerome Marchand wrote:
> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> > 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> > `show' functions and reduce code duplication.
> >
> > 2) Account and report back to user numbers of failed READ and WRITE
> >
>
> Eh, looks like this path is incomplete too:(
>
> I think we can't set a reference counter for objects which is allocated
> from a SLAB_DESTROY_BY_RCU cache. Look at the following backtrace.
>
> cpu1cpu2
> ct = nf_conntrack_find()
>
From: Srinivas Kandagatla
Some of the SOCs hold the IRB IP in softreset state by default.
For this IP to work driver needs to bring it out of softreset.
This patch adds support to reset the IP via reset framework.
Without this patch the driver can not work with SoCs which holds the IP
in
On Tue, 14 Jan 2014 07:56:32 +
"li.xi...@freescale.com" wrote:
>
> > > Whether the dt is used or not, almost all the simple card information
> > > for the DAI link and sound card are initialized in the simple card driver.
> > >
> > > And for the platform caller, the snd_link and snd_card
On Tue, Jan 14, 2014 at 1:31 PM, Xiong, Jinshan wrote:
>
> On Jan 13, 2014, at 11:56 PM, Dilger, Andreas
> wrote:
>
>>
>>
>> Begin forwarded message:
>>
>>> From: Greg KH
>>> Subject: Re: [PATCH v3 1/2] Staging: lustre: Refactor the function
>>> interval_erase_color() in
On 01/14/2014 01:07 PM, Srivatsa S. Bhat wrote:
> On 01/14/2014 12:30 PM, Srivatsa S. Bhat wrote:
>> On 01/14/2014 11:35 AM, Preeti U Murthy wrote:
>>> On PowerPC, in a particular test scenario, all the cpu idle states were
>>> disabled.
>>> Inspite of this it was observed that the idle state
On 01/13/2014 08:41 PM, Toshi Kani wrote:
> On Tue, 2014-01-14 at 10:11 +0900, Yasuaki Ishimatsu wrote:
> :
I think we need a knob manually enable mem-hotplug when specify memmap. But
it is another story.
Acked-by: KOSAKI Motohiro
>>>
>>> As mentioned, self-NAK. I have
On 01/13/2014 03:03 PM, Vlastimil Babka wrote:
On 01/10/2014 06:48 PM, Motohiro Kosaki wrote:
diff --git a/mm/rmap.c b/mm/rmap.c
index 068522d..b99c742 100644
--- a/mm/rmap.c
+++ b/mm/rmap.c
@@ -1389,9 +1389,19 @@ static int try_to_unmap_cluster(unsigned long
cursor, unsigned int *mapcount,
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> Introduce init_done() helper function which allows us to drop
> `init_done' struct zram member. init_done() uses the fact that
> ->init_done == 1 equals to ->meta != NULL.
>
> Signed-off-by: Sergey Senozhatsky
Acked-by: Jerome Marchand
> ---
On Tue, Jan 14, 2014 at 10:28:23AM +0800, Daniel J Blueman wrote:
> >Peter,
> >
> >I found out that the build failure was caused by the fact that the
> >__native_word() macro (used internally by compiletime_assert_atomic())
> >allows only a size of 4 or 8 for x86-64. The data type that I used is a
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw()
> chain, decode it in zram_bvec_rw() instead. Besides, this is the place
> where we distinguish READ (+READ AHEAD) and WRITE bio data directions, so
> account zram RW stats
On 01/13/2014 07:33 PM, Toshi Kani wrote:
> On Mon, 2014-01-13 at 18:39 -0500, Prarit Bhargava wrote:
>>
>> On 01/13/2014 03:31 PM, KOSAKI Motohiro wrote:
>>> On Sun, Jan 12, 2014 at 6:46 PM, Prarit Bhargava wrote:
On 01/11/2014 11:35 AM, 7egg...@gmx.de wrote:
>
>
>
Following patch ports the cpuidle framework for powernv
platform and also implements a cpuidle back-end powernv
idle driver calling on to power7_nap and snooze idle states.
Moving the idle states over to cpuidle framework can take advantage
of advanced heuristics, tunables and features provided
Following patch ports the cpuidle framework for powernv
platform and also implements a cpuidle back-end powernv
idle driver calling on to power7_nap and snooze idle states.
Signed-off-by: Deepthi Dharwar
---
arch/powerpc/platforms/powernv/setup.c | 13 ++
drivers/cpuidle/Kconfig.powerpc
Hello Jerome,
On (01/14/14 11:38), Jerome Marchand wrote:
> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> > 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> > `show' functions and reduce code duplication.
> >
> > 2) Account and report back to user numbers of failed READ
On Mon, Jan 13, 2014 at 10:24:09PM -0600, Mike Travis wrote:
> Fix some problems found by the kbuild test robot.
>
> Signed-off-by: Mike Travis
> Reviewed-by: Hedi Berriche
In general it is best to actually mention the issues the patch cures,
otherwise review is impossible, /me stares hard at
From: Stephen Gallimore
This patch adds a reset controller platform driver for the STiH415
SoC. This initial version provides a compatible driver for the
"st,stih415-powerdown" device, which registers a system configuration
register based reset controller that controls the powerdown state of
From: Stephen Gallimore
This patch adds a reset controller platform driver for the STiH416
SoC. This initial version provides a compatible driver for the
"st,stih416-powerdown" device, which registers a system configuration
register based reset controller that controls the powerdown state of
This patch adds softreset controller for STiH416 SOC, soft reset
controller is based on system configuration registers which are mapped
via regmap. This reset controller does not have any feedback or
acknowledgement. With this patch a new device "st,stih416-softreset" is
registered with system
This patch adds softreset controller for STiH415 SOC, soft reset
controller is based on system configuration registers which are mapped
via regmap. This reset controller does not have any feedback or
acknowledgement. With this patch a new device "st,stih415-softreset" is
registered with system
Hi All,
This patch series adds reset controller support for STi SOC series STiH415 and
STiH416. It adds support for both regular reset and soft reset controllers.
On STi series SOCs reset lines are wired up to system configuration registers.
Patch 01: Adds reset controller based on system
From: Stephen Gallimore
This patch adds a reset controller implementation for STMicroelectronics
STi family SoCs; it allows a group of related reset like controls found
in multiple system configuration registers to be represented by a single
controller device. System configuration registers are
On 01/13/2014 09:43 PM, Yasuaki Ishimatsu wrote:
> (2014/01/14 10:41), Toshi Kani wrote:
>> On Tue, 2014-01-14 at 10:11 +0900, Yasuaki Ishimatsu wrote:
>> :
> I think we need a knob manually enable mem-hotplug when specify memmap.
> But
> it is another story.
>
> Acked-by:
From: Stephen Gallimore
This patch selects reset controller support for ARCH_STI and
selects the reset controllers for STiH415 and STiH416 SoCs.
Signed-off-by: Stephen Gallimore
Signed-off-by: Srinivas Kandagatla
---
arch/arm/mach-sti/Kconfig |3 +++
1 files changed, 3 insertions(+), 0
On Mon, Jan 13, 2014 at 11:55:17PM -0500, Vince Weaver wrote:
> On Fri, 10 Jan 2014, Peter Zijlstra wrote:
>
> > On Thu, Jan 09, 2014 at 11:08:47PM -0500, Vince Weaver wrote:
> > > On Thu, 9 Jan 2014, Will Deacon wrote:
> > >
> > > > I'd rather see it in the generic code if at all possible.
On 1/14/2014 10:53 AM, Nicholas A. Bellinger wrote:
On Tue, 2014-01-14 at 09:44 +0200, Sagi Grimberg wrote:
On 1/10/2014 8:53 AM, Nicholas A. Bellinger wrote:
On Thu, 2014-01-09 at 12:43 +0200, Sagi Grimberg wrote:
On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger
This patch replaces the cpuidle driver and devices initialisation
calls with a single generic cpuidle_register() call
and also includes minor refactoring of the code around it.
Remove the cpu online check in snooze loop, as this code can
only locally run on a cpu only if it is online. Therefore,
Move the file from arch specific pseries/processor_idle.c
to drivers/cpuidle/cpuidle-pseries.c
Make the relevant Makefile and Kconfig changes.
Also, introduce Kconfig.powerpc in drivers/cpuidle
for all powerpc cpuidle drivers.
Signed-off-by: Deepthi Dharwar
---
Currently cpuidle-pseries backend driver cannot be
built as a module due to dependencies wrt cpuidle framework.
This patch removes all the module related code in the driver.
Signed-off-by: Deepthi Dharwar
---
drivers/cpuidle/cpuidle-pseries.c | 15 +--
1 file changed, 1
smt-snooze-delay was designed to disable NAP state or delay the entry
to the NAP state prior to adoption of cpuidle framework. This
is per-cpu variable. With the coming of CPUIDLE framework,
states can be disabled on per-cpu basis using the cpuidle/enable
sysfs entry.
Also, with the coming of
This patch removes the usage of MAX_IDLE_STATE macro
and dead code around it. The number of states
are determined at run time based on the cpuidle
state table selected on a given platform
Signed-off-by: Deepthi Dharwar
---
drivers/cpuidle/cpuidle-pseries.c | 28 ++--
1
The following patch series includes a bunch of clean-ups for the
pseries cpuidle backend driver. This includes,
moving the driver from arch/powerpc/platforms/pseries to
driver/cpuidle, refactoring of the code, making it a non-module,
removing smt-snooze-delay update and dead code around it.
After
From: Preeti U Murthy
Commit fbd7740fdfdf9475f(powerpc: Simplify pSeries idle loop) switched pseries
cpu idle handling from complete idle loops to ppc_md.powersave functions.
Earlier to this switch, ppc64_runlatch_off() had to be called in each of the
idle routines. But after the switch, this
On Sun, Jan 12, 2014 at 12:21:14PM -0800, Eric Dumazet wrote:
> On Sun, 2014-01-12 at 21:50 +0400, Andrey Vagin wrote:
> > Lets look at destroy_conntrack:
> >
> > hlist_nulls_del_rcu(>tuplehash[IP_CT_DIR_ORIGINAL].hnnode);
> > ...
> > nf_conntrack_free(ct)
> >
This patch adds support for SMBus-only adapters (e.g. i2c-piix4).
The driver has implementet only support for I2C adapter
which implements the I2C_FUNC_SMBUS_I2C_BLOCK functionality before.
With this patch it is possible to load and use the RTC driver with
I2C and SMBUS adapters like the
On 14/01/14 02:11, Boris Ostrovsky wrote:
> On 01/13/2014 06:07 PM, Olaf Hering wrote:
>> On Mon, Jan 13, Boris Ostrovsky wrote:
>>
>>> On 01/13/2014 04:30 AM, Olaf Hering wrote:
> Similarly, if xenbug_gather("discard-secure") fails, I think the
> code will
> assume that secure discard
On Tue, 2014-01-14 at 10:30 +, Linus Walleij wrote:
> Please consult your fellow upstream developers on how to get
> the mail out of the ARM offices in a form that I can apply...
They were exactly in the same position :-)
Fortunately we've got a Christmas gift of a normal SMTP server, so
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> `show' functions and reduce code duplication.
>
> 2) Account and report back to user numbers of failed READ and WRITE
> operations.
>
> 3) Remove `good' and `bad' compressed
Hello Yann,
On Tue, Jan 14, 2014 at 10:57:33AM +0100, Yann Droneaud wrote:
> Le mardi 14 janvier 2014 à 09:19 +0100, Uwe Kleine-König a écrit :
> > On Tue, Jan 14, 2014 at 08:18:29AM +0100, Yann Droneaud wrote:
> > > Since commit 01dcc60a7cb8, platform_device_register_full() is
> > > available to
On Mon, Jan 13, 2014 at 01:25:17PM +0100, Jan Kara wrote:
> On Wed 08-01-14 23:10:15, Miklos Szeredi wrote:
> > From: Miklos Szeredi
> >
> > Implement RENAME_EXCHANGE flag in renameat2 syscall.
> Yes, this is much better than last time. Thanks for the work. You can add
> Reviewed-by: Jan Kara
On Mon, Jan 13, 2014 at 08:52:27AM +0100, Jan Kara wrote:
> On Wed 08-01-14 23:10:11, Miklos Szeredi wrote:
> > + if (max_links && new_dir != old_dir) {
> > error = -EMLINK;
> > - if (max_links && !target && new_dir != old_dir &&
> > - new_dir->i_nlink >=
On Wed, Jan 8, 2014 at 4:57 PM, Pawel Moll wrote:
> On Mon, 2013-12-23 at 17:26 +, Linus Walleij wrote:
>> Good point. But what about also adding device tree support for
>> naming the chips while you're at it?
>>
>> I imagine a generic gpiochip property in
>>
On Mon, Jan 13, 2014 at 10:07:12PM +0100, Rafael J. Wysocki wrote:
> > Currently, the CFS scheduler has no knowledge about frequency scaling.
> > Frequency scaling governors generally try to match the frequency to
> > the load, which means that the idle time has no absolute meaning. The
> >
On Wed, Jan 8, 2014 at 11:18 AM, boris brezillon
wrote:
> Anyway, do you want me to rework the gpio hog as described below ?
If you feel you have time, drive and a proper usecase for testing it,
sure. I just want it to be driven my someone who *really* needs
that feature.
Yours,
Linus Walleij
On Tue, Jan 7, 2014 at 9:45 PM, Sherman Yin wrote:
> On 14-01-07 09:15 AM, Linus Walleij wrote:
> Is that what you wanted to see in pinctrl-bindings.txt, or is there
> something else you want to see added to that txt file? I didn't want to add
> the description of slew-rate arguments there
This patch adds runtime PM support for the HID over I2C driver. When the
i2c-hid device is first opened we power it on and on the last close we
power it off.
The implementation is not the most power efficient because it needs some
interaction from the userspace (e.g close the device node whenever
Hi Dave/Peppe,
Do you have any plans to take this series?
Peppe already Acked these series.
Please let me know if you want me to rebase these patches to a
particular branch.
Thanks,
srini
On 18/11/13 11:30, srinivas.kandaga...@st.com wrote:
> From: Srinivas Kandagatla
>
> Hi Peppe,
>
>
On Tue, Jan 14, 2014 at 02:58:14AM +0200, Marian Marinov wrote:
> On 01/13/2014 07:12 PM, Peter Zijlstra wrote:
> >On Mon, Jan 13, 2014 at 06:23:50PM +0200, Marian Marinov wrote:
> >>Hello Peter,
> >>
> >>I need help with the scheduler.
> >>
> >>I'm currently trying to patch the /proc/loadavg to
This scancode is used in new 2013 models like Satellite P75-A7200.
Signed-off-by: Unai Uribarri
---
drivers/platform/x86/toshiba_acpi.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/toshiba_acpi.c
b/drivers/platform/x86/toshiba_acpi.c
index 7fce391..5d23ca2 100644
On Jan 13, 2014, Sergei Shtylyov wrote:
> Hello.
>> Commit 14bd8c08, that replaced Loongson2-specific ifdefs with cpu tests,
>> inverted the CPU test in local_r4k_flush_icache_range. Loongson2 won't
>> boot up using the generic icache flush code. Presumably other CPUs
>> might face other
On Mon, Jan 13, 2014 at 11:03 PM, Tetsuo Handa
wrote:
> Miklos Szeredi wrote:
>> Cross rename (A, B) is equivalent to plain rename(A, B) + plain rename
>> (B, A) done as a single atomic operation. If security module allows
>> both then cross rename is allowed. If at least one is denied then the
Hi Uwe,
Le mardi 14 janvier 2014 à 09:19 +0100, Uwe Kleine-König a écrit :
> On Tue, Jan 14, 2014 at 08:18:29AM +0100, Yann Droneaud wrote:
> > Since commit 01dcc60a7cb8, platform_device_register_full() is
> > available to allocate and register a platform device.
> >
> > If a dma_mask is
Hi Mark,
I have sent another patch, if that patch is ok, please ignore this patch
series.
The new patch :" ASoC: add snd_soc_of_parse_audio_simple_widgets for
DeviceTree"
Thanks,
--
Best Regards,
Xiubo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
This patch adds snd_soc_of_parse_audio_simple_widgets() and supports
below style of widgets name on DT.
"wname-prefix[ individual name]"
"wname-prefix" includes: "Mic", "Line", "Hp", "Spk"...
For instance:
simple-audio-widgets =
"Mic Jack", "Line In Jack",
On Tue, Jan 14, 2014 at 04:45:24PM +0800, Jason Wang wrote:
> On 01/14/2014 04:25 PM, Michael S. Tsirkin wrote:
> > On Tue, Jan 14, 2014 at 02:53:07PM +0800, Jason Wang wrote:
> >> We used to limit the number of packets queued through tx_queue_length. This
> >> has several issues:
> >>
> >> -
On (01/14/14 12:37), Sergey Senozhatsky wrote:
> This patchset includes code clean up and zram stats rework.
>
forgot to mention. this patchset based on top of Minchan's
patchset.
-ss
> Sergey Senozhatsky (3):
> zram: drop `init_done' struct zram member
> zram: do not pass rw
From: walt
> On 01/09/2014 03:50 PM, Sarah Sharp wrote:
>
> >>> On Tue, Jan 07, 2014 at 03:57:00PM -0800, walt wrote:
> >>
> >> I've wondered if my xhci problems might be caused by hardware quirks, and
> >> wondering why I seem to be the only one who has this problem.
> >>
> >> Maybe I could
On 01/14/14 at 04:41pm, Dave Young wrote:
> On 01/14/14 at 09:26am, Wim Van Sebroeck wrote:
> > Hi Dave,
> >
> > > In kdump kernel watchdog could interrupt vmcore capturing because we
> > > have no way to disable/stop it while crashing happens.
> > >
> > > Add a module parameter
Am Mon, 13 Jan 2014 16:36:20 -0800
schrieb Andrew Morton :
> Patch is big. I'll toss this in for some testing but it does look too
> large and late for 3.14. How will this affect your s390 development?
It is needed for s390 bootmem -> memblock transition. The s390 dump
mechanisms cannot be
Introduce init_done() helper function which allows us to drop
`init_done' struct zram member. init_done() uses the fact that
->init_done == 1 equals to ->meta != NULL.
Signed-off-by: Sergey Senozhatsky
---
drivers/block/zram/zram_drv.c | 21 +++--
drivers/block/zram/zram_drv.h |
Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw()
chain, decode it in zram_bvec_rw() instead. Besides, this is the place
where we distinguish READ (+READ AHEAD) and WRITE bio data directions, so
account zram RW stats here, instead of __zram_make_request(). This also
allows
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of failed READ and WRITE
operations.
3) Remove `good' and `bad' compressed sub-requests stats. RW request may
cause a number of RW
This patchset includes code clean up and zram stats rework.
Sergey Senozhatsky (3):
zram: drop `init_done' struct zram member
zram: do not pass rw argument to __zram_make_request()
zram: rework reported to end-user zram statistics
drivers/block/zram/zram_drv.c | 213
On Tue, Jan 7, 2014 at 9:40 AM, Laxman Dewangan wrote:
> From: Mallikarjun Kasoju
>
> If pins are used for function output like pwm, clk32k,
> power good etc then set it as output mode default.
>
> Signed-off-by: Mallikarjun Kasoju
> Signed-off-by: Laxman Dewangan
Patch applied with Lee's
On 01/13/2014 12:19 PM, Minchan Kim wrote:
> read/write lock's performance is really bad compared to
> mutex_lock in write most workload.(AFAIR, recenlty there
> were some effort to enhance it but not sure it got merged).
>
> Anyway, we don't need such big granuarity read-write lock
> any more so
Hi Rongrong,
> I noticed that Stephen submitted a patch for pinctrl:
> http://www.gossamer-threads.com/lists/linux/kernel/1500890?do=post_view_threaded
>
> In this patch, Stephen said, "When an SoC muxes pins in a group, it's
> quite possible for the group to contain e.g. 6 pins, but only 4 of
>
Hello,
On 2014-01-13 14:53, Thierry Reding wrote:
Provide an implementation for dma_{alloc,free}_writecombine() when the
architecture supports DMA attributes.
Signed-off-by: Thierry Reding
---
arch/arm/include/asm/dma-mapping.h | 16
include/linux/dma-mapping.h| 16
On 10 January 2014 17:30, Roy Franz wrote:
> This patch adds EFI stub support for the ARM Linux kernel. The EFI stub
> operates similarly to the x86 stub: it is a shim between the EFI firmware
> and the normal zImage entry point, and sets up the environment that the
> zImage is expecting. This
On Mon, Jan 13, 2014 at 03:16:42PM -0500, Alan Stern wrote:
> On Wed, 8 Jan 2014, Daniel Vetter wrote:
>
> > On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
> > > On Wed, 8 Jan 2014, Daniel Vetter wrote:
> > >
> > > > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
> > >
Thanks Bjorn,
I have prepared second version, but never send it out :-).
One thing suggested by Mark was missed in this version.
On Mon, 2014-01-13 at 16:30 -0800, Bjorn Andersson wrote:
> From: "Ivan T. Ivanov"
>
> The Qualcomm Universal Peripherial (QUP) wraps I2C mini-core and
> provide
On Tue, Jan 14, 2014 at 09:50:40AM +0100, Alexander Gordeev wrote:
> What if we try to address both goals by making pci_enable_msi() a helper over
> pci_enable_msi_range(pdev, 1, 1)?
Or pci_enable_msi_single() to help reading and avoid drivers conversion mess.
--
Regards,
Alexander Gordeev
On Tue, 2014-01-14 at 09:44 +0200, Sagi Grimberg wrote:
> On 1/10/2014 8:53 AM, Nicholas A. Bellinger wrote:
> > On Thu, 2014-01-09 at 12:43 +0200, Sagi Grimberg wrote:
> >> On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
> >>> From: Nicholas Bellinger
> >>>
> >>> This patch adds support for
On Mon, Jan 13, 2014 at 12:12:20PM -0700, Bjorn Helgaas wrote:
> > - nvec = rc;
> > - rc = pci_enable_msi_block(pdev, nvec);
> > - if (rc)
> > + if (pci_enable_msi_range(pdev, nvec, nvec) < 0)
> > goto intx;
> >
> > return nvec;
> >
> > single_msi:
> > - rc =
An ACPI enumerated device may have its compatible id strings.
To support the compatible ACPI ids (acpi_device->pnp.ids),
we introduced acpi_driver_match_device() to match
the driver->acpi_match_table and acpi_device->pnp.ids.
For those drivers, MODULE_DEVICE_TABLE(acpi, xxx) is used to
exports
ACPI enumerated devices has ACPI style _HID and _CID strings,
all of these strings can be used for both driver loading and matching.
Currently, in Platform, I2C and SPI bus, the ACPI style driver matching
is supported by invoking acpi_driver_match_device() in bus .match() callback.
But, the
Currently, create_modalias() handles the output truncated case in
an improper way (return -EINVAL).
Plus, acpi_device_uevent() and acpi_device_modalias_show() do
improper check for the create_modalias() return value as well.
This patch fixes create_modalias() to
return -EINVAL if there is an
Fix a problem that, the platform bus supports the OF style modalias
in .uevent() call, but not in its device 'modalias' sysfs attribute.
cc: devicet...@vger.kernel.org
Signed-off-by: Zhang Rui
---
drivers/base/platform.c |4
drivers/of/device.c |3 +++
Hi, all,
This patch set fixes a couple of module autoloading problem.
Patch 1/4 fixes a bug in ACPI device 'modalias' and 'uevent' attributes,
although the bug can rarely be reproduced (only if there is an
output error of snprintf, or the ids are longer than 1024 bytes)
Patch
On 01/14/2014 04:25 PM, Michael S. Tsirkin wrote:
> On Tue, Jan 14, 2014 at 02:53:07PM +0800, Jason Wang wrote:
>> We used to limit the number of packets queued through tx_queue_length. This
>> has several issues:
>>
>> - tx_queue_length is the control of qdisc queue length, simply reusing it
>>
On 01/14/14 at 09:26am, Wim Van Sebroeck wrote:
> Hi Dave,
>
> > In kdump kernel watchdog could interrupt vmcore capturing because we
> > have no way to disable/stop it while crashing happens.
> >
> > Add a module parameter stop_before_register so watchdog can be stopped
> > before register in
On 01/06/2014 11:56 PM, Stephen Boyd wrote:
Set the CLOCK_EVT_FEAT_DYNIRQ flag on the memory mapped
clockevent so that we save power by waking up the CPU with the
next event when this timer is used in broadcast mode.
Signed-off-by: Stephen Boyd
---
drivers/clocksource/arm_arch_timer.c | 1 +
op 13-01-14 19:50, Colin Cross schreef:
> On Mon, Jan 13, 2014 at 4:31 AM, Maarten Lankhorst
> wrote:
>> The kernel fence implementation doesn't use event queues, but needs
>> to perform the same wake up. The symbol is not exported, since the
>> fence implementation is not built as a module.
>>
Hi Christophe,
> Convert mpc8xxx_wdt.c to the new watchdog API.
>
> Signed-off-by: Christophe Leroy
This patch has been added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
> -Original Message-
> From: Stephen Rothwell [mailto:s...@canb.auug.org.au]
> Sent: Tuesday, January 14, 2014 06:51
> To: Andrew Morton; Greg KH; Arnd Bergmann
> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Ian Munsie;
> Winkler, Tomas
> Subject: linux-next: manual
Hi Srivatsa,
On 01/14/2014 12:30 PM, Srivatsa S. Bhat wrote:
> On 01/14/2014 11:35 AM, Preeti U Murthy wrote:
>> On PowerPC, in a particular test scenario, all the cpu idle states were
>> disabled.
>> Inspite of this it was observed that the idle state count of the shallowest
>> idle state,
Hi Dave,
> In kdump kernel watchdog could interrupt vmcore capturing because we
> have no way to disable/stop it while crashing happens.
>
> Add a module parameter stop_before_register so watchdog can be stopped
> before register in driver loading path. Thus we can try to load the
> watchdog
On Tue, Jan 14, 2014 at 02:53:07PM +0800, Jason Wang wrote:
> We used to limit the number of packets queued through tx_queue_length. This
> has several issues:
>
> - tx_queue_length is the control of qdisc queue length, simply reusing it
> to control the packets queued by device may cause
On 01/13/2014 08:44 PM, Casey Schaufler wrote:
On 1/13/2014 12:01 AM, Jan Kaluza wrote:
Hi,
this patchset against net-next (applies also to linux-next) adds 3 new types
of "Socket"-level control message (SCM_AUDIT, SCM_PROCINFO and SCM_CGROUP).
How about the group list, while you're at it?
On Tue, 2014-01-14 at 09:01 +0100, Mike Galbraith wrote:
> On Tue, 2014-01-14 at 02:31 -0500, Len Brown wrote:
> > > This is a false alarm.
> >
> > Thanks for the follow-up, Mel.
> >
> > Agreed, it makes no sense for ebizzy measure 'throughput', when a
> > library debug bottleneck
> > prevents
In kdump kernel watchdog could interrupt vmcore capturing because we
have no way to disable/stop it while crashing happens.
Add a module parameter stop_before_register so watchdog can be stopped
before register in driver loading path. Thus we can try to load the
watchdog driver as early as
On Tue, Jan 14, 2014 at 03:47:36PM +0800, rogera...@realtek.com wrote:
> +static int ms_pull_ctl_disable(struct rtsx_ucr *ucr)
> +{
> + rtsx_usb_init_cmd(ucr);
> +
> + if (CHECK_PKG(ucr, LQFP48)) {
> + rtsx_usb_add_cmd(ucr, WRITE_REG_CMD,
> +
Hello Yann,
On Tue, Jan 14, 2014 at 08:18:29AM +0100, Yann Droneaud wrote:
> Since commit 01dcc60a7cb8, platform_device_register_full() is
> available to allocate and register a platform device.
>
> If a dma_mask is provided as part of platform_device_info,
> platform_device_register_full()
2014/1/6 Barry Song <21cn...@gmail.com>:
> From: Barry Song
>
> sirfprima2 and sirfatlas6 are two different SoCs in CSR SiRF series. for
> prima2 and atlas6, there are many shared clocks but there are still
> some different register layout and hardware clocks, then result in
> different clock
801 - 900 of 1818 matches
Mail list logo
