> So I find the patch, the description and the comments in the code conflicting
> and
> confusing.
>
> The patch does this:
>
> @@ -5676,10 +5676,10 @@ static int migrate_degrades_locality(struct
> task_struct *p, struct lb_env *env)
> unsigned long src_faults, dst_faults;
> in
Along with DT support, this patch also cleans up the unnecessary
code around 'rtc_wakeup' initialization.
Signed-off-by: Chao Xie
Signed-off-by: Vaibhav Hiremath
---
drivers/rtc/rtc-88pm80x.c | 28 +---
1 file changed, 17 insertions(+), 11 deletions(-)
diff --git a/driv
> From: Markus Elfring
> Date: Thu, 5 Feb 2015 17:54:16 +0100
>
> The vfree() function performs also input parameter validation.
> Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
> ---
> drivers/iommu
On Thu, 2 Jul 2015 23:29:56 +0900
Akinobu Mita wrote:
> There are several race conditions while freezing queue.
>
> When unfreezing queue, there is a small window between decrementing
> q->mq_freeze_depth to zero and percpu_ref_reinit() call with
> q->mq_usage_counter. If the other calls blk_m
Ian Munsie writes:
> Acked-by: Ian Munsie
>
> We are probably also missing an idr_destroy(&afu->contexts_idr); in
> cxl_release_afu() as well if you wanted to send a patch for that.
>
> Cheers,
> -Ian
>
Correct, patch is going out today. Thanks for the hint.
--
Johannes Thumshirn
Greg Kroah-Hartman writes:
> On Wed, Jul 08, 2015 at 05:24:46PM +0200, Johannes Thumshirn wrote:
>> Destroy uio_idr on module exit, reclaiming the allocated memory.
>>
>> This was detected by the following semantic patch (written by Luis Rodriguez
>> )
>>
>> @ defines_module_init @
>> declarer
On 07/09/15 08:09, Paolo Bonzini wrote:
>
>
> On 09/07/2015 00:36, Bandan Das wrote:
>> Let userspace inquire the maximum physical address width
>> of the host processors; this can be used to identify maximum
>> memory that can be assigned to the guest.
>>
>> Reported-by: Laszlo Ersek
>> Signed-
On Tue, Jul 07, 2015 at 09:49:36PM +0800, Herbert Xu wrote:
> On Mon, Jul 06, 2015 at 09:10:47PM +0200, LABBE Corentin wrote:
> >
> > +int sun4i_hash_init(struct ahash_request *areq)
> > +{
> > + const char *hash_type;
> > + struct sun4i_req_ctx *op = ahash_request_ctx(areq);
> > + struct cry
From: Denys Vlasenko
Date: Tue, 7 Jul 2015 20:48:55 +0200
> As its first order of business, boomerang_interrupt() checks whether
> the device really has any pending interrupts. If it does not,
> it does nothing and returns, but it still returns IRQ_HANDLED.
>
> This is wrong: interrupt was not
Dear Lorenzo,
On Wed, 8 Jul 2015 18:34:58 +0100
Lorenzo Pieralisi wrote:
> On Wed, Jul 08, 2015 at 01:51:08PM +0100, Jisheng Zhang wrote:
> > This patch implements cpuidle_ops using psci. After this patch, we can
> > use cpuidle-arm.c with psci backend for both arm and arm64.
> >
> > Signed-off
On Thu, 2015-07-09 at 12:47 +0800, Daniel Kurtz wrote:
> On Thu, Jul 9, 2015 at 10:45 AM, YH Huang wrote:
> >
> > On Wed, 2015-07-08 at 20:11 +0800, Daniel Kurtz wrote:
> > > On Mon, Jul 6, 2015 at 9:29 PM, YH Huang wrote:
> > > > Document the device-tree binding of MediatTek display PWM.
> > > >
Hi Lee,
I'm interested in this feature (so as Doug is), could you add us in Cc
of your next submission ?
On Tue, 7 Jul 2015 16:06:44 +0100
Lee Jones wrote:
> This patch-set has been rebased on to topic/pwm.
>
> Continuous mode uses the PWM regulator's maximum and minimum supplied
> voltages
* Rik van Riel wrote:
> On 07/08/2015 09:56 AM, Ingo Molnar wrote:
> >
> > * Srikar Dronamraju wrote:
> >
> >> In commit:8a9e62a "sched/numa: Prefer NUMA hotness over cache hotness"
> >> sched feature NUMA was always set to true. However this sched feature was
> >> suppose to be enabled on NU
On Thu, Jul 09, 2015 at 11:39:11AM +0530, Ronit Halder wrote:
> Fixed a coding style issue.
>
> Signed-off-by: Ronit Halder
Greg has commented in your v1 that it is a false positive. See that:
#define DEFINE_DMA_BUF_EXPORT_INFO(a) \
struct dma_buf_export_info a = { .exp_name = KBUILD_MO
The driver used incorrect flags to clear interrupt status.
The patch fixes it.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_mixer.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_mixer.c
b/drivers/gpu/drm/exynos/exynos
Driver uses only VSYNC interrupts, so we need to cache VSYNC bit state only.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_mixer.c | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_mixer.c
b/drivers/gpu/drm/e
The driver uses bool protected by mutex to track power state.
The patch replaces this combo with single bit and atomic bitops.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_mixer.c | 52 ++-
1 file changed, 14 insertions(+), 38 deletions(-)
diff
INT_EN cache field was updated only by mixer_enable_vblank.
The patch adds update also by mixer_disable_vblank function.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_mixer.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/exynos/exynos_mixer.c
b/driver
edid returned by drm_get_edid should be freed.
The patch fixes it.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c
b/drivers/gpu/drm/exynos/exynos_hdmi.c
index 99
Specification advises to clear vsync indicator before configuring vsync.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_mixer.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_mixer.c
b/drivers/gpu/drm/exynos/exynos_mixer.
Andrzej Hajda (6):
drm/exynos/hdmi: fix edid memory leak
drm/exynos/mixer: fix interrupt clearing
drm/exynos/mixer: correct vsync configuration sequence
drm/exynos/mixer: always update INT_EN cache
drm/exynos/mixer: simplify poweron flag
drm/exynos/mixer: replace MXR_INT_EN register c
Commit ed71871bed719 ("tty/8250_early: Turn serial_in/serial_out into
weak symbols") made these routines weak to allow platform specific
Big endian override
However recent updates to core, specifically ebc5e20082 ("serial:
of_serial: Support big-endian register accesses") and 6e63be3fee14
("serial
On 2015-07-09 08:07, Holger Schurig wrote:
>> Cory Tusar (1):
>> ARM: dts: vfxxx: Include support for esdhc0 functionality.
>>
>> arch/arm/boot/dts/vfxxx.dtsi | 11 +++
>> 1 file changed, 11 insertions(+)
>>
>> --
>> 2.3.6
>
> Your patch looks empty.
This is a cover letter which provid
Hi,
I tested the patch on a setup with 7 devices, all running the same troublesome
use-case in parallel (same use-case as we used to produce the crash dumps).
This use-case was previously able to reproduce the problem about 21 times
during 24 hours. After including the patch the setup ran perfe
On 09/07/2015 00:36, Bandan Das wrote:
> Let userspace inquire the maximum physical address width
> of the host processors; this can be used to identify maximum
> memory that can be assigned to the guest.
>
> Reported-by: Laszlo Ersek
> Signed-off-by: Bandan Das
> ---
> arch/x86/kvm/x86.c
Fixed a coding style issue.
Signed-off-by: Ronit Halder
---
drivers/staging/android/ion/ion.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/android/ion/ion.c
b/drivers/staging/android/ion/ion.c
index 6f48112..e44f5e6 100644
--- a/drivers/staging/android/ion/ion.c
+++ b/dri
From: Markus Elfring
Date: Thu, 9 Jul 2015 08:00:10 +0200
The input_free_device() function tests whether its argument is NULL and
then returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
> Cory Tusar (1):
> ARM: dts: vfxxx: Include support for esdhc0 functionality.
>
> arch/arm/boot/dts/vfxxx.dtsi | 11 +++
> 1 file changed, 11 insertions(+)
>
> --
> 2.3.6
Your patch looks empty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
This one is on top of the last one ? or replace the last one?
On Wed, Jul 08, 2015 at 10:01:47PM -0700, Yinghai Lu wrote:
>On Wed, Jul 8, 2015 at 8:30 PM, Wei Yang wrote:
>> Hi, Yinghai
>>
>> This patch may introduce some problem.
>>
>> On my P8 machine, after applying this patch, I see following
On 07/09/2015 10:11 AM, Daniel Axtens wrote:
>> I recommend creating an alias or script that does:
>>
>> $ git log --pretty=fixes -n 1 $commit | xclip
>>
>
> FWIW, having finally got around to doing this, I found I first needed
> the following snippet in ~/.gitconfig from
> https://www.kernel.or
From: Rohit Thapliyal
On 64bit kernel, the dump_mem gives 32 bit addresses
on the stack dump. This gives unorganized information regarding
the 64bit values on the stack. Hence, modified to get a complete 64bit memory
dump.
With patch:
[ 93.534801] Process insmod (pid: 1587, stack limit = 0xfff
On Thu, Jul 09, 2015 at 08:20:57AM +0530, rcodin wrote:
> From: Ronit Halder
>
> Fixed a coding style issue.
>
> Signed-off-by: Ronit Halder
> ---
> drivers/staging/android/ion/ion.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/android/ion/ion.c
> b/drivers/stagin
* Ingo Molnar wrote:
> > Without something like that, we'll be in the awkward position of having
> > some
> > of the selectors (DS, ES, FS, and GS) in both the normal pt_regs slot and
> > in
> > the extended hardware frame during execution of normal vm86-unaware kernel
> > code. If, on the
On Thu, 2015-07-09 at 11:05 +0530, Sudip Mukherjee wrote:
> On Thu, Jul 09, 2015 at 08:20:57AM +0530, rcodin wrote:
> > From: Ronit Halder
>
> You do not need a From: here. Please fix your gitconfig file and
> git send-email will give your name correctly in the email header.
>
> regards
> sudip
* Andy Lutomirski wrote:
> >> I look forward to it.
> >>
> >> However: I imagine that, if you do this, you may need to be quite careful
> >> about an x86_32-ism. Currently, if you have a pt_regs pointer for the
> >> current entry and user_mode(regs) returns true, then regs ==
> >> current_pt
> > + chosen {
> > + bootargs = "console=ttyS0,921600n8 earlyprintk";
>
> PLease get rid of bootargs here; earlyprintk doesn't do anything on
> arm64 (it's earlycon these days), and you can specify the serial
> configuration in stdout-path, so please use that instead.
>
Got it. Will r
On Thursday 09 July 2015 02:06 AM, Stephen Warren wrote:
On 06/30/2015 04:54 AM, Laxman Dewangan wrote:
Signed-off-by: Laxman Dewangan
Signed-off-by: Chaitanya Bandi
I'm not sure why Chaitanya's S-o-b is there and listed last if he's
not the patch author. If he wrote the patch, he should
On Thu, Jul 09, 2015 at 08:20:57AM +0530, rcodin wrote:
> From: Ronit Halder
You do not need a From: here. Please fix your gitconfig file and
git send-email will give your name correctly in the email header.
regards
sudip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Hi Peter and Prarit,
On 2015/07/08 23:00, Prarit Bhargava wrote:
>
>
> On 07/08/2015 09:51 AM, Peter Hurley wrote:
>> Hi Prarit,
>>
>> On 07/08/2015 08:53 AM, Prarit Bhargava wrote:
>>>
>>>
>>> On 07/08/2015 07:55 AM, Peter Hurley wrote:
Hi Taichi,
On 06/05/2015 06:03 AM, Taichi Kag
Fixed a coding style issue.
Signed-off-by: Ronit Halder
---
drivers/staging/android/ion/ion.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/android/ion/ion.c
b/drivers/staging/android/ion/ion.c
index 6f48112..e44f5e6 100644
--- a/drivers/staging/android/ion/ion.c
+++ b/dri
Hi Paul,
2015-07-09 5:39 GMT+09:00 Paul Bolle :
> Hi Masahiro,
>
> On wo, 2015-07-08 at 14:01 +0900, Masahiro Yamada wrote:
>> Actually, most of pinctrl drivers are boolean, but most of them
>> conventionally have MODULE_AUTHOR, THIS_MODULE, etc.
>>
>> I do not think it looks so weird. Thought?
>
On 09-07-15, 09:55, Pi-Cheng Chen wrote:
> That's what I did in previous version. But the reason I use the device-
> driver model is to handle the defer probing issue. Since there's no
> arch/arm64/mach-mediatek/ directory to hold the device registration
> code anymore, no device tree way to match
dma_alloc_from_coherent uses get_order(size) which makes carve-out
allocations not aligned on order boundaries to fail even though
they are page aligned. So wanted to know why is it required to have
the size aligned on order boundary. Changing it to get_order(PAGE_SIZE)
makes the non aligned carve-
On 09-07-15, 02:40, Rafael J. Wysocki wrote:
> The above sentence is completely unclear to anyone unfamiliar with the
> code in question.
>
> The fix is to access the policy data structure for the given CPU directly
> (which also returns a valid policy for offline CPUs), but the policy
> itself ha
On Wed, Jul 8, 2015 at 9:44 PM, Dmitry Torokhov
wrote:
> On Wed, Jul 08, 2015 at 06:00:41PM -0700, Dan Williams wrote:
>> On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
>> wrote:
>> > On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
>> >> On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torok
On 09-07-15, 02:33, Rafael J. Wysocki wrote:
> > We also missed marking policy->governor as NULL while restoring the
> > policy. Because of that, we call __cpufreq_governor(CPUFREQ_GOV_LIMITS)
>
> How exactly does that happen?
Should have mentioned that in detail, sorry for being lazy. Hopefully
Replace a malloc+strcpy by an equivalent strdup in order to improve
readability.
Signed-off-by: Christophe JAILLET
---
arch/um/os-Linux/umid.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/um/os-Linux/umid.c b/arch/um/os-Linux/umid.c
index b514ead..cc9ac2e 100644
Turn some spaces into a tab to be consistent with the rest of the code.
Signed-off-by: Christophe JAILLET
---
arch/um/os-Linux/umid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/um/os-Linux/umid.c b/arch/um/os-Linux/umid.c
index c1dc892..b514ead 100644
--- a/arch/um/
On 07/08/2015 09:40 PM, Josh Cartwright wrote:
> On Mon, Jun 08, 2015 at 11:38:35PM +0530, Punnaiah Choudary Kalluri wrote:
>> The following patches add arm pl353 static memory controller driver for
>> xilinx zynq soc. The arm pl353 smc supports two interfaces i.e nand and
>> nor/sram memory interf
Le 07/07/15 22:19, Vaishali Thakkar a écrit :
> Use eth_hw_addr_random() instead of calling random_ether_addr().
> Here, this change is setting addr_assign_type to NET_ADDR_RANDOM.
>
> The Coccinelle semantic patch that performs this transformation
> is as follows:
>
> @@
> identifier a,b;
> @@
>
On Wed, Jul 8, 2015 at 8:30 PM, Wei Yang wrote:
> Hi, Yinghai
>
> This patch may introduce some problem.
>
> On my P8 machine, after applying this patch, I see following error:
>
> [0.589948] pnv_ioda_setup_pe_seg: trigger IO SEG 0
> [0.589992] pnv_ioda_setup_pe_seg: res[io 0x1000-0x3fff]
On Thu, Jul 9, 2015 at 11:17 AM, Linus Torvalds
wrote:
> On Wed, Jul 8, 2015 at 5:58 PM, Ming Lei wrote:
>> On Thu, Jul 9, 2015 at 1:29 AM, Linus Torvalds
>> wrote:
>>> Also, it looks like you need to hold the "fw_lock" to even look at
>>> that pointer, since the buffer can get reallocated etc.
On 09-07-15, 01:41, Rafael J. Wysocki wrote:
> On Wednesday, July 08, 2015 04:07:32 PM Viresh Kumar wrote:
> > CPUFreq drivers today support a ->get(cpu) callback, which returns
> > current rate of a CPU. The problem with ->get() is that it takes a cpu
> > number as parameter and this unnecessarily
On 09-07-15, 00:25, Steven Rostedt wrote:
> On Thu, 9 Jul 2015 09:34:45 +0530
> Viresh Kumar wrote:
>
>
> > I think it might be related to what I chased down yesterday:
> >
> > http://marc.info/?l=linux-kernel&m=143633485824975&w=2
> >
> > @Steven: Can you please give this a try ?
> >
>
> Ye
On Wed, Jul 08, 2015 at 09:19:14AM +0900, Byungchul Park wrote:
> On Tue, Jul 07, 2015 at 01:28:18PM -0700, Cong Wang wrote:
> > On Mon, Jul 6, 2015 at 9:40 PM, wrote:
> > > From: Byungchul Park
> > >
> > > __sched_period() returns a period which a rq can have. the period has to
> > > be
> > >
On Wed, Jul 08, 2015 at 12:34:49AM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.2 release.
> There are 56 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
Use module_pci_driver for drivers whose init and exit functions
only register and unregister, respectively.
A simplified version of the Coccinelle semantic patch that performs
this transformation is as follows:
@a@
identifier f, x;
@@
-static f(...) { return pci_register_driver(&x); }
@b depends
On Thu, Jul 9, 2015 at 10:45 AM, YH Huang wrote:
>
> On Wed, 2015-07-08 at 20:11 +0800, Daniel Kurtz wrote:
> > On Mon, Jul 6, 2015 at 9:29 PM, YH Huang wrote:
> > > Document the device-tree binding of MediatTek display PWM.
> > > The PWM has one channel to control the backlight brightness for di
On Wed, Jul 08, 2015 at 06:00:41PM -0700, Dan Williams wrote:
> On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
> wrote:
> > On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
> >> On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
> >> wrote:
> >> > On Tue, Jul 07, 2015 at 01:23:15AM +02
> I recommend creating an alias or script that does:
>
> $ git log --pretty=fixes -n 1 $commit | xclip
>
FWIW, having finally got around to doing this, I found I first needed
the following snippet in ~/.gitconfig from
https://www.kernel.org/doc/Documentation/SubmittingPatches
[core]
On Thu, Jul 09, 2015 at 02:50:25AM +0200, Rafael J. Wysocki wrote:
> Hi Paul,
>
> Something seems to have changed in RCU in 4.2-rc1, as it is now complaining
> about a tracepoint in tick_freeze() like this:
>
> [ 66.340508] ===
> [ 66.340509] [ INFO: suspicious RCU
On Thu, 9 Jul 2015 09:34:45 +0530
Viresh Kumar wrote:
> I think it might be related to what I chased down yesterday:
>
> http://marc.info/?l=linux-kernel&m=143633485824975&w=2
>
> @Steven: Can you please give this a try ?
>
Yes that seems to fix my issue as well.
Tested-by: Steven Rostedt
On Wed, Jul 08, 2015 at 12:34:35AM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.0.8 release.
> There are 55 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
> Sysrq+f is used to kill a process either for debug or when the VM is
> otherwise unresponsive.
>
> It is not intended to trigger a panic when no process may be killed.
>
> Avoid panicking the system for sysrq+f when no processes are killed.
>
> Suggested-by: Michal Hocko
> Signed-off-by: Davi
Hi all,
Changes since 20150708:
The drm-intel tree gained conflicts against Linus' and the drm-intel-fixes
trees.
The tip tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1275
1128 files changed, 68969 insertions(+), 20637
On Wed, 8 Jul 2015 12:29:43 -0400
Steven Rostedt wrote:
> I tested the following patch. Feel free to author it yourself and just
> add my reported/tested-by tags, or give it to me. Either way, I don't
> care. I just want it fixed so that it doesn't make my own tests fail.
>
OK, you posted your
On 09-07-15, 02:13, Rafael J. Wysocki wrote:
> So the cpufreq driver's ->get() callback returns 0 for the given CPU and
> that's what triggers the WARN_ON(). And it most likely returns 0, because
> its internal data structure for that CPU is not present.
>
> I *guess* that before the above commit
On Wed, Jul 08, 2015 at 04:56:34PM -0700, Stephen Boyd wrote:
> On 06/26/2015 02:50 PM, bj...@kryo.se wrote:
> > += EXAMPLE
> > +The following example shows the SMEM setup for MSM8974, with a main SMEM
> > region
> > +at 0xfa0 and an auxiliary region at 0xfc428000:
> > +
> > + reserved-memor
The schedule for the 2015 Linux Security Summit in Seattle is now
published.
The refereed talks are:
* CC3: An Identity Attested Linux Security Supervisor Architecture
- Greg Wettstein, IDfusion
* SELinux in Android Lollipop and Android M
- Stephen Smalley, NSA
* Linu
On Thu, 09 Jul 2015 02:13:45 +0200
"Rafael J. Wysocki" wrote:
> > Initializing CPU#1
> > [ cut here ]
> > WARNING: CPU: 0 PID: 1609 at
> > /home/rostedt/work/git/linux-trace.git/drivers/cpufreq/cpufreq.c:2350
> > cpufreq_update_policy+0xc8/0x139()
>
> So the cpufreq dr
This adds afe (audio front end) device node to the MT8173 dtsi file.
Signed-off-by: Koro Chen
---
This patch is based on Matthias's tree:
https://github.com/mbgg/linux-mediatek
branch: v4.2-next/arm64
Changes since v1:
- change node name to afe: audio-controller@1122
---
arch/arm64/boot/dts
Hi, Yinghai
This patch may introduce some problem.
On my P8 machine, after applying this patch, I see following error:
[0.589948] pnv_ioda_setup_pe_seg: trigger IO SEG 0
[0.589992] pnv_ioda_setup_pe_seg: res[io 0x1000-0x3fff] 100
The last 0x100 is the res->flags, which indicates the UN
QUP from version 2.1.1 onwards, supports a new format of
i2c command tags. Tag codes instructs the controller to
perform a operation like read/write. This new tagging version
supports bam dma and transfers of more than 256 bytes without 'stop'
in between. Adding the support for the same.
For each
QUP cores can be attached to a BAM module, which acts as a dma engine for the
QUP core. When DMA with BAM is enabled, the BAM consumer pipe transmitted data
is written to the output FIFO and the BAM producer pipe received data is read
from the input FIFO.
With BAM capabilities, qup-i2c core can tr
Hi,
On Tue, Jul 07, 2015 at 03:25:53PM +0300, Anda-Maria Nicolae wrote:
> Charging events this patch refers to are:
> - charger is connected to/disconnected from the power source
> - battery is reconnected to the charger, after it was absent.
>
> When the charger is connected to/disconnected from
Signed-off-by: Sricharan R
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
b/arch/arm/boot/dts/qcom-msm8974.dtsi
index f138202..17dcda3 100644
--- a/arch/arm/boot/dts/qcom-msm8974.dtsi
+++ b/arch/arm/boot/dts/qcom-
The definition of i2c_msg says that
"If this is the last message in a group, it is followed by a STOP.
Otherwise it is followed by the next @i2c_msg transaction segment,
beginning with a (repeated) START"
So the expectation is that there is no 'STOP' bit inbetween individual
i2c_msg segments with
qup_wait_writeready waits only on a output fifo empty event.
Change the same function to accept the event and data length
to wait as parameters. This way the same function can be used for
timeouts in otherplaces as well.
Signed-off-by: Sricharan R
---
drivers/i2c/busses/i2c-qup.c | 67 ++
Signed-off-by: Sricharan R
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
b/arch/arm/boot/dts/qcom-msm8974.dtsi
index 37b47b5..f138202 100644
--- a/arch/arm/boot/dts/qcom-msm8974.dtsi
++
The qup_i2c_write/read_one functions can be split to have
the common initialization code and function to loop around
the data bytes separately. This way the initialization code
can be reused while adding v2 tags functionality.
Signed-off-by: Sricharan R
---
drivers/i2c/busses/i2c-qup.c | 147 +++
QUP from version 2.1.1 onwards, supports a new format of i2c command tags.
Tag codes instructs the controller to perform a operation like read/write.
This new tagging version supports and is required for adding bam dma
capabilities. V2 tags supports transfer of more than 256 bytes in a single
i2c t
On 07/08/2015 08:40 PM, Jean Tourrilhes wrote:
> Hi,
>
> The kthread park/unpark facility is not used in the kernel
kernel/smpboot.c ?
> , so one would assume that it's made for kernel modules. This patch should
> definitely help most modules.
> Patch untested, at your own ris
On Wed, Jul 8, 2015 at 5:58 PM, Ming Lei wrote:
> On Thu, Jul 9, 2015 at 1:29 AM, Linus Torvalds
> wrote:
>> Also, it looks like you need to hold the "fw_lock" to even look at
>> that pointer, since the buffer can get reallocated etc.
>
> Yes, the above code with holding 'fw_lock' is right fix fo
This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
Features:
1. F81534 is 1-to-4 & F81532 is 1-to-2 serial ports IC
2. Support Baudrate from B50 to B150 (excluding B100).
3. The RTS signal can be transformed their behavior with
configuration by default ioctl TIOCGRS485/TIOC
commit c627f2ceb692 ("serial: 8250: Add support for big-endian MMIO accesses")
added support for 32-bit big-endian mmio to the 8250 driver. Support for
ioreadXXbe/iowriteXXbe io accessors was missing from m32r arch, which caused
build errors.
Add trivial macro mmio accessors.
Reported-by: Fenggua
This replaces the platform_name in snd_soc_dai_link by device tree node.
Signed-off-by: Koro Chen
---
.../devicetree/bindings/sound/mt8173-max98090.txt | 2 ++
.../bindings/sound/mt8173-rt5650-rt5676.txt | 2 ++
sound/soc/mediatek/mt8173-max98090.c | 17 +
From: Ronit Halder
Fixed a coding style issue.
Signed-off-by: Ronit Halder
---
drivers/staging/android/ion/ion.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/android/ion/ion.c
b/drivers/staging/android/ion/ion.c
index 6f48112..e44f5e6 100644
--- a/drivers/staging/androi
On Wed, 2015-07-08 at 17:45 +0200, Andres Freund wrote:
> Workload:
>
> postgresql (multi-process via shared memory SQL server) and benchmark
> client (pgbench, multi threaded) running on the same server. Connected
> using unix sockets. The statements are relatively simple (~1.5ms on
> average),
On Wed, 2015-07-08 at 20:11 +0800, Daniel Kurtz wrote:
> On Mon, Jul 6, 2015 at 9:29 PM, YH Huang wrote:
> > Document the device-tree binding of MediatTek display PWM.
> > The PWM has one channel to control the backlight brightness for display.
> > It supports MT8173 and MT6595.
> >
> > Signed-off
On 07/08/2015 07:19 PM, Paolo Bonzini wrote:
On 08/07/2015 07:59, Xiao Guangrong wrote:
On 07/07/2015 09:45 PM, Paolo Bonzini wrote:
Right now, NPT page attributes are not used, and the final page
attribute depends solely on gPAT (which however is not synced
correctly), the guest MTRRs an
On Thu, 9 Jul 2015 03:36:02 +0200 "H. Mijail" wrote:
>
> > On 09 Jul 2015, at 02:03, Andrew Morton wrote:
> >
> > On Thu, 9 Jul 2015 01:44:18 +0200 Horacio Mijail Ant__n Quiles
> > wrote:
> >
> >> An hexdump with a buf not aligned to the groupsize causes
> >> non-naturally-aligned memory ac
On 06/29/2015 07:59 PM, Patrick Donnelly wrote:
> task_pgrp requires an rcu or tasklist lock to be obtained if the returned pid
> is to be dereferenced, which kill_pgrp does. Obtain an RCU lock for the
> duration of use.
Reviewed-by: Peter Hurley
--
To unsubscribe from this list: send the line "
On Wed, Jul 08, 2015 at 10:06:10PM +0800, juncheng bai wrote:
> Hi, All
>
> As far as I know, the patch b3f03bac8132207a20286d5602eda64500c19724
> solves one case which big directory size.
>
> I am not very familiar with xfs, but I think why can't we use vmalloc
> when kmalloc fails?
Because vma
Acked-by: Ian Munsie
We are probably also missing an idr_destroy(&afu->contexts_idr); in
cxl_release_afu() as well if you wanted to send a patch for that.
Cheers,
-Ian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.or
From: "Luis R. Rodriguez"
PCI BARs tell us whether prefetching is safe, but they don't say
anything about write combining (WC). WC changes ordering rules and
allows writes to be collapsed, so it's not safe in general to use it on
a prefetchable region.
Add pci_iomap_wc() and pci_iomap_wc_range()
Hi Viresh,
On Wed, Jul 8, 2015 at 7:34 PM, Viresh Kumar wrote:
> On 01-07-15, 10:16, Pi-Cheng Chen wrote:
>> This patch implements MT8173 cpufreq driver.
>
> Now that you are going to resend this patchset, a few more comments.
>
> Please describe your SoC a bit here, so that reviewers know what a
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86-specific MTRR code to the
architecture-agnostic arch_phys_wc_add(). It will avoid MTRRs if
write-combining is available. In order to take advantage of that
also ensure th
On Wed, Jul 08, 2015 at 10:32:54AM -0400, Bill Pringlemeir wrote:
>
> On 8 Jul 2015, shawn...@kernel.org wrote:
> > On Fri, Jun 19, 2015 at 12:58:37AM +0200, Stefan Agner wrote:
> >> Enable the NAND Flash Controller driver which is part of the Vybrid
> >> SoC by default.
> >>
> >> Signed-off-by:
Kbuild should descend into drivers/pinctrl/ only when CONFIG_PINCTRL
is enabled because everything under that directory depends on
CONFIG_PINCTRL.
We can avoid the conditional, ifeq ($(CONFIG_OF),y) ... endif.
Signed-off-by: Masahiro Yamada
---
drivers/Makefile | 2 +-
drivers/pinctrl/
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86-specific MTRR code to the
architecture-agnostic arch_phys_wc_add(). It will avoid MTRRs if
write-combining is available. In order to take advantage of that
also ensure th
1 - 100 of 1227 matches
Mail list logo
