On 06/15/2014 10:42 AM, Yang,Wei wrote:
Its v4, sorry for missing it in subject.
Alan, How about this version?
Cheers
Wei
Regards
Wei
On 06/15/2014 10:40 AM, wei.y...@windriver.com wrote:
From: Yang Wei wei.y...@windriver.com
While loading g_mass_storage module, the following warning
is
Hi Simon,
How about this patch?
Thanks
Wei
On 06/12/2014 01:16 PM, wei.y...@windriver.com wrote:
From: Yang Wei wei.y...@windriver.com
The commit b02d735bf was to rearrange the device-tree entries, and
assumed that these entries are sorted in the ascending order. but
acctually when I was
On Tue, Jun 17, 2014 at 12:14:18AM +0200, Rickard Strandqvist wrote:
2014-06-16 21:09 GMT+02:00 Dan Carpenter dan.carpen...@oracle.com:
On Mon, Jun 16, 2014 at 10:01:14PM +0300, Dan Carpenter wrote:
No one calls U14DriverName() so just delete this function.
Oh. This is a userspace
Simon, I missed kexec string in subject, so please ignore this
version. I would resend it with adding kexec in subject.
Thanks
Wei
On 06/17/2014 02:01 PM, Yang,Wei wrote:
Hi Simon,
How about this patch?
Thanks
Wei
On 06/12/2014 01:16 PM, wei.y...@windriver.com wrote:
From: Yang Wei
From: Yang Wei wei.y...@windriver.com
The commit b02d735bf was to rearrange the device-tree entries, and
assumed that these entries are sorted in the ascending order. but
acctually when I was validating kexec and kdump, the order of
serial node still is changed. We should not only compare the
Am 16.06.2014 23:30, schrieb Francois Romieu:
Stefan Priebe - Profihost AG s.pri...@profihost.ag :
[...]
That sounds great! Is there anything I can do or some code I can port to
veth?
You may add an empty handler for .ndo_poll_controller in drivers/net/veth.c
and give it a try on current
On Mon, Jun 16, 2014 at 11:23:13PM -0400, Nicholas Krause wrote:
Signed-off-by: Nicholas Krause xerofo...@gmail.com
---
drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
On 17.06.2014 07:39, Ben Skeggs wrote:
[snip]
In any case, I encountered the oops myself earlier (absolutely nothing
to do with that commit) and fixed it here. I've sent it onto Dave for
the next -fixes merge, so hopefully it'll help your case too.
Has this anything to do with
Hi,
On 06/17/2014 02:38 AM, Vincent Palatin wrote:
Map V4L2_CID_TILT_RELATIVE and V4L2_CID_PAN_RELATIVE to the standard UVC
CT_PANTILT_ABSOLUTE_CONTROL terminal control request.
s/ABSOLUTE/RELATIVE in the commit message here.
Otherwise looks good to me.
Regards,
Hans
Tested by plugging
Hello,
I have a Business Proposal for you worth the sum of $40,000,000.00 USD
Please reply for more info. Email: suzukiyuki4...@yahoo.co.jp
Regards,
Mr. Takuya Suzuki Yuki
Zero Problem 2014, Cakupan Semesta
ttm_tt_cache_flush's implementation was removed in 2009 by commit
c9c97b8c, but its declaration has been hiding in ttm_bo_driver.h since
then.
It has been surviving in the dark for too long now ; give it the mercy
blow.
Signed-off-by: Alexandre Courbot acour...@nvidia.com
Reviewed-by: Thierry
Hi Tomasz,
Hi,
On 10.05.2014 08:56, Pankaj Dubey wrote:
From: Young-Gun Jang yg1004.j...@samsung.com
Add support for mapping Samsung Power Management Unit (PMU) base
address from device tree. This patch also adds helper function as
get_exynos_pmuregmap. This function can be used by
The one-bit bitfields are assigned true (1) or false (0) and checked
for them respectively. While it should work either way and -1 is true
as well it is more clear to see what's going on when using an unsigned int
because 1 doesn't silently become -1 behind the label true.
Signed-off-by: Martin
On Mon, 2014-06-16 at 23:35 -0600, Alex Williamson wrote:
Any idea what an off-the-shelf Asus motherboard would be doing with an
RMRR on the Intel HD graphics?
dmar: RMRR base: 0x00bb80 end: 0x00bf9f
IOMMU: Setting identity map for device :00:02.0 [0xbb80 -
On 06/16/2014 11:23 AM, Peter Griffin wrote:
This patch fixes two problems: -
1) The device tree isn't currently providing sti-ethclk which is
required by the dwmac glue code to correctly configure the ethernet
PHY clock speed.
This means depending on what the bootloader/jtag has
Some machines'(E,G Lenovo Z480) ECs are not stable during boot up
and causes battery driver fails to be loaded due to failure of getting
battery information from EC sometimes. After several retries, the
operation will work. This patch is to retry to get battery information 5
times if the first try
On 16/06/14 12:22, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140613 09:17]:
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Cc: Andrew Morton a...@linux-foundation.org
Acked-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Sathya Prakash M R sath...@ti.com
On Tue, Jun 17, 2014 at 9:04 AM, David Woodhouse dw...@infradead.org wrote:
On Mon, 2014-06-16 at 23:35 -0600, Alex Williamson wrote:
Any idea what an off-the-shelf Asus motherboard would be doing with an
RMRR on the Intel HD graphics?
dmar: RMRR base: 0x00bb80 end: 0x00bf9f
This patch adds the devicetree bindings for cc2520 driver.
Signed-off-by: Varka Bhadram var...@cdac.in
---
.../devicetree/bindings/net/ieee802154/cc2520.txt | 26
1 file changed, 26 insertions(+)
create mode 100644
This patch adds the driver support for TI cc2520 radio.
Few points about CC2520:
- The CC2520 is TI's second generation IEEE 802.15.4 RF transceiver
for the 2.4 GHz unlicensed ISM band.
- DSSS baseband modem with 250 kbps data rate
- Programmable output power up
Hi,
This patch series adds the driver support for TI cc2520 radio and also
adds the device tree bindings for cc2520 driver.
changes:
- Improvements in the locking mechanism in Tx and SFD ISR.
- Proper checkings for GPIO pins.
- avoids the memory leak for priv.
-
This patch creates a hook into kernel build system for cc2520 radio.
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ieee802154/Kconfig | 11 +++
drivers/net/ieee802154/Makefile |1 +
2 files changed, 12 insertions(+)
diff --git a/drivers/net/ieee802154/Kconfig
On Mon, 16 Jun 2014, Darren Hart wrote:
On Fri, 2014-06-13 at 11:44 +0200, Thomas Gleixner wrote:
Two general concerns, we appear to be eliminating both the force_take
and the retry.
The force_take only occurs if TID==0, and that is covered here in a
cleaner way, so I believe we are good
On Tue, 2014-06-17 at 09:15 +0200, Daniel Vetter wrote:
We've always been struggling with stolen handling, and we've' always
been struggling with vt-d stuff. Also pass-through seems to be a major
pain (I've never tried myself). Given all that I'm voting for keeping
the RMRR and everything else
On Mon, Jun 16, 2014 at 11:45:42PM -0400, Waiman Long wrote:
On 06/16/2014 04:59 PM, Kirill A. Shutemov wrote:
On Mon, Jun 16, 2014 at 11:49:34PM +0300, Kirill A. Shutemov wrote:
On Mon, Jun 16, 2014 at 03:35:48PM -0400, Waiman Long wrote:
In the __split_huge_page_map() function, the check for
Hi,
On Tue, Jun 17, 2014 at 10:09:52AM +0900, Joonsoo Kim wrote:
[...]
To fix the problem, I introduces object status buffer on each slab.
With this, we can track object status precisely, so slab leak detector
would not access active object and no kernel oops would occur.
Memory overhead
* Tomi Valkeinen tomi.valkei...@ti.com [140617 00:10]:
On 16/06/14 12:22, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140613 09:17]:
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Cc: Andrew Morton a...@linux-foundation.org
Acked-by: Rajendra Nayak
The init_data and of_node fields of the axp2xx_matches tables are filled
at each device probe by the axp20x_regulator_parse_dt function (which then
calls the of_regulator_match function).
This means we can probe a new device and consider data initialized during
the probe of another device as
Add support for the AXP221 PMIC device to the existing AXP20x driver.
The AXP221 defines a new set of registers, power supplies and regulators,
but most of the API is similar to the AXP20x ones.
The AXP20x irq chip definition is reused, though some interrupts are not
available in the AXP221.
Make use of the devm_regulator_set_register instead of registering each
regulator provided by the PMIC.
This also solves a self dependency issue where one regulator of the PMIC
is used as a supply for anoher regulator provided by the same PMIC.
Signed-off-by: Boris BREZILLON
PMIC devices often provide several regulators, and these regulators are
all using the same regmap and are all attached to the same device (the
PMIC device).
Add helper functions (both simple and resource managed versions) to
register and unregister such kind of regulator set.
This implementation
Add x-powers,axp221 compatible string to the AXP20x DT bindings
documentation.
Signed-off-by: Boris BREZILLON boris.brezil...@free-electrons.com
---
Documentation/devicetree/bindings/mfd/axp20x.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hello,
This patch series adds basic support for X-Powers' AXP221 PMIC.
At the moment the MFD device only exposes AXP221 regulators but other
subdevices might be added later.
Best Regards,
Boris
Changes since v3:
- rework mfd probe to avoid multiple AXP variant tests
- add new compatible
Rework the AXP20X_ macros to support the several chip families, so that
each family can define it's own set of regulators, and regulator matches.
Pass a match table to the axp20x_regulator_parse_dt function instead of
statically using the axp20x match table.
Signed-off-by: Boris BREZILLON
Add AXP221 regulator definitions and choose the appropriate definitions
according to the variant id passed by the MFD device.
Signed-off-by: Boris BREZILLON boris.brezil...@free-electrons.com
---
drivers/regulator/axp20x-regulator.c | 98 +---
1 file changed, 90
On 17 June 2014 03:04, micky micky_ch...@realsil.com.cn wrote:
On 06/16/2014 08:40 PM, Ulf Hansson wrote:
On 16 June 2014 11:09, micky micky_ch...@realsil.com.cn wrote:
On 06/16/2014 04:42 PM, Ulf Hansson wrote:
@@ -36,7 +37,10 @@ struct realtek_pci_sdmmc {
struct rtsx_pcr
On 17/06/2014 05:39, Jongsung Kim :
On 06/17/2014 06:28 AM, Sören Brinkmann wrote:
Shouldn't it be sufficient to replace 'MACB_BIT(RCOMP) with
'MACB_RX_INT_FLAGS'
to clear all the RX IRQ flags.
I'm afraid not.
You know, this driver initially targeted only GEMs configured with
From: Jiancheng Xue xuejianch...@huawei.com
Add necessary binding documentation SATA PHY on Hisilicon hix5hd2 soc.
Signed-off-by: Jiancheng Xue xuejianch...@huawei.com
Signed-off-by: Zhangfei Gao zhangfei@linaro.org
---
.../devicetree/bindings/phy/hix5hd2-sata-phy.txt | 26
On Sun, 15 Jun 2014, Hugh Dickins wrote:
Date: Sun, 15 Jun 2014 18:28:00 -0700 (PDT)
From: Hugh Dickins hu...@google.com
To: Andrew Morton a...@linux-foundation.org
Cc: Lukas Czerner lczer...@redhat.com,
Namjae Jeon namjae.j...@samsung.com, linux-kernel@vger.kernel.org
Subject: [PATCH]
From: Jiancheng Xue xuejianch...@huawei.com
Add hix5hd2-sata-phy driver on Hisilicon hix5hd2 soc.
Signed-off-by: Jiancheng Xue xuejianch...@huawei.com
Signed-off-by: Zhangfei Gao zhangfei@linaro.org
---
drivers/phy/Kconfig|8 ++
drivers/phy/Makefile |1 +
Jiancheng Xue (2):
Documentation: Document Hisilicon hix5hd2 sata PHY
phy: add hix5hd2-sata-phy driver
.../devicetree/bindings/phy/hix5hd2-sata-phy.txt | 26 +++
drivers/phy/Kconfig|8 +
drivers/phy/Makefile |1 +
On Mon, 16 Jun 2014, Dan Carpenter wrote:
Adding --param allow-store-data-races=0 to the GCC options for the
kernel breaks C=1 because Sparse isn't expecting a GCC option with that
format.
It thinks allow-store-data-races=0 is the name of the file we are trying
to test. Try use Sparse on
On Monday 16 June 2014 09:17:11 Peter Hurley wrote:
tty_wait_until_sent_from_close() drops the tty lock while waiting
for the tty driver to finish sending previously accepted data (ie.,
data remaining in its write buffer and transmit fifo).
However, dropping the tty lock is a hold-over from
Hi,
On 06/17/2014 04:43 AM, xiaofeng.yan wrote:
[...]
The basic ideas are (warning! This is an over-simplification of the algorithm!
:)
- You assign runtime and period to each SCHED_DEADLINE task as usual
- Each task is guaranteed to receive its runtime every period
- You can also define a
Dear Email User,
This message is from the Database Information Technology Service Messaging
Center, to all our e-mail account users. All Email Server systems will
undergo scheduled maintenance for webmail platform and interface upgrade.
Access to your mailbox via our EMail Portal will be
On 16.06.2014 04:23, schrieb Tyler Hall:
The commit slip: Fix deadlock in write_wakeup fixes a deadlock caused
by a change made in both slcan and slip. This is a direct port of that
fix.
I don't know if it is still needed, but for the slcan part, you can add my:
Tested-by: Andre Naujoks
Hi,
I observe the below warnings while trying to boot Exynos5420 based boards
since yesterday's linux-next (next-20140616) using multi_v7_defconfig. Looks
like it is triggered by the commit 56e6921829 (CPU hotplug, smp:
flush any pending IPI callbacks before CPU offline). Any ideas?
Driver for the TI TMP103.
The TI TMP103 is similar to the TMP102. It differs from the TMP102
by having only 8 bit registers.
Signed-off-by: Heiko Schocher h...@denx.de
---
Cc: Jean Delvare kh...@linux-fr.org
Cc: Guenter Roeck li...@roeck-us.net
Cc: linux-kernel@vger.kernel.org
Cc:
On Tue, Jun 17, 2014 at 08:21:31AM +0100, David Woodhouse wrote:
On Tue, 2014-06-17 at 09:15 +0200, Daniel Vetter wrote:
We've always been struggling with stolen handling, and we've' always
been struggling with vt-d stuff. Also pass-through seems to be a major
pain (I've never tried
On Mon, 2014-06-16 at 09:02 -0700, Josh Triplett wrote:
On Mon, Jun 16, 2014 at 01:43:06PM +0300, Andy Shevchenko wrote:
Very dumb patch to just skip --param allow-store-data-races=0 introduced in
newest Linux kernel buildsystem.
Actually the option is present in few GCC versions and
From: Arnd Bergmann
On Monday 16 June 2014 09:17:11 Peter Hurley wrote:
tty_wait_until_sent_from_close() drops the tty lock while waiting
for the tty driver to finish sending previously accepted data (ie.,
data remaining in its write buffer and transmit fifo).
However, dropping the tty
On June 16, 2014 14:28, Lee Jones wrote:
+#ifndef _DA9150_CHARGER_H
+#define _DA9150_CHARGER_H
Two '_'s are normally preferred.
Ok, can change it accordingly.
+#include linux/device.h
+#include linux/i2c.h
What are you using this for?
Nothing. Will remove them. Thanks.
On 06/17/2014 04:24 AM, Guenter Roeck wrote:
mips:allmodconfig fails in 3.16-rc1 with lots of undefined symbols.
arch/mips/net/bpf_jit.c: In function 'is_load_to_a':
arch/mips/net/bpf_jit.c:559:7: error: 'BPF_S_LD_W_LEN' undeclared (first use in
this function)
arch/mips/net/bpf_jit.c:559:7:
Remove redundant return value settings 'ret = 0;' in the function
try_to_bring_up_master(), since it has already been set to zero.
Signed-off-by: Liu Ying ying@freescale.com
---
drivers/base/component.c |2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/base/component.c
Arnd, Olof, Kevin,
As advised by Olof, here is the interesting updated on PWM drivers for AT91
resent after 3.16-rc1 release. Delaying the inclusion of this material has
solved all the issues with dependecies that previous pull-request had ([GIT
PULL] at91: drivers for 3.16 #1).
I remind you
Hi Varka,
you are on v2 not v1. :-)
On Tue, Jun 17, 2014 at 12:44:56PM +0530, Varka Bhadram wrote:
This patch adds the driver support for TI cc2520 radio.
Few points about CC2520:
- The CC2520 is TI's second generation IEEE 802.15.4 RF transceiver
for the 2.4 GHz unlicensed
Doug,
On Fri, 2014-06-13 at 08:22 -0700, Doug Anderson wrote:
On Fri, Jun 13, 2014 at 1:08 AM, Paul Bolle pebo...@tiscali.nl wrote:
On Wed, 2014-06-11 at 08:11 -0700, Doug Anderson wrote:
This is a config option on the ChromeOS EC
https://chromium.googlesource.com/chromiumos/platform/ec.
Hi Steve,
Although I have merged this into cifs-2.6.git for-next, in my testing
I am also seeing this fail with vers=3.0 (and probably 2.0 and 2.1) so
I would like to fix that too (and mfsymlinks may be at least as
important there)
Thanks! When can we expect this to be proposed for 3.16 (and
On Monday 16 June 2014 07:34 PM, Santosh Shilimkar wrote:
Sricharan,
On Monday 16 June 2014 07:23 AM, Sricharan R wrote:
This series does some cleanups, fixes for handling two interrupts
getting mapped twice to same crossbar and provides support for
hardwired IRQ and crossbar definitions.
Instead of allowing public keys, with certificates signed by any
key on the system trusted keyring, to be added to a trusted keyring,
this patch further restricts the certificates to those signed only by
builtin keys on the system keyring.
This patch defines a new option 'builtin' for the kernel
Instead of allowing public keys, with certificates signed by any key on
the system trusted keyring, to be added to a trusted keyring, this patch
set further restricts the certificates to those signed by a particular key
or builtin keys on the system keyring.
This patch defines a new kernel
On 16/06/14 14:43, Mimi Zohar wrote:
On Thu, 2014-06-12 at 23:17 +0300, Dmitry Kasatkin wrote:
Instead of allowing public keys, with certificates signed by any
key on the system trusted keyring, to be added to a trusted keyring,
this patch further restricts the certificates to those signed by
Key id matching will also be used in the following patch.
To avoid code duplication this patch moves functionality
to a separate function.
Signed-off-by: Dmitry Kasatkin d.kasat...@samsung.com
---
crypto/asymmetric_keys/asymmetric_keys.h | 2 ++
crypto/asymmetric_keys/asymmetric_type.c | 50
Instead of allowing public keys, with certificates signed by any
key on the system trusted keyring, to be added to a trusted keyring,
this patch further restricts the certificates to those signed by a
particular key on the system keyring.
This patch defines a new kernel parameter 'keys_ownerid'
On Mon 16-06-14 16:52:45, Don Zickus wrote:
[...]
Michal, do you remember why we needed preempt here? I wouldn't think it
mattered as we are not doing anything per-cpu specific.
Yes, you are right. Preempt can be enabled because we are always
accessing watchdog_ev on a specific cpu so
On Jun 15, 8:43pm, Curtis wrote:
} Subject: Re: [Scst-devel] ANNOUNCE: Hugepage (HPD) block device driver.
Greg,
Hi Curtis, hope your is starting out well.
this project looks quite interesting, and I hope to try it out soon,
however I do have one question, though it may expose my ignorance
The function tries to split a key / value from the given argument where
delimiter can be either ' ' (space) or '=' (equal sign).
It will be useful later as well.
Signed-off-by: Andy Shevchenko andriy.shevche...@linux.intel.com
---
lib.c | 23 ++-
1 file changed, 14
There is a dumb fix to avoid --param option and make sparse survive.
Since v1:
- added patch 1/2
- handle both --param=* and --param *
Andy Shevchenko (2):
lib.c: introduce split_value_from_arg helper
lib.c: skip --param parameters
lib.c | 38 --
1
Very dumb patch to just skip --param allow-store-data-races=0 introduced in
newer GCC versions.
Without this patch sparse recognizes parameter of the --param option as a file
name which obviously couldn't be found.
The patch for easy implementation's sake slightly changed behaviour of
--version.
Add trace events for the power allocator governor and the power actor
interface of the cpu cooling device.
Cc: Zhang Rui rui.zh...@intel.com
Cc: Eduardo Valentin edubez...@gmail.com
Cc: Steven Rostedt rost...@goodmis.org
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Ingo Molnar mi...@redhat.com
Document struct thermal_zone_device and struct thermal_governor fields
and their use by the thermal framework code.
Cc: Zhang Rui rui.zh...@intel.com
Cc: Eduardo Valentin edubez...@gmail.com
Signed-off-by: Javi Merino javi.mer...@arm.com
---
Hi linux-pm,
This patch is independent of the whole
Hi Sachin,
On 06/17/2014 01:39 PM, Sachin Kamat wrote:
Hi,
I observe the below warnings while trying to boot Exynos5420 based boards
since yesterday's linux-next (next-20140616) using multi_v7_defconfig. Looks
I guess you meant next-20140617.
like it is triggered by the commit 56e6921829
A governor may need to store its current state between calls to
throttle(). That state depends on the thermal zone, so store it as
private data in struct thermal_zone_device.
The governors may have two new ops: bind_to_tz() and unbind_from_tz().
When provided, these functions let governors do
Introduce a power actor for cpus. It has a basic power model to get
the current power utilization and uses cpufreq cooling devices to set
the desired power. It uses the current frequency (as reported by
cpufreq) as well as load and OPPs for the power calculations. The
cpus must have registered
Hi linux-pm,
The power allocator governor allocates device power to control
temperature. This requires transforming performance requests into
requested power, which we do with the aid of power models. Patch 4
(thermal: add a basic cpu power actor) implements a simple power model
for cpus. The
The power allocator governor is a thermal governor that controls system
and device power allocation to control temperature. Conceptually, the
implementation divides the sustainable power of a thermal zone among
all the heat sources in that zone.
This governor relies on power actors, entities
This patch introduces the Power Actor API in the thermal framework.
With it, devices that can report their power consumption and control
it can be registered. This base interface is meant to be used to
derive specific power actors, such as a cpu power actor.
Cc: Zhang Rui rui.zh...@intel.com
Cc:
From: Punit Agrawal punit.agra...@arm.com
Introduce an optional property called, sustainable-power, which
represents the power (in mW) which the thermal zone can safely
dissipate.
If provided the property is parsed and associated with the thermal
zone via the thermal zone parameters.
Cc: Zhang
Switch to using the Type-B Multi-Touch protocol.
Reviewed-by: Henrik Rydberg rydb...@euromail.se
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 125 ++
1 file changed, 94 insertions(+), 31 deletions(-)
diff --git
Hi Dmitry,
These are the pending patches that didn't go through in the 3.16 merge window.
Please queue them for -next. Thanks.
The series does the following
- convert to Type-B multi touch protocol
- support upto 5 fingers with hardware supplied tracking IDs
- device tree support
Tony,
The
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts | 4 ++--
1 file changed, 2 insertions(+), 2
Some variants of the Pixcir touch controller support upto 5
simultaneous fingers and hardware tracking IDs. Prepare the driver
for that.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 74 ---
include/linux/input/pixcir_ts.h
Provide device tree support and binding information.
Also provide support for a new chip pixcir_tangoc.
Signed-off-by: Roger Quadros rog...@ti.com
---
.../bindings/input/touchscreen/pixcir_i2c_ts.txt | 26
.../devicetree/bindings/vendor-prefixes.txt| 1 +
-next (next-20140616) using multi_v7_defconfig. Looks
I guess you meant next-20140617.
I meant I started observing this warning next-20140616 onwards
(next-20140617 as well).
like it is triggered by the commit 56e6921829 (CPU hotplug, smp:
flush any pending IPI callbacks before CPU offline
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
On MIPS calls to _mcount in modules generate 2 instructions to load
the _mcount address (and therefore 2 relocations). The mcount_loc
table should only reference the first of these, so the second is
filtered out by checking the relocation offset and ignoring ones that
immediately follow the
On 04/10/2014 10:37 PM, Andy Lutomirski wrote:
It occurs to me that, before going nuts with these kinds of flags, it
may pay to just try to fix the /proc/self/fd issue for real -- we
could just make open(/proc/self/fd/3, O_RDWR) fail if fd 3 is
read-only. That may be enough for the file
* Roger Quadros rog...@ti.com [140617 02:33]:
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
This should be fine to queue along with the
* Roger Quadros rog...@ti.com [140617 02:33]:
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
This too:
Acked-by: Tony Lindgren
Hi,
On Tue, Jun 17, 2014 at 02:45:42PM +0530, Varka Bhadram wrote:
On 06/17/2014 02:11 PM, Alexander Aring wrote:
Hi Varka,
...
+
+/* Generic Functions */
+static int
+cc2520_cmd_strobe(struct cc2520_private *priv, u8 cmd)
+{
* Roger Quadros rog...@ti.com [140617 02:33]:
Hi Dmitry,
These are the pending patches that didn't go through in the 3.16 merge window.
Please queue them for -next. Thanks.
The series does the following
- convert to Type-B multi touch protocol
- support upto 5 fingers with hardware
On 06/17/2014 12:51 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [140617 02:33]:
Hi Dmitry,
These are the pending patches that didn't go through in the 3.16 merge
window.
Please queue them for -next. Thanks.
The series does the following
- convert to Type-B multi touch protocol
On Mon, Jun 16, 2014 at 11:29:38PM +0100, Abhimanyu Kapur wrote:
Add support for debug communications channel based
hvc console for arm64 cpus.
Should we be setting MDSCR_EL1.TDCC to prevent userspace access to the DCC?
Signed-off-by: Abhimanyu Kapur abhim...@codeaurora.org
---
On 06/13/2014 05:33 PM, David Herrmann wrote:
On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski l...@amacapital.net wrote:
Isn't the point of SEAL_SHRINK to allow servers to mmap and read
safely without worrying about SIGBUS?
No, I don't think so.
The point of SEAL_SHRINK is to prevent a file
On 06/17/2014 03:03 PM, Sachin Kamat wrote:
Below is an updated patch, please let me know how it goes. (You'll have to
revert c47a9d7cca first, and then 56e692182, before trying this patch).
I am unable to apply your below patch on top of the above 2 reverts.
Applying: CPU hotplug, smp:
On Mon, Jun 16, 2014 at 11:49:18PM +0200, Stephen Warren wrote:
On 06/04/2014 05:32 AM, Mikko Perttunen wrote:
This makes the SATA PLL be controlled by hardware instead of software.
This is required for working SATA support.
Peter, could you please take patches 4 and 5 through the clock
At Tue, 17 Jun 2014 09:54:07 +1000,
Benjamin Herrenschmidt wrote:
On Mon, 2014-06-16 at 17:35 +1000, Benjamin Herrenschmidt wrote:
I somewhat doubt that this (and 5:5:5) actually work, do they ? the
green gets split into two separate fields, which we can't express
properly here...
So
Hi
On Tue, Jun 17, 2014 at 11:54 AM, Florian Weimer fwei...@redhat.com wrote:
On 06/13/2014 05:33 PM, David Herrmann wrote:
On Fri, Jun 13, 2014 at 5:17 PM, Andy Lutomirski l...@amacapital.net
wrote:
Isn't the point of SEAL_SHRINK to allow servers to mmap and read
safely without worrying
On 06/17/2014 12:01 PM, David Herrmann wrote:
I don't think this is what potential users expect because mlock requires
capabilities which are not available to them.
A couple of weeks ago, sealing was to be applied to anonymous shared memory.
Has this changed? Why should *reading* it trigger
Hi
On Tue, Jun 17, 2014 at 12:04 PM, Florian Weimer fwei...@redhat.com wrote:
On 06/17/2014 12:01 PM, David Herrmann wrote:
I don't think this is what potential users expect because mlock requires
capabilities which are not available to them.
A couple of weeks ago, sealing was to be applied
1 - 100 of 2174 matches
Mail list logo
