On 2014/11/13 21:06, Thomas Gleixner wrote:
> On Thu, 13 Nov 2014, Li, Aubrey wrote:
>
>> On 2014/11/13 17:10, Thomas Gleixner wrote:
>>> On Thu, 13 Nov 2014, Peter Zijlstra wrote:
On Wed, Nov 12, 2014 at 10:09:47PM +0100, Thomas Gleixner wrote:
But sure, we can add suspend notifiers to
On 10/30, Tomeu Vizoso wrote:
> @@ -2145,6 +2218,16 @@ struct clk *__clk_register(struct device *dev, struct
> clk_hw *hw)
> }
> EXPORT_SYMBOL_GPL(__clk_register);
>
> +static void __clk_free_clk(struct clk *clk)
> +{
> + struct clk_core *core = clk->core;
> +
> +
Hi!
> > > > Do you have an example client that can talk to ofonod?
> > >
> > > I have not yet played with userland stuff. You could try
> > > telepathy-ring, which integrates the ofono into the telepathy
> > > framework.
> >
> > Ok, I took a look, and telepathy-ring is not in debian, and has
>
On pią, 2014-11-14 at 11:53 +0900, Inki Dae wrote:
> On 2014년 11월 07일 22:53, Krzysztof Kozlowski wrote:
> > Add runtime Power Management to the Exynos DSI driver so the LCD power
> > domain could be turned off.
> >
> > This slightly reduces the energy consumption when screen is completely
> >
On 11/14/2014 01:58 AM, Tony Lindgren wrote:
* Paul Walmsley [141113 15:01]:
Hi
On Thu, 13 Nov 2014, Tony Lindgren wrote:
* Tomi Valkeinen [141113 03:33]:
On 12/11/14 17:02, Tony Lindgren wrote:
And, with a quick grep, I see CONTROL_DEVCONF1 touched in multiple
places in the kernel. I
On Thu, Nov 13, 2014 at 11:55:38PM +0100, Barto wrote:
> it's interesting, with this commit
> 74665016086615bbaa3fa6f83af410a0a4e029ee I have the bug :
>
> scsi: convert host_busy to atomic_t :
At this point we'll need a bisction between v3.16 as the last good
point, and
On 13 November 2014 23:28, Kevin Hilman wrote:
> From: Kevin Hilman
>
> The IA64_HP_SIM dependency on PM_RUNTIME should be done in the arch
> Kconfig instead of in the PM core. Move it accordingly.
>
> NOTE: arch/ia64/Kconfig currently does a 'select PM', which since
> commit 1eb208aea317 (PM:
Hi Kevin,
On Thu, Nov 13, 2014 at 11:28 PM, Kevin Hilman wrote:
> It makes little sense to use generic power domains without runtime PM.
Does it?
It still powers down the PM domains on system suspend (at least on my
boards ;-)
> Also, since the complexities of handling the !PM_RUNTIME case are
On 14 November 2014 08:26, Ulf Hansson wrote:
> On 13 November 2014 23:28, Kevin Hilman wrote:
>> From: Kevin Hilman
>>
>> It makes little sense to use generic power domains without runtime PM.
>> Also, since the complexities of handling the !PM_RUNTIME case are
>> causing more trouble and
Fix for a really embarrassing braino in iov_iter. Kudos to paulus...
Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Paul Mackerras (1):
Fix thinko in iov_iter_single_seg_count
Diffstat:
mm/iov_iter.c |4 ++--
On 13 November 2014 23:28, Kevin Hilman wrote:
> From: Kevin Hilman
>
> It makes little sense to use generic power domains without runtime PM.
> Also, since the complexities of handling the !PM_RUNTIME case are
> causing more trouble and confusion than they're worth, let's simplify
> the world
Hi,
Who should merge this serie ? as Mark merged the previous one it would
probably make sense to do the same here (at least, in my opinion)
Thanks for your feedbacks.
Have a nice day,
Romain
2014-11-13 21:55 GMT+01:00 Grant Likely :
igned-off-by: Romain Perier
>
> Acked-by: Grant Likely
>
>
From: "jeffrey.lin"
this patch is porting Raydium I2C touch driver. Developer can enable
Raydium touch driver by modifying define "CONFIG_TOUCHSCREEN_RM31100"
in config/base.config
Change-Id: Idae54cc4bca17f321a1d0895a8b59680bf9af859
Signed-off-by: jeffrey@rad-ic.com
chromeos: config:
* Andy Lutomirski [2014-11-13 23:01:12]:
> On Thu, Nov 13, 2014 at 10:08 PM, Srikar Dronamraju
> wrote:
> > * Andy Lutomirski [2014-11-13 14:31:21]:
> >
> >> x86 call do_notify_resume on paranoid returns if TIF_UPROBE is set
> >> but not on non-paranoid returns. I suspect that this is a
Hi Suman,
On Thu, Nov 13, 2014 at 11:02 PM, Suman Anna wrote:
> OK, lets take an example. I have say 2 device instances, say
> hwlock1: hwlock@0 {
> hwlock-num-locks = <32>
> hwlock-base-id = <0>;
> #hwlock-cells = <1>;
> };
>
From: Michael Neuling
Currently all interrupts generated by cxl are named "cxl". This is not very
informative as we can't distinguish between cards, AFUs, error interrupts, user
contexts and user interrupts numbers. Being able to distinguish them is useful
for setting affinity.
This patch
On 10/30, Tomeu Vizoso wrote:
> Moves clock state to struct clk_core, but takes care to change as little API
> as
> possible.
>
> struct clk_hw still has a pointer to a struct clk, which is the
> implementation's per-user clk instance, for backwards compatibility.
>
> The struct clk that
On 13.11.2014 18:24, Pavel Machek wrote:
On Fri 2014-11-07 09:04:52, Ivaylo Dimitrov wrote:
Sebastian is quiet, can we have the patch? :-).
Sure, why not :)
https://gitorious.org/linux-n900/freemangordons-linux-n900/commits/30e9a5c498a89cea4c29523f69e436bf0af3c631
commits 89ce13b,
At Thu, 13 Nov 2014 22:55:09 -0800,
Joe Perches wrote:
>
> On Fri, 2014-11-14 at 07:37 +0100, Takashi Iwai wrote:
> > At Thu, 13 Nov 2014 16:05:30 -0800,
> > Joe Perches wrote:
> > >
> > > On Thu, 2014-11-13 at 23:53 +, Russell King - ARM Linux wrote:
> > > > On Fri, Oct 31, 2014 at
On Thu, Nov 13, 2014 at 01:47:08PM +0100, Vlastimil Babka wrote:
> On 11/04/2014 01:37 AM, Joonsoo Kim wrote:
> >On Mon, Nov 03, 2014 at 09:12:33AM +0100, Vlastimil Babka wrote:
> >>On 10/27/2014 08:41 AM, Joonsoo Kim wrote:
> >>>On Tue, Oct 07, 2014 at 05:33:39PM +0200, Vlastimil Babka wrote:
>
On Thu, Nov 13, 2014 at 10:08 PM, Srikar Dronamraju
wrote:
> * Andy Lutomirski [2014-11-13 14:31:21]:
>
>> x86 call do_notify_resume on paranoid returns if TIF_UPROBE is set
>> but not on non-paranoid returns. I suspect that this is a mistake
>> and that the code only works because int3 is
Hi James,
Today's linux-next merge of the scsi tree got a conflict in
drivers/usb/storage/uas.c between commit e28e2f2f7c42 ("uas: Make uas
work with blk-mq") from the usb tree and commits 125c99bc8b6b ("scsi:
add new scsi-command flag for tagged commands"), abd0c533e377
("scsi: remove
The core always tries to translate any "reg" property to construct the platform
device names. This results in a pile of "OF: no ranges; cannot translate" errors
in dmesg whenever we expose things like i2c devices that cannot directly
translate
to the MMIO space.
Turn this into a pr_debug instead
A fork starts with a single branch.
As a precaution, I (for one (of many)) have all the debian source packages
allready,
and the full binary set for some architectures.
(I'm sure many others have taken this precaution aswell, some
as a matter of course)
This is how all forks start.
I've done it
(Erich Schubert put forth false claims about lack of involvement of mine in
free/opensource software)
(When corrected he first engaged, then deleted all the posts, keeping only his
false statements visible)
"We are unable to post your comment because you have been blocked by Vitavonni.
Find out
We have a historical hack that treats missing ranges properties as the
equivalent of an empty one. This is needed for ancient PowerMac "bad"
device-trees, and shouldn't be enabled for any other PowerPC platform,
otherwise we get some nasty layout of devices in sysfs or even
duplication when a set
On Fri, 2014-11-14 at 07:37 +0100, Takashi Iwai wrote:
> At Thu, 13 Nov 2014 16:05:30 -0800,
> Joe Perches wrote:
> >
> > On Thu, 2014-11-13 at 23:53 +, Russell King - ARM Linux wrote:
> > > On Fri, Oct 31, 2014 at 01:42:44PM +0800, Wang, Yalin wrote:
> > > > This patch add bitrev.h file to
Dear Mr Schubert;
"He has not contributed anything to the open source community."
This is a complete lie. I've contributed gigabytes of media alone.
I've done years and years of programming work.
I have done far more than you ever will.
"His songs and "games" are not worth looking at,"
Your
Discussion on lennart poettering, systemd, sysv
http://youtu.be/2toVPMHRo8M
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Free software worked great for a time, it was a movement
on the upswing. Then it was noticed. Feminists appeared
and lobbied to have those of unclean mind excluded from
the free/opensource movement, only those who believed
the correct thing were allowed to stay. Code nor contribution
mattered
From: Ian Munsie
If an AFU has a hardware bug that causes it to acknowledge a context
terminate or remove while that context has outstanding transactions, it
is possible for the kernel to receive an interrupt for that context
after we have removed it from the context list.
The kernel will not
At Thu, 13 Nov 2014 16:05:30 -0800,
Joe Perches wrote:
>
> On Thu, 2014-11-13 at 23:53 +, Russell King - ARM Linux wrote:
> > On Fri, Oct 31, 2014 at 01:42:44PM +0800, Wang, Yalin wrote:
> > > This patch add bitrev.h file to support rbit instruction,
> > > so that we can do bitrev operation
On Tue, 2014-11-11 at 11:06 +, Luis Henriques wrote:
> 3.16.7-ckt1 -stable review patch. If anyone has any objections, please let
> me know.
>
> --
>
> From: "Eric W. Biederman"
>
> commit 65b38851a17472d31fec9019fc3a55b0802dab88 upstream.
>
> The usage of
Ingo,
could you take the patches, please?
Juergen
On 11/03/2014 02:01 PM, Juergen Gross wrote:
The x86 architecture offers via the PAT (Page Attribute Table) a way to
specify different caching modes in page table entries. The PAT MSR contains
8 entries each specifying one of 6 possible cache
Hi Takao Indoh,
Your update for the patchset works fine. Thanks.
Joerg,
I am working following your directions:
1. If the VT-d driver finds the IOMMU enabled, it reuses its root entry
table, and do NOT disable-enable iommu. Other data will be copied.
2. When a device driver issues the first
On 31 October 2014 12:33, Peter De Schrijver wrote:
> On Thu, Oct 30, 2014 at 11:48:26AM +0100, Tomeu Vizoso wrote:
>> Hello,
>>
>> this fifth version of the series has just one change, suggested by Stephen:
Hi Mike, how is this looking for 3.19?
Regards,
Tomeu
>> * Initialize
On Thu, Nov 13, 2014 at 10:38:01PM -0500, Steven Rostedt wrote:
> On Wed, 5 Nov 2014 16:18:46 +0900
> byungchul.p...@lge.com wrote:
>
> > -static unsigned long preempt_mark_thresh_us = 100;
> > +DEFINE_MARK_STRUCT = {
> > + DEFINE_MARK(0ULL, ' '), /* 0 usecs */
> > +
On Fri, 2014-11-14 at 11:03 +0530, Vineeth Vijayan wrote:
> ping !
>
> any update on this ? As i understand, only powerpc and s390 uses the
> randomize_et_dyn call; for all other architecture this is an obsolete
> function call.
I asked:
> >> I'm not clear on what has changed to break this?
Hello,
On Thu, Nov 13, 2014 at 10:32:06PM -0500, Steven Rostedt wrote:
> On Wed, 5 Nov 2014 16:18:45 +0900
> byungchul.p...@lge.com wrote:
>
> > +/* trace overhead mark */
> > +struct trace_mark {
> > + unsigned long long val; /* unit: nsec */
> > + char sym;
> > +};
>
> Please format
Thanks for the sharing. Will do more tests. :)
On 11/14/2014 07:39 AM, Wanpeng Li wrote:
Hi Tang,
On Tue, Nov 11, 2014 at 01:35:29PM +0800, Tang Chen wrote:
Hi Wanpeng,
Sorry for the late.
I think I have totally missed this thread.
I opened lockdep and RCU debug, and tried on 3.18-rc1.
On Fri, 2014-11-14 at 07:06 +0100, Julia Lawall wrote:
> On Thu, 13 Nov 2014, Joe Perches wrote:
>
> > I added a checkpatch entry for this.
> > Maybe some cocci test like this would be useful?
> >
> > @@
> > type t;
> > t *p;
> > @@
> > - p == NULL
> > + !p
> >
> > @@
> > type t;
> > t *p;
+CC: Colin Cross, James Hogan
On Thursday, November 13, 2014 11:30 PM, Nicolas Pitre wrote:
> To: Russell King - ARM Linux
> Cc: Pankaj Dubey; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH] ARM: b.L: fix unmet dependency for CPU_PM
>
> On Thu, 13 Nov
* Andy Lutomirski [2014-11-13 14:31:21]:
> x86 call do_notify_resume on paranoid returns if TIF_UPROBE is set
> but not on non-paranoid returns. I suspect that this is a mistake
> and that the code only works because int3 is paranoid.
>
> Setting _TIF_NOTIFY_RESUME in the uprobe code was
On Thu, 13 Nov 2014, Joe Perches wrote:
> I added a checkpatch entry for this.
> Maybe some cocci test like this would be useful?
>
> @@
> type t;
> t *p;
> @@
> - p == NULL
> + !p
>
> @@
> type t;
> t *p;
> @@
> - p != NULL
> + p
>
> @@
> type t;
> t *p;
> @@
> - NULL == p
Add read sensors' raw data from trackpad device interface supported in cyapa
driver through debugfs raw_data interface.
Through this interface, user can read difference count map of each sensors
directly from trackpad device (some customers want). And it's useful to help
users to find out the root
Add read raw data function supported for gen5 trackpad device,
it can be used through debugfs raw_data interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen5.c | 138 +++
1 file changed, 138 insertions(+)
diff --git
Add read firmware image function supported for gen3 trackpad device,
it can be used through debugfs read_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 67
1 file changed, 67 insertions(+)
diff
Add read firmware image function supported for gen5 trackpad device,
it can be used through debugfs read_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.h | 1 +
drivers/input/mouse/cyapa_gen5.c | 155 +++
Add read baseline function supported for gen5 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.h | 2 +
drivers/input/mouse/cyapa_gen5.c | 621 +++
2
Add force re-calibrate function supported for gen3 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 58
1 file changed, 58 insertions(+)
diff
Add firmware image update function supported for gen5 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/Kconfig | 2 +-
drivers/input/mouse/cyapa_gen5.c | 290
Add read firmware image from trackpad device interface supported in cyapa
driver through debugfs read_fw interface.
Through this interface user can read out, check and backup the firmware image
of the trackpad device before any firmware update, or can use the backed image
to do firmware image
Add force re-calibrate function supported for gen5 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen5.c | 65
1 file changed, 65 insertions(+)
diff
Add runtime_suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the runtime power
management strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 167
Add suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the power management
strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 105
Add firmware image update function supported for gen3 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 284 +++
1 file changed, 284 insertions(+)
diff
Add device's basic control and features supported in cyapa driver through
sysfs file system interfaces. These interfaces are commonly used in
pre- and after production, for trackpad device state checking, managing
and firmware image updating.
These interfaces including mode, firmware_version and
Add read baseline function supported for gen3 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 71
1 file changed, 71 insertions(+)
diff --git
Remove cyapa_remove() method, add cyapa_open() and cyapa_close() methods for
input interface, also modified together with driver's memory and IRQ resource
allocations to support device resource management infrastructure to reduce
the mistakes of resource management.
TEST=test on Chromebooks.
Based on the cyapa core, add the gen5 trackpad device's basic functions
supported, so gen5 trackpad device can work with kernel input system.
And also based on the state parse interface, the cyapa driver can
automatically determine the attached is gen3 or gen5 protocol trackpad
device, then set
In order to support multiple different chipsets and communication protocols
trackpad devices in one cyapa driver, the new cyapa driver is re-designed
with one cyapa driver core and multiple device specific functions component.
The cyapa driver core is contained in this patch, it supplies basic
This patch modified the code to fix the patch check warning issue with latest
checkpatch.sh tool, and also changed the return variable name from "ret" to
"error" when there is only one error path to follow code style.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 151
V10 patches have below main updates compared with v9 patches:
1) Modify code to following kernel code style.
e.g.: correct to use error as return name when there is only error path,
and fix the checkpatch.sh wanting in the driver.
2) Remove cyapa_remove method and use input open and close
On Fri, 2014-11-14 at 13:13 +0800, Wang, Yalin wrote:
> Use the inline function instead of directly indexing the array.
>
> This allows some architectures with hardware instructions for bit
> reversals to eliminate the array.
>
> Signed-off-by: Joe Perches
> Signed-off-by: Yalin Wang
> ---
[]
From: Brad Griffis
TSC interrupt handler had udelay to avoid reporting of false pen-up
interrupt to user space. This patch implements workaround suggesting in
Advisory 1.0.31 of silicon errata for am335x, thus eliminating udelay
and touchscreen lag. This also improves performance of touchscreen
This series of patches fix TSC defects related to lag in touchscreen
performance and cursor jump at touch release. The lag was result of
udelay in TSC interrupt handler. Cursor jump due to false pen-up event.
The patches implement Advisory 1.0.31 in silicon errata of am335x-evm
to avoid false
The charge delay value is by default 0x400. But it can be set to lower
values on some boards, as long as false pen-ups are avoided. Lowering the
value increases the sampling rate (though current sampling rate is
sufficient for TSC operation). In some boards, the value has to be
increased to avoid
This patch reads charge delay from tsc DT node and writes to
REG_CHARGEDELAY register. If the charge delay is not specified in DT
then default value of 0x400(CHARGEDLY_OPENDLY) is used.
Signed-off-by: Vignesh R
---
drivers/input/touchscreen/ti_am335x_tsc.c | 8 +++-
1 file changed, 7
Previously, delta filtering was applied TSC co-ordinate readouts before
reporting a single value to user space. This patch replaces delta filtering
with median filtering. Median filtering sorts co-ordinate readouts, drops min
and max values, and reports the average of remaining values. This method
In one shot mode, sequencer automatically disables all enabled steps at
the end of each cycle. (both ADC steps and TSC steps) Hence these steps
need not be saved in reg_se_cache for clearing these steps at a later
stage.
Also, when ADC wakes up Sequencer should not be busy executing any of the
From: Brad Griffis
This patch makes the initial changes required to workaround TSC-false
pen-up interrupts. It is required to implement these changes in order to
remove udelay in the TSC interrupt handler and false pen-up events.
The charge step is to be executed immediately after sampling X+.
> From: Joe Perches [mailto:j...@perches.com]
> Sent: Friday, November 14, 2014 1:33 PM
> To: Wang, Yalin
> Cc: 'chunk...@googlemail.com'; 'linvi...@tuxdriver.com'; 'linux-
> wirel...@vger.kernel.org'; 'net...@vger.kernel.org'; 'linux-
> ker...@vger.kernel.org'
> Subject: Re: [PATCH] carl9170:
ping !
any update on this ? As i understand, only powerpc and s390 uses the
randomize_et_dyn call; for all other architecture this is an obsolete
function call.
this call for another patch where randomize_et_dyn is removed.
On Wed, Oct 15, 2014 at 12:08 PM, Vineeth Vijayan wrote:
> On Wed, Oct
On Fri, 2014-11-14 at 13:16 +0800, Wang, Yalin wrote:
> Use the inline function instead of directly indexing the array.
>
> This allows some architectures with hardware instructions for bit
> reversals to eliminate the array.
This one is already in -next
commit
On Thu, 13 Nov 2014 23:57:22 -0500
Steven Rostedt wrote:
> That assignment is what it is initialized to at boot up. I can't see
> any optimization that would cause gcc to modify that. Especially since
> we are hiding its accesses within the ACCESS_ONCE(). That alone should
> confuse gcc enough
* Steven Rostedt [2014-11-13 20:12:51]:
> From: "Steven Rostedt (Red Hat)"
>
> Instead of checking the return value of trace_seq_printf() and friends
> for overflowing of the buffer, use the trace_seq_has_overflowed() helper
> function.
>
> This cleans up the code quite a bit and also takes
* Steven Rostedt [2014-11-13 20:12:54]:
> From: "Steven Rostedt (Red Hat)"
>
> The functions trace_seq_printf() and friends will soon no longer have
> return values. Using trace_seq_has_overflowed() and trace_handle_return()
> should be used instead.
>
> Cc: Masami Hiramatsu
> Cc: Namhyung
When building without CONFIG_PRINTK, we need to provide a stub
check_syslog_permissions. As there is no way to turn on the
dmesg_restrict sysctl without CONFIG_PRINTK, return success.
Reported-by: Jim Davis
Signed-off-by: Sebastian Schmidt
---
include/linux/syslog.h | 8
1 file
* A dtsi for boards based on Mediatek MT6592 SoCs
* Compatible string in arch/arm/mach-mediatek/mediatek.c
Signed-off-by: Howard Chen
---
arch/arm/boot/dts/mt6592.dtsi | 97 +++
arch/arm/mach-mediatek/mediatek.c | 1 +
2 files changed, 98 insertions(+)
Use the inline function instead of directly indexing the array.
This allows some architectures with hardware instructions for bit
reversals to eliminate the array.
Signed-off-by: Joe Perches
Signed-off-by: Yalin Wang
---
drivers/net/wireless/ath/carl9170/phy.c | 4 ++--
1 file changed, 2
The mt6592-evb is an evaluation board based on the MT6592 SoC.
Signed-off-by: Howard Chen
---
arch/arm/boot/dts/Makefile | 3 ++-
arch/arm/boot/dts/mt6592-evb.dts | 25 +
2 files changed, 27 insertions(+), 1 deletion(-)
create mode 100644
This adds a DT binding documentation for the MT6592 SoC from Mediatek.
Signed-off-by: Howard Chen
---
Documentation/devicetree/bindings/arm/mediatek.txt | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
David Miller [mailto:da...@davemloft.net]
> Sent: Friday, November 14, 2014 5:23 AM
[...]
> What if even the first r8152_submit_rx() fails? What ever will cause
> any of these retries to trigger at all?
According to the patch #1 "adjust r8152_submit_rx", the
r8152_submit_rx() would add the rx
Use the inline function instead of directly indexing the array.
This allows some architectures with hardware instructions for bit
reversals to eliminate the array.
Signed-off-by: Joe Perches
Signed-off-by: Yalin Wang
---
sound/usb/6fire/firmware.c | 2 +-
1 file changed, 1 insertion(+), 1
Hi all,
On Thu, Nov 13, 2014 at 11:21:18AM -0800, Kees Cook wrote:
> > This looks to come from your "Honor dmesg_restrict sysctl on dmesg dumps"
> > patch
Oops, you are right.
> > The randconfig doesn't have CONFIG_PRINTK. I guess we need to provide a
> > stub
> > in to cover this.
>
>
> -Original Message-
> From: Joe Stringer [mailto:joestrin...@nicira.com]
> Sent: Friday, November 14, 2014 6:08 AM
> To: netdev
> Cc: sathya.pe...@emulex.com; Shahed Shaikh; am...@mellanox.com; Dept-
> GE Linux NIC Dev; Tom Herbert (Partner - google); gerlitz...@gmail.com;
>
On Fri, Nov 14, 2014 at 12:17 AM, Matthias Brugger
wrote:
> 2014-11-12 17:07 GMT+01:00 Howard Chen :
>> * A dtsi for boards based on Mediatek MT6592 SoCs
>> * Compatible string in arch/arm/mach-mediatek/mediatek.c
>>
>> Signed-off-by: Howard Chen
>> ---
>> arch/arm/boot/dts/mt6592.dtsi | 97
On Thu, 13 Nov 2014 22:48:33 -0600
Alex Elder wrote:
> > diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> > index e748971..4790191 100644
> > --- a/kernel/printk/printk.c
> > +++ b/kernel/printk/printk.c
> > @@ -1624,7 +1624,7 @@ asmlinkage int vprintk_emit(int facility, int level,
On 11/13/2014 08:56 PM, Konrad Rzeszutek Wilk wrote:
+ mfn_save = virt_to_mfn(buf);
+
+ while (xen_remap_mfn != INVALID_P2M_ENTRY) {
So the 'list' is constructed by going forward - that is from low-numbered
PFNs to higher numbered ones. But the 'xen_remap_mfn' is going the
other
> I will figure out how to make dwc2 detect the device connect after auto
> suspend,
> or disable the auto suspend feature for the dwc2 hcd.
I think auto-suspend of the root hub device (which is what calls
bus_suspend, but is not the host controller device itself) is expected
to always happen and
On 11/13/2014 09:21 PM, Pranith Kumar wrote:
> Remove volatile type qualifier and use ACCESS_ONCE() in its place for each
> access. Using volatile is not recommended as documented in
> Documentation/volatile-considered-harmful.txt.
>
> Here logbuf_cpu is a local variable and it is not clear how
Hi Dan,
This patch series addresses a problem seen on the brcmstb ARM platform where
dma_debug_init is called by the ARM kernel at fs_initcall time, while some of
our callers using the DMA-API were running at arch_initcall time.
Unless CONFIG_DMA_API_DEBUG is set, this is completely silent.
dma_debug_init() is called by architecture specific code at different
levels, but typically as a fs_initcall due to the debugfs
initialization. Some platforms may have early callers of the DMA-API,
running prior to the fs_initcall() level, which is not much of an issue
unless CONFIG_DMA_API_DEBUG
Add a helper function which returns whether the DMA debugging API is
disabled, right now we only check for global_disable, but in order to
accomodate early callers of the DMA-API, we will check for more
initialization flags in the future.
Signed-off-by: Florian Fainelli
---
lib/dma-debug.c | 37
Fix documentation typo for shash_alg->descsize.
Add documentation for initially uncovered member variables.
Signed-off-by: Stephan Mueller
---
include/crypto/hash.h | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/include/crypto/hash.h b/include/crypto/hash.h
index
Hi Linus,
Just two patches to remove hp_accel events from the keyboard bus stream via an
i8042 filter.
My inclination was to merge these, but as I had (incorrectly) pushed them to
linux-next already, and you had cautioned against rebasing and to just fix
issues in follow-on patches, I kept the
> On 11/12/14, 9:02 PM, gsant...@codeaurora.org wrote:
>> Hi All,
>>
>> The Question is for the compressed offload session.
>>
>> For a generic codec driver during the startup function it will set some
>> of
>> the hw_constraints rule similarly like this.
>>
>>
On Tuesday 04 November 2014 04:45 PM, Vignesh R wrote:
> This series of patches enable ADC on am437x-gp-evm and am43x-epos-evm.
> The ADC clock hwmod data of am33xx has been moved to commom place so that
> both am43xx and am33xx can reuse them.
> tscadc DT node has been adided to am437x-gp and
On Thu, Nov 13, 2014 at 10:47 PM, Steven Rostedt wrote:
> On Thu, 13 Nov 2014 22:21:21 -0500
> Pranith Kumar wrote:
>
>> Remove volatile type qualifier and use ACCESS_ONCE() in its place for each
>> access. Using volatile is not recommended as documented in
>>
Aaron reported 32bit/PAE mode, has problem with 64bit resource.
[6.610012] pci :03:00.0: reg 0x10: [mem 0x383fffc0-0x383fffdf
64bit pref]
[6.622195] pci :03:00.0: reg 0x20: [mem 0x383fffe04000-0x383fffe07fff
64bit pref]
[6.656112] pci :03:00.1: reg 0x10: [mem
1 - 100 of 1956 matches
Mail list logo
