On Fri, Dec 19, 2014 at 11:15:33PM -0800, Jeremiah Mahler wrote:
> Dudley,
>
> On Thu, Dec 18, 2014 at 06:00:44PM +0800, Dudley Du wrote:
> > V16 patches have below updates, details of other updates see history list:
> [...]
>
> This version has problems. I am getting an oops (below) and then th
On Sat, Dec 20, 2014 at 03:16:18AM +0100, Samuel Thibault wrote:
> Dmitry Torokhov, le Fri 19 Dec 2014 15:07:21 -0800, a écrit :
> > On Sat, Dec 20, 2014 at 12:02:53AM +0100, Pavel Machek wrote:
> > > On Fri 2014-12-19 23:59:33, Samuel Thibault wrote:
> > > > Andrew Morton, le Fri 19 Dec 2014 14:46
core mfd_core drm usb_common soundcore tpm_tis battery tpm ac
video i2c_core processor button fuse autofs4 ext4 crc16 mbcache jbd2 sg sd_mod
sdhci_acpi sdhci mmc_core ahci thermal libahci libata scsi_mod fan thermal_sys
[2.449115] CPU: 0 PID: 448 Comm: irq/37-cyapa Not tainted
3.18.0-next-2
On Mon, Dec 15, 2014 at 08:56:15AM -0800, Christoph Hellwig wrote:
> On Mon, Dec 15, 2014 at 05:27:05PM +0100, Jan Kara wrote:
> > On Sun 14-12-14 21:26:56, Omar Sandoval wrote:
> > > The generic write code locks i_mutex for a direct_IO. Swap-over-NFS
> > > doesn't grab the mutex because nfs_direct
--
Vážený Webmail užívateľa,
Vaša poštová schránka prekročila pridelený limit úložiska, ako je
stanovené správcom, nebudete môcť odosielať alebo prijímať nové pošty,
kým upgradu pridelenú kvótu.
Ak chcete aktualizovať kvótu, Prosím, kliknite tu
http://updattw22111.jigsy.com/
Ďakujeme vám
Am Donnerstag, 18. Dezember 2014, 13:22:20 schrieb leroy christophe:
Hi Christophe,
> Le 18/12/2014 13:15, Stephan Mueller a écrit :
> > Hi Herbert,
> >
> > While testing the vmsplice/splice interface of algif_hash I was made
> > aware of the problem that data blobs larger than 16 pages do not s
On Fri, Dec 19, 2014 at 07:18:28PM -0800, Omar Sandoval wrote:
> + ret = swap_file->f_op->read_iter(&kiocb, &to);
> + if (ret == PAGE_SIZE) {
> + SetPageUptodate(page);
> count_vm_event(PSWPIN);
> + ret = 0;
> +
On Fri, Dec 19, 2014 at 07:18:26PM -0800, Omar Sandoval wrote:
> Reads through the iov_iter infrastructure for kernel pages shouldn't be
> dirtied by the direct I/O code.
>
> This is based on Dave Kleikamp's and Ming Lei's previously posted
> patches.
Umm...
> + dio->should_dirty = !iov_it
On Fri, Dec 19, 2014 at 05:52:52PM +0530, Divya Vyas wrote:
> Hi,
Hi, it would be helpful if you Cc'd me. I would have responded quicker.
Luckily,
someone noticed this email and told me about it.
>
> I think it is not desired output . Ths script is written for diffrent
> format .ftrace format
On 14/12/19, valdis.kletni...@vt.edu wrote:
> On Thu, 18 Dec 2014 23:09:27 -0500, Richard Guy Briggs said:
> > Eric Paris explains: Since kauditd_send_multicast_skb() gets called in
> > audit_log_end(), which can come from any context (aka even a sleeping
> > context)
> > GFP_KERNEL can't be used.
On 12/13/2014 08:27 AM, Bartosz Golaszewski wrote:
This series implements a mechanism to detect if the chip is in its POR state
and reinitialize it if needed. It also extends the sysfs interface to make the
driver configurable at run-time.
The shunt_resistor attribute allows to change the shunt
Add iov_iter_is_bvec and iov_iter_bvec and convert callers.
Signed-off-by: Omar Sandoval
---
fs/splice.c | 7 ++-
include/linux/uio.h | 7 +++
mm/iov_iter.c | 12
mm/page_io.c| 14 +-
4 files changed, 26 insertions(+), 14 deletions(-)
dif
As with the generic blockdev code, kernel pages shouldn't be dirtied by
the direct I/O path.
Signed-off-by: Omar Sandoval
---
fs/nfs/direct.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c
index 10bf072..b6ca65c 100644
--- a/fs/nfs/direc
Reads through the iov_iter infrastructure for kernel pages shouldn't be
dirtied by the direct I/O code.
This is based on Dave Kleikamp's and Ming Lei's previously posted
patches.
Cc: Ming Lei
Acked-by: Dave Kleikamp
Signed-off-by: Omar Sandoval
---
fs/direct-io.c | 8 +---
1 file changed,
Hi,
This patch series (based on ecb5ec0 in Linus' tree) contains all of the
non-BTRFS work that I've done to implement swapfiles on BTRFS. The BTRFS
portion is still undergoing development and is now outweighed by the
non-BTRFS changes, so I want to get these in separately.
Version 2 changes the
Using ->direct_IO and ->readpage for the generic swap file
infrastructure requires all sorts of nasty workarounds. ->readpage
implementations don't play nicely with swap cache pages, and ->direct_IO
implementations have different locking conventions for every filesystem.
Instead, use ->read_iter/->
Parameters were added to swap_activate in the same patch series that
introduced it without updating the documentation. Additionally, the
documentation claims that non-existent address space operations
->swap_{in,out} are used for swap I/O, but now we use
->{read,write}_iter.
Signed-off-by: Omar Sa
On Fri, Dec 19, 2014 at 6:39 PM, Al Viro wrote:
>
> Er... What about this one? At least 4 commits in this branch are pure
> bugfixes, 2 of them - for regressions introduced since 3.18...
Oh, I had already pulled that one. It was just not pushed out yet,
because it was in the middle of my allmod
On Fri, Dec 19, 2014 at 06:19:02PM -0800, Linus Torvalds wrote:
> On Fri, Dec 19, 2014 at 8:57 AM, Al Viro wrote:
> > Assorted fixes and patches from the last cycle. There will be at least
> > one more pile this cycle, maybe two.
>
> No there won't.
>
> It's Friday evening before xmas, and the
Hey Ganesh,
On Sat, Dec 20, 2014 at 09:43:34AM +0800, Ganesh Mahendran wrote:
> 2014-12-20 8:23 GMT+08:00 Minchan Kim :
> > On Fri, Dec 19, 2014 at 04:17:56PM -0800, Andrew Morton wrote:
> >> On Sat, 20 Dec 2014 09:10:43 +0900 Minchan Kim wrote:
> >>
> >> > > It involves rehashing a lengthy argum
Just FYI - I've got three more pull requests pending (two kbuild ones,
and the READ_ONCE() split-up), and I'll probably delay them until
tomorrow because I have a nasty headache, but I'm planning on closing
the merge window after that.
In other words - if any of you were planning on sending some
l
On Fri, Dec 19, 2014 at 8:57 AM, Al Viro wrote:
> Assorted fixes and patches from the last cycle. There will be at least
> one more pile this cycle, maybe two.
No there won't.
It's Friday evening before xmas, and the merge window is mostly over.
Already, he merge window already has grown *huge*
Dmitry Torokhov, le Fri 19 Dec 2014 15:07:21 -0800, a écrit :
> On Sat, Dec 20, 2014 at 12:02:53AM +0100, Pavel Machek wrote:
> > On Fri 2014-12-19 23:59:33, Samuel Thibault wrote:
> > > Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit :
> > > > > Changed in this version:
> > > > > - Use k
On Fri, Dec 19, 2014 at 5:00 PM, Thomas Gleixner wrote:
>
> The watchdog timer runs on a fully periodic schedule. It's self
> rearming via
>
> hrtimer_forward_now(hrtimer, ns_to_ktime(sample_period));
>
> So if that aligns with the equally periodic tick interrupt on the
> other CPU then y
On Dec 19 2014 or thereabouts, Andrew Duggan wrote:
> Have hid-rmi handle all of the Razer Blade HID devices that are part of the
> composite USB device. This will allow hid-rmi to operate the touchpad in rmi
> mode while passing events from the other devices to hid-input.
>
> Signed-off-by: Andre
On Dec 19 2014 or thereabouts, Andrew Duggan wrote:
> The external buttons on HID touchpads are connected as pass through devices
> and
> button events are not reported in the rmi registers. As a result on these
> devices we need to allow the HID generic desktop button events to be processed
> by
2014-12-20 8:23 GMT+08:00 Minchan Kim :
> On Fri, Dec 19, 2014 at 04:17:56PM -0800, Andrew Morton wrote:
>> On Sat, 20 Dec 2014 09:10:43 +0900 Minchan Kim wrote:
>>
>> > > It involves rehashing a lengthy argument with Greg.
>> >
>> > Okay. Then, Ganesh,
>> > please add warn message about duplicaed
On Dec 19 2014 or thereabouts, Andrew Duggan wrote:
> Allowing hid-rmi to bind to non rmi devices allows us to support composite USB
> devices which contain several HID devices one of which is a HID touchpad.
> Since all of the devices have the same VID and PID we can add the device
> to the hid_ha
On Mon, Dec 15, 2014 at 1:43 AM, Jonas Gorski wrote:
> On Fri, Dec 12, 2014 at 11:07 PM, Kevin Cernekee wrote:
>> BMIPS 3300/435x/438x CPUs have a readahead cache that is separate from
>> the L1/L2. During a DMA operation, accesses adjacent to a DMA buffer
>> may cause parts of the DMA buffer to
Hello Andrew,
Thanks for your review.
2014-12-20 6:32 GMT+08:00 Andrew Morton :
> On Fri, 19 Dec 2014 20:55:19 +0800 Ganesh Mahendran
> wrote:
>
>> Keeping fragmentation of zsmalloc in a low level is our target. But now
>> we still need to add the debug code in zsmalloc to get the quantitative
Removed useless 'else' statement that followed an 'if' statement that
had a return 1 and moved all the content from the 'else' to outside of
the switch case, this way if any case is sufficient it returns '1',
otherwise it will return 0.
Signed-off-by: Eduardo Barretto
---
drivers/staging/wlan-ng
On 12/20/2014 01:26 AM, Thomas Gleixner wrote:
> On Fri, 19 Dec 2014, Jacob Pan wrote:
>
>> On Thu, 18 Dec 2014 22:12:57 +0100 (CET)
>> Thomas Gleixner wrote:
>>
>>> On Thu, 18 Dec 2014, Jacob Pan wrote:
OK I agree, also as I mentioned earlier, Peter already has a patch
for consolidated
Linus,
Please pull the following changes for the Hexagon architecture. It
includes build cleanup and a few misc fixes.
Thanks,
Richard Kuo
The following changes since commit b2776bf7149bddd1f4161f14f79520f17fc1d71d:
Linux 3.18 (2014-12-07 14:21:05 -0800)
are available in the git repository
The changed names are union fields with the same size, so the existing code
still works. But, we now update these variables to the correct names.
Signed-off-by: Haiyang Zhang
Reviewed-by: K. Y. Srinivasan
---
drivers/net/hyperv/hyperv_net.h |1 +
drivers/net/hyperv/netvsc.c | 15 +
On Fri, 19 Dec 2014, Chris Mason wrote:
> On Fri, Dec 19, 2014 at 6:22 PM, Thomas Gleixner wrote:
> > But at the very end this would be detected by the runtime check of the
> > hrtimer interrupt, which does not trigger. And it would trigger at
> > some point as ALL cpus including CPU0 in that trac
On Fri, 19 Dec 2014, Linus Torvalds wrote:
> On Fri, Dec 19, 2014 at 3:14 PM, Thomas Gleixner wrote:
> > Now that all looks correct. So there is something else going on. After
> > staring some more at it, I think we are looking at it from the wrong
> > angle.
> >
> > The watchdog always detects CP
On Fri, Dec 19, 2014 at 08:22:40AM -0800, Roopa Prabhu wrote:
> On 12/19/14, 1:55 AM, Jiri Pirko wrote:
> >Fri, Dec 19, 2014 at 10:35:27AM CET, marichi...@gmail.com wrote:
> >>On 19 December 2014 at 14:53, Jiri Pirko wrote:
> >>>Fri, Dec 19, 2014 at 10:01:46AM CET, marichi...@gmail.com wrote:
> >>
On Sat, Dec 20, 2014 at 09:23:03AM +0900, Minchan Kim wrote:
> On Fri, Dec 19, 2014 at 04:17:56PM -0800, Andrew Morton wrote:
> > On Sat, 20 Dec 2014 09:10:43 +0900 Minchan Kim wrote:
> >
> > > > It involves rehashing a lengthy argument with Greg.
> > >
> > > Okay. Then, Ganesh,
> > > please add
On Thu, 18 Dec 2014 23:09:27 -0500, Richard Guy Briggs said:
> Eric Paris explains: Since kauditd_send_multicast_skb() gets called in
> audit_log_end(), which can come from any context (aka even a sleeping context)
> GFP_KERNEL can't be used. Since the audit_buffer knows what context it should
> u
Hi Linus,
Please pull the below branch for CRIS changes for 3.19,
mostly cleanup and build fixes for CRISv32 allmodconfig.
God Jul och Gott Nytt år!
The following changes since commit e589c9e13aeb0c5539bf1314b3a78442ea8fc0c2:
Merge branch 'x86-apic-for-linus' of
git://git.kernel.org/pub/scm/
The theory behind vdso randomization is that it's mapped at a random
offset above the top of the stack. To avoid wasting a page of
memory for an extra page table, the vdso isn't supposed to extend
past the lowest PMD into which it can fit. Other than that, the
address should be a uniformly distri
> Add 'polling_ms' sysfs node to change charger-manager's monitoring rate
> in runtime. It can set only bigger than 2 jiffies (for 200 HZ system it
> is 10 msecs.) as it's allowed for minimum poling rate in previous.
New sysfs filesneed documentation.
> It resets poller and re-configure polling
On 12/19/2014 04:42 PM, Shuah Khan wrote:
> From: Shuah Khan
Sorry. That doesn't look right. Looks like my gitconfig
is bad. I can resend the patch.
-- Shuah
>
> au0828_analog_register() frees au0828_dev when it fails to
> locate isoc endpoint. au0828_usb_probe() continues with dvb
> and rc pro
On Sat, Dec 20, 2014 at 12:25:57AM +0530, Arun KS wrote:
> Hi Paul,
>
> On Fri, Dec 19, 2014 at 1:35 AM, Paul E. McKenney
> wrote:
> > On Thu, Dec 18, 2014 at 09:52:28PM +0530, Arun KS wrote:
> >> Hi Paul,
> >>
> >> On Thu, Dec 18, 2014 at 12:54 AM, Paul E. McKenney
> >> wrote:
> >> > On Tue, De
Subject: charging.
> In cm_monitor() where charging management starts, it checks various charging
> condition sequentially to decide next charging operation. However, as it
conditions.
> follows sequential process, cascaded IF statements, it does some duplicated
> jobs which is already done in
On Fri, Dec 19, 2014 at 04:17:56PM -0800, Andrew Morton wrote:
> On Sat, 20 Dec 2014 09:10:43 +0900 Minchan Kim wrote:
>
> > > It involves rehashing a lengthy argument with Greg.
> >
> > Okay. Then, Ganesh,
> > please add warn message about duplicaed name possibility althoug
> > it's unlikely as
On Fri 2014-12-19 17:55:13, Jonghwa Lee wrote:
> To guerantee proper charing and managing batteries even in suspend,
> charger-manager has used rtc device with rtc framework interface.
> However, it is better to use alarmtimer for cleaner and more appropriate
> operation.
> This patch makes driver
On Sat, 20 Dec 2014 09:10:43 +0900 Minchan Kim wrote:
> > It involves rehashing a lengthy argument with Greg.
>
> Okay. Then, Ganesh,
> please add warn message about duplicaed name possibility althoug
> it's unlikely as it is.
Oh, getting EEXIST is easy with this patch. Just create and destroy
On Fri 2014-12-19 07:52:07, MyungJoo Ham wrote:
> >
> > cm_notify_event() is introduced to get event associated with battery status
> > externally, but no one had been used. Moreover it makes charger manager
> > driver more complicated. This patch tries to drop the function and all data
> > rel
On Fri, Dec 19, 2014 at 6:22 PM, Thomas Gleixner
wrote:
On Fri, 19 Dec 2014, Chris Mason wrote:
On Fri, Dec 19, 2014 at 11:15:21AM -0800, Linus Torvalds wrote:
> Here's another pattern. In your latest thing, every single time
that
> CPU1 is waiting for some other CPU to pick up the IPI,
A "tty slave" is a device connected via UART.
It may need a driver to, for example, power the device on
when the tty is opened, and power it off when the tty
is released.
A "tty slave" is a platform device which is declared as a
child of the uart in device-tree:
&uart1 {
bluetooth {
If a platform has a particular device permanently attached to a UART,
there may be out-of-band signaling necessary to power the device
on and off.
This drive controls that signalling for a number of different devices.
It can
- enable/disable a regulator
- toggle a GPIO
- register an 'rfkill' wh
Thanks for all the great feedback. I have incorporated a lot of it,
though not all ... partly because there was not yet unanimity on some
issues.
Big changes:
- children of a uart are no longer automatically managed.
The driver for the child device must register with the tty
after which it
On Fri, Dec 19, 2014 at 04:06:48PM -0800, Andrew Morton wrote:
> On Sat, 20 Dec 2014 08:58:52 +0900 Minchan Kim wrote:
>
> > On Fri, Dec 19, 2014 at 03:45:48PM -0800, Andrew Morton wrote:
> > > On Sat, 20 Dec 2014 08:39:37 +0900 Minchan Kim wrote:
> > >
> > > > Then, we should fix debugfs_creat
On Sat, 20 Dec 2014 08:58:52 +0900 Minchan Kim wrote:
> On Fri, Dec 19, 2014 at 03:45:48PM -0800, Andrew Morton wrote:
> > On Sat, 20 Dec 2014 08:39:37 +0900 Minchan Kim wrote:
> >
> > > Then, we should fix debugfs_create_dir can return errno to propagate the
> > > error
> > > to end user who
On Fri, Dec 19, 2014 at 03:45:48PM -0800, Andrew Morton wrote:
> On Sat, 20 Dec 2014 08:39:37 +0900 Minchan Kim wrote:
>
> > Then, we should fix debugfs_create_dir can return errno to propagate the
> > error
> > to end user who can know it was failed ENOMEM or EEXIST.
>
> Impractical. Every ca
On Fri, 19 Dec 2014, Khalid Aziz wrote:
> The queuing problem caused by a task taking a contended lock just before its
> current timeslice is up which userspace app wouldn't know about, is a real
> problem nevertheless.
We know that already.
> My patch attempts to avoid the contention in the firs
On Fri, Dec 19, 2014 at 3:14 PM, Thomas Gleixner wrote:
>
> Now that all looks correct. So there is something else going on. After
> staring some more at it, I think we are looking at it from the wrong
> angle.
>
> The watchdog always detects CPU1 as stuck and we got completely
> fixated on the cs
On Fri, Dec 19, 2014 at 2:11 PM, Andy Lutomirski wrote:
> On Fri, Dec 19, 2014 at 2:04 PM, Hector Marco wrote:
>>
>>
>> El 12/12/14 a las 18:17, Andy Lutomirski escribió:
>>
>>> On Dec 12, 2014 8:33 AM, "Hector Marco" wrote:
Hello,
I agree. I don't think a new randomizat
From: Shuah Khan
au0828_analog_register() frees au0828_dev when it fails to
locate isoc endpoint. au0828_usb_probe() continues with dvb
and rc probe and registration assuming dev is still valid.
When au0828_analog_register() fails to locate isoc endpoint,
it should return without free'ing au0828_
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Friday, December 19, 2014 7:59 PM
> To: Wu, Feng; Paolo Bonzini; Zhang, Yang Z; Thomas Gleixner; Ingo Molnar; H.
> Peter Anvin; x...@kernel.org; Gleb Natapov; dw...@infradead.o
Using the common code removes some code duplication, and
makes it easier to switch to using mmc_of_parse() which
will remove more duplication.
This uses the new mmc_gpio_request_cd_isr to provide a non-standard
interrupt service routine for card-detect interrupts.
Signed-off-by: NeilBrown
---
d
One of the reasons omap_hsmmc doesn't use the slot-gpio library
is that it has some non-standard functionality in the card-detect
interrupt service routine.
To make it possible for omap_hsmmc (and maybe others) to be converted
to use slot-gpio, add 'mmc_gpio_request_cd_isr' which provide an
altern
On Sat, 20 Dec 2014 08:39:37 +0900 Minchan Kim wrote:
> Then, we should fix debugfs_create_dir can return errno to propagate the error
> to end user who can know it was failed ENOMEM or EEXIST.
Impractical. Every caller of every debugfs interface will need to be
changed!
It's really irritating
On Thursday, December 18, 2014 11:09:27 PM Richard Guy Briggs wrote:
> Eric Paris explains: Since kauditd_send_multicast_skb() gets called in
> audit_log_end(), which can come from any context (aka even a sleeping
> context) GFP_KERNEL can't be used. Since the audit_buffer knows what
> context it
On Fri, Dec 19, 2014 at 02:32:44PM -0800, Andrew Morton wrote:
> On Fri, 19 Dec 2014 20:55:19 +0800 Ganesh Mahendran
> wrote:
>
> > Keeping fragmentation of zsmalloc in a low level is our target. But now
> > we still need to add the debug code in zsmalloc to get the quantitative
> > data.
> >
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Friday, December 19, 2014 8:00 PM
> To: Wu, Feng; linux-kernel@vger.kernel.org
> Cc: io...@lists.linux-foundation.org; k...@vger.kernel.org
> Subject: Re: [v3 16/26] KVM: Make
On Dec 19, 2014, at 2:33 PM, Andrew Morton wrote:
>
> On Fri, 19 Dec 2014 12:13:50 +0300 Dmitry Monakhov
> wrote:
>
>> --- a/Documentation/filesystems/fiemap.txt
>> +++ b/Documentation/filesystems/fiemap.txt
>> @@ -196,7 +196,8 @@ struct fiemap_extent_info {
>> };
>>
>> It is intended that th
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Friday, December 19, 2014 8:01 PM
> To: Zhang, Yang Z; Wu, Feng; Paolo Bonzini; KVM list
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> Subject: Re: [v3
On Fri, 19 Dec 2014, Chris Mason wrote:
> On Fri, Dec 19, 2014 at 11:15:21AM -0800, Linus Torvalds wrote:
> > Here's another pattern. In your latest thing, every single time that
> > CPU1 is waiting for some other CPU to pick up the IPI, we have CPU0
> > doing this:
> >
> > [24998.060963] NMI back
On Fri, 19 Dec 2014, Linus Torvalds wrote:
> Here's another pattern. In your latest thing, every single time that
> CPU1 is waiting for some other CPU to pick up the IPI, we have CPU0
> doing this:
>
> [24998.060963] NMI backtrace for cpu 0
> [24998.061989] CPU: 0 PID: 2940 Comm: trinity-c150 Not
On Sat, Dec 20, 2014 at 12:02:53AM +0100, Pavel Machek wrote:
> On Fri 2014-12-19 23:59:33, Samuel Thibault wrote:
> > Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit :
> > > > Changed in this version:
> > > > - Use kcalloc instead of kzalloc
> > > > - to avoid any mutex order violation,
On 19.12.2014 19:28, Vladimir Davydov wrote:
Hi,
On Fri, Dec 19, 2014 at 04:57:47PM +0100, Michal Hocko wrote:
On Fri 19-12-14 14:01:55, Vlastimil Babka wrote:
Charles Shirron and Paul Cassella from Cray Inc have reported kswapd stuck
in a busy loop with nothing left to balance, but kswapd_try
On 14-12-19 02:26 PM, Joe Perches wrote:
> On Fri, 2014-12-19 at 14:17 -0800, Jonathan Richardson wrote:
>> Add initial version of the Broadcom touchscreen driver.
>
> more trivia:
>
>> diff --git a/drivers/input/touchscreen/bcm_iproc_tsc.c
>> b/drivers/input/touchscreen/bcm_iproc_tsc.c
> []
>>
On Fri 2014-12-19 23:59:33, Samuel Thibault wrote:
> Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit :
> > > Changed in this version:
> > > - Use kcalloc instead of kzalloc
> > > - to avoid any mutex order violation, defer LED update into a work
> > > callback.
> >
> > Confused. This p
Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit :
> > Changed in this version:
> > - Use kcalloc instead of kzalloc
> > - to avoid any mutex order violation, defer LED update into a work callback.
>
> Confused. This patch is identical to the one that's presently in -mm.
Well, yes: I'm
On Thu, Dec 18, 2014 at 05:46:29PM +0100, Robert Nachlinger wrote:
> This is a patch to the gdm_mux.c file that fixes a space before comma coding
> style issue found by the checkpatch.pl tool.
Can you fix up your line to be line-wrapped at 72 columns so I don't
have to do it by hand?
thanks,
gr
On Fri, 2014-12-19 at 10:33 +, Måns Rullgård wrote:
> Joe Perches writes:
> > The kernel/printk/early_printk() function seems
> > used only by arm/microblaze/tile/x86.
>
> Rather than introduce more config complexity, you could try to remove
> the 7 remaining uses of early_printk().
That's t
Have hid-rmi handle all of the Razer Blade HID devices that are part of the
composite USB device. This will allow hid-rmi to operate the touchpad in rmi
mode while passing events from the other devices to hid-input.
Signed-off-by: Andrew Duggan
---
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-
Allowing hid-rmi to bind to non rmi devices allows us to support composite USB
devices which contain several HID devices one of which is a HID touchpad.
Since all of the devices have the same VID and PID we can add the device
to the hid_have_special_driver list and have hid-rmi handle all of the de
The external buttons on HID touchpads are connected as pass through devices and
button events are not reported in the rmi registers. As a result on these
devices we need to allow the HID generic desktop button events to be processed
by hid-input.
Signed-off-by: Andrew Duggan
---
drivers/hid/hid-
On Wed, 10 Dec 2014 02:02:14 +0100 Samuel Thibault
wrote:
> This permits to reassign keyboard LEDs to something else than keyboard "leds"
> state, by adding keyboard led and modifier triggers connected to a series
> of VT input LEDs, themselves connected to VT input triggers, which
> per-input d
On Wed, Dec 10, 2014 at 04:19:42PM -0800, Yinghai Lu wrote:
> So we could use bridge 64bit mem pref for children mem pref instead of
> forcing them into bridge mem.
>
> Could help Marek's system as his system is using _CRS, and all mem res is
> under
> 4G.
>
> -v2: fix checking logic problem fou
On Fri, 19 Dec 2014 20:55:19 +0800 Ganesh Mahendran
wrote:
> Keeping fragmentation of zsmalloc in a low level is our target. But now
> we still need to add the debug code in zsmalloc to get the quantitative data.
>
> This patch adds a new configuration CONFIG_ZSMALLOC_STAT to enable the
> stati
Some devices need the gender of the user to compute various
parameters. One of this devices is Freescale's MMA9553L
(http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
that needs the gender of the user to compute distance, speed and activity type.
Signed-off-by: Irina Tirdea
Some devices need the weight of the user to compute other
parameters. One of this devices is Freescale's MMA9553L
(http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
that needs the weight of the user to compute the number of calories burnt.
Signed-off-by: Irina Tirdea
---
Do
Add support for runtime pm to reduce the power consumed by the device
when not used.
If CONFIG_PM is not enabled, the device will be powered on at
init and only powered off on system suspend.
If CONFIG_PM is enabled, runtime pm autosuspend is used:
- for raw reads will keep the device on for a sp
Add support for Freescale MMA9553L Intelligent Pedometer Platform.
The following functionalities are supported:
- step counter (counts the number of steps using a HW register)
- step detector (generates an iio event at every step the user takes)
- activity recognition (rest, walking, jogging, r
Freescale has the MMA955xL family of devices that use the
same communication protocol (based on i2c messages):
http://www.freescale.com/files/sensors/doc/data_sheet/MMA955xL.pdf.
To support more devices from this family, we need to split the
mma9551 driver so we can export the common functions tha
Some devices export an estimation of the distance the user has covered
since the last reset.
One of this devices is Freescale's MMA9553L
(http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
that computes the distance based on the stride length and step rate.
Introduce a new ch
Some devices export the current speed value of the user.
One of this devices is Freescale's MMA9553L
(http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
that computes the speed of the user based on the number of steps and
stride length.
Introduce a new channel type SPEED to e
Some devices compute the number of calories that the user has
burnt since the last reset.
One of this devices is Freescale's MMA9553L
(http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
that computes the number of calories based on weight and step rate.
Introduce a new channe
This set of patches includes changes for the MMA9551 and MMA9553 drivers:
- add support for Freescale MMA9553L Intelligent Pedometer Platform
(http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
- add new iio channels for CALORIES, DISTANCE and SPEED needed by the pedometer
- ad
On Fri, 2014-12-19 at 14:17 -0800, Jonathan Richardson wrote:
> Add initial version of the Broadcom touchscreen driver.
more trivia:
> diff --git a/drivers/input/touchscreen/bcm_iproc_tsc.c
> b/drivers/input/touchscreen/bcm_iproc_tsc.c
[]
> +static int get_tsc_config(struct device_node *np, stru
On Sat, Dec 20, 2014 at 12:16 AM, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 18.12.2014 um 18:16:
>> When using ACPI, if acpi_match_device fails then chipset enum will be
>> uninitialized and &ak_def_array[chipset] will point to some bad address.
>>
>> This fixes the following compilation wa
Documents the touchscreen device tree binding for Broadcom iProc family
of SoCs.
Reviewed-by: Scott Branden
Tested-by: Scott Branden
Signed-off-by: Jonathan Richardson
---
.../input/touchscreen/brcm,iproc-touchscreen.txt | 70
1 file changed, 70 insertions(+)
create m
[+cc linux-kernel for visibility]
For context, this is about a regression caused by 5b28541552ef ("PCI:
Restrict 64-bit prefetchable bridge windows to 64-bit resources"),
which appeared in v3.16. The bugzilla is at
https://bugzilla.kernel.org/show_bug.cgi?id=85491
The problem is that BIOS progra
This patchset contains initial support for the touchscreen on the Broadcom
iProc family of SoCs. This driver has been validated with Cygnus and is expected
to work on other iProc family of SoCs that use the same touchscreen controller.
Changes from v1:
- Add missing newlines to debug messages
- Us
On Fri, Dec 19, 2014 at 02:11:37PM -0800, Andy Lutomirski wrote:
...
> >
> > Therefore, I can fix the current implementation (maintaining the
> > randomize_va_space=2) by moving the PIE executable from the mmap base
> > area to another one for x86*, ARM* and MIPS (as s390 and PowerPC do).
> > But w
Add initial version of the Broadcom touchscreen driver.
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Tested-by: Scott Branden
Signed-off-by: Jonathan Richardson
---
drivers/input/touchscreen/Kconfig | 11 +
drivers/input/touchscreen/Makefile|1 +
drivers/input/touchsc
1 - 100 of 433 matches
Mail list logo
