Currently we are iterating over all possible (currently four) bits of
active_bases to see if corresponding clock bases are active. This is good enough
for cases where 3 or 4 bases are used but if only 1 or 2 are used then it makes
more sense to use ffs() to find the right bit directly.
(2014/03/25 4:35), Steven Rostedt wrote:
> On Wed, 05 Mar 2014 20:59:53 +0900
> Masami Hiramatsu wrote:
>
>> There is no need to prohibit probing on the functions
>> used in preparation phase. Those are safely probed because
>> those are not invoked from breakpoint/fault/debug handlers,
>> there
Currently we are iterating over all possible (currently four) bits of
active_bases to see if corresponding clock bases are active. This is good enough
for cases where 3 or 4 bases are used but if only 1 or 2 are used then it makes
more sense to use __ffs() to find the right bit directly.
On 27 March 2014 11:10, Thomas Gleixner wrote:
> What if this is a spurious interrupt and active_bases is 0?
Hmm.. haven't thought about that actually.. I thought it would be
guaranteed here that active_bases isn't zero.
Will fix it as the current code would end up in a infinite loop.
--
To
On Thu, 27 Mar 2014, Viresh Kumar wrote:
> Currently we are iterating over all possible (currently four) bits of
> active_bases to see if corresponding clock bases are active. This is good
> enough
> for cases where 3 or 4 bases are used but if only 1 or 2 are used then it
> makes
> more sense
On Thu, 27 Mar 2014, Viresh Kumar wrote:
> If active_bases already has entry for a particular clock type, then we don't
> need to rewrite it while queuing a hrtimer.
>
> Signed-off-by: Viresh Kumar
> ---
> Initially I thought of doing this but then thought better remove active_bases
>
On Thu, 2014-03-27 at 04:20 +, jimmie.da...@l-3com.com wrote:
> The example code submitted into bugzilla (chase back on the thread a
> bit, there is a reference) shows the problem.
>
> Two threads, TaskA (high priority) and TaskB (low priority). Assigned
> to the same processor,
From: Micky Ching
commit a27fbf2f067b0cd6f172c8b696b9a44c58bfaa7a
produced a cmd.flags unhandled in realtek pci host driver.
This will make MMC card failed initialize, this patch is
used to handle the new cmd.flags condition and MMC card can be used.
Signed-off-by: Micky Ching
---
From: Micky Ching
Using non-DMA dump-regs, which would be more exactly for DMA transfer failed.
More careful handle when cmd/data timeout, add stop(CMD12) cmd before go to
finish request when multi-rw timeout.
Remove some static checher warings.
on commit:
From: Micky Ching
v2:
fix checkpatch warning.
WARNING: Missing a blank line after declarations
v1:
Add new command type(R1 without CRC) handle, without this
patch mmc card initialize will be failed.
Using a more careful handle in request timeout, this would
improve error recover capability.
On Thursday 27 March 2014 09:13 AM, Jingoo Han wrote:
> On Wednesday, March 26, 2014 10:58 PM, Kishon Vijay Abraham I wrote:
>>
>> Added support for pcie controller in dra7xx. This driver re-uses
>> the designware core code that is already present in kernel.
>>
>> Signed-off-by: Kishon Vijay
Since regmap core and mmio have already support for 1/2/8 bytes wide values,
so adds support for 1/2/8 bytes wide registers address.
Signed-off-by: Xiubo Li
---
drivers/base/regmap/regmap-mmio.c | 24 +---
1 file changed, 21 insertions(+), 3 deletions(-)
diff --git
Signed-off-by: Xiubo Li
---
drivers/base/regmap/regmap-mmio.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/drivers/base/regmap/regmap-mmio.c
b/drivers/base/regmap/regmap-mmio.c
index 81f9775..4f1efce 100644
--- a/drivers/base/regmap/regmap-mmio.c
+++
If active_bases already has entry for a particular clock type, then we don't
need to rewrite it while queuing a hrtimer.
Signed-off-by: Viresh Kumar
---
Initially I thought of doing this but then thought better remove active_bases
completely and so didn't sent this one. Now it might find some
Currently we are iterating over all possible (currently four) bits of
active_bases to see if corresponding clock bases are active. This is good enough
for cases where 3 or 4 bases are used but if only 1 or 2 are used then it makes
more sense to use __ffs() to find the right bit directly.
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/wlags49_h2/wl_netdev.c between commit 8d4ade284a41
("wlags49_h2: Call dev_kfree/consume_skb_any instead of dev_kfree_skb")
from the net-next tree and commit fed3ffd8f7ef ("staging: wlags49_h2:
reindent
Add documentation and usage examples for 'hash' triggers.
Signed-off-by: Tom Zanussi
---
Documentation/trace/events.txt | 81 ++
1 file changed, 81 insertions(+)
diff --git a/Documentation/trace/events.txt b/Documentation/trace/events.txt
index
On Thu, 2014-03-27 at 02:37 +0800, Yuyang du wrote:
> Hi all,
>
> This is continued after the first RFC about splitting the scheduler. Still
> work-in-progress, and call for feedback.
>
> The question addressed here is how load balance should be changed. And I think
> the question then goes to
Some triggers may need access to the trace event, so pass it in. Also
fix up the existing trigger funcs and their callers.
Signed-off-by: Tom Zanussi
---
include/linux/ftrace_event.h| 7 ---
kernel/trace/trace.h| 6 --
kernel/trace/trace_events_trigger.c | 35
Hi Steve,
This is my current code for the hash triggers mentioned in the other
thread.
I've been using it for a project here, and as such it works fine for
me, but it's nowhere near anything like a mergeable state; I'm only
sending/posting it because I didn't realize until today that you were
Add a utility function to grab the syscall name from the syscall
metadata, given a syscall id.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.h | 9 +
kernel/trace/trace_syscalls.c | 11 +++
2 files changed, 20 insertions(+)
diff --git a/kernel/trace/trace.h
Make is_string_field() and is_function_field() accessible outside of
trace_event_filters.c for other users of ftrace_event_fields.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.h | 12
kernel/trace/trace_events_filter.c | 12
2 files changed, 12
On 03/26/2014 06:11 PM, Andy Lutomirski wrote:
>
> TBH I'm highly skeptical of this kind of entropy estimation.
> /dev/random is IMO just silly, since you need to have very
> conservative entropy estimates for the concept to really work, and
> that ends up being hideously slow.
In the absence of
On Wed, 26 Mar 2014, ty...@mit.edu wrote:
> But that's another new user of GFP_NOFAIL (and one added three years
> after David tried to declare There Shalt Be No New Users of
> GFP_NOFAIL), and sure, we could probably patch around that by having
> places where there's no other alternaive to keep
> -Original Message-
> From: alsa-devel-boun...@alsa-project.org [mailto:alsa-devel-bounces@alsa-
> project.org] On Behalf Of Mark Brown
> Sent: Wednesday, March 26, 2014 6:09 PM
> To: Lars-Peter Clausen
> Cc: Songhee Baek; Arun Shamanna Lakshmi; alsa-de...@alsa-project.org;
>
On Wed, Mar 26 2014, Vladimir Davydov wrote:
> We don't track any random page allocation, so we shouldn't track kmalloc
> that falls back to the page allocator.
This seems like a change which will leads to confusing (and arguably
improper) kernel behavior. I prefer the behavior prior to this
On 26 March 2014 22:58, Thomas Gleixner wrote:
> Instead of removing it we should actually use ffs and avoid the whole
> looping. That was the intention in the first place, but I never wrote
> the patch...
I thought about that and then using ffs for a field of which only 4 bits
are useful didn't
On 27 March 2014 08:17, Li Zefan wrote:
> This doesn't look like a complete solution, because newer timers/workqueues
> can
> still run in those CPUs.
The initial idea was to disable load balance between CPUs and then do this.
So, that new timers and workqueues from other CPUs would never get
-Original Message-
From: Andy Lutomirski [mailto:l...@amacapital.net]
Sent: Wednesday, March 26, 2014 7:40 PM
To: Davis, Bud @ SSG - Link; umgwanakikb...@gmail.com
Cc: oneu...@suse.de; artem_fetis...@epam.com; pet...@infradead.org;
kosaki.motoh...@jp.fujitsu.com;
> > So let's just ignore the clearance of these bits in isr().
> >
> > +
> > SAI Transmit Control Register (I2S1_TCSR) : 32 : R/W : _h
>
> I'm talking about FWF and FRF bits, not TCSR as a register.
>
> > -
> >
> > I have checked in the Vybrid and LS1 SoC datasheets, and they are
On Thu, Mar 27, 2014 at 12:06:53PM +0800, Xiubo Li-B47053 wrote:
> > > > > > > > + if (xcsr & FSL_SAI_CSR_FWF)
> > > > > > > > + dev_dbg(dev, "isr: Enabled transmit FIFO is
> > > > > > > > empty\n");
> > > > > > > > +
> > > > > > > > + if (xcsr & FSL_SAI_CSR_FRF)
> > > >
> > > > > > > + if (xcsr & FSL_SAI_CSR_FWF)
> > > > > > > + dev_dbg(dev, "isr: Enabled transmit FIFO is empty\n");
> > > > > > > +
> > > > > > > + if (xcsr & FSL_SAI_CSR_FRF)
> > > > > > > + dev_dbg(dev, "isr: Transmit FIFO watermark has been
> > > reached\n");
> > > > > > > +
> >
On Wed, Mar 26, 2014 at 7:33 PM, Lucas Stach wrote:
>> > It does so by doing the necessary manual cache flushes/invalidates on
>> > buffer access, so costs some performance. To avoid this you really want
>> > to get writecombined mappings into the kernel<->userspace interface.
>> > Simply mapping
On Thu, Mar 27, 2014 at 11:41:02AM +0800, Xiubo Li-B47053 wrote:
>
> > Subject: Re: [PATCH] ASoC: fsl_sai: Add isr to deal with error flag
> >
> > On Thu, Mar 27, 2014 at 10:53:50AM +0800, Xiubo Li-B47053 wrote:
> > > > On Thu, Mar 27, 2014 at 10:13:48AM +0800, Xiubo Li-B47053 wrote:
> > > > > >
On Wednesday, March 26, 2014 10:58 PM, Kishon Vijay Abraham I wrote:
>
> Added support for pcie controller in dra7xx. This driver re-uses
> the designware core code that is already present in kernel.
>
> Signed-off-by: Kishon Vijay Abraham I
Hi Kishon,
Long time no see! I added trivial
> Subject: Re: [PATCH] ASoC: fsl_sai: Add isr to deal with error flag
>
> On Thu, Mar 27, 2014 at 10:53:50AM +0800, Xiubo Li-B47053 wrote:
> > > On Thu, Mar 27, 2014 at 10:13:48AM +0800, Xiubo Li-B47053 wrote:
> > > > > + regmap_read(sai->regmap, FSL_SAI_TCSR, );
> > > > > +
Hi,
On Wed, Mar 26, 2014 at 10:27:13PM -0400, Peter Hurley wrote:
> On 03/26/2014 10:10 PM, Felipe Balbi wrote:
> >Hi,
> >
> >On Wed, Mar 26, 2014 at 08:39:11PM -0400, Peter Hurley wrote:
> >>On 03/25/2014 02:28 PM, Tony Lindgren wrote:
> >>>* Felipe Balbi [140320 12:39]:
> This reverts
Hi,
On Wed, Mar 26, 2014 at 10:20:15PM -0400, Peter Hurley wrote:
> >>You may want to build on top of this patch split handling;
> >>I noticed some of the protocol drivers are calling
> >>hci_uart_tx_wakeup() from work functions already (so don't
> >>need to schedule another work...)
> >
> >I
On Wed, 26 Mar 2014 20:05:16 -0700
Andy Lutomirski wrote:
> On Wed, Mar 26, 2014 at 7:48 PM, Jeff Layton
> wrote:
> > On Wed, 26 Mar 2014 17:23:24 -0700
> > Andy Lutomirski wrote:
> >
> >> Hi various people who care about user-space NFS servers and/or
> >> security-relevant APIs.
> >>
> >> I
On Thu, Mar 27, 2014 at 10:53:50AM +0800, Xiubo Li-B47053 wrote:
> > On Thu, Mar 27, 2014 at 10:13:48AM +0800, Xiubo Li-B47053 wrote:
> > > > + regmap_read(sai->regmap, FSL_SAI_TCSR, );
> > > > + regmap_write(sai->regmap, FSL_SAI_TCSR, xcsr);
> > > > +
> > > > + if (xcsr &
On 03/26/2014 04:51 PM, Srivatsa S. Bhat wrote:
> On 03/26/2014 09:26 AM, Preeti U Murthy wrote:
>> Its possible that the tick_broadcast_force_mask contains cpus which are not
>> in cpu_online_mask when a broadcast tick occurs. This could happen under the
>> following circumstance assuming CPU1 is
On Wed, Mar 26, 2014 at 7:48 PM, Jeff Layton wrote:
> On Wed, 26 Mar 2014 17:23:24 -0700
> Andy Lutomirski wrote:
>
>> Hi various people who care about user-space NFS servers and/or
>> security-relevant APIs.
>>
>> I propose the following set of new syscalls:
>>
>> int credfd_create(unsigned int
On Wed, Mar 26, 2014 at 04:46:48PM +0100, Paolo Bonzini wrote:
> Il 26/03/2014 15:57, Fengguang Wu ha scritto:
> >
> >git://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
> >commit 93c4adc7afedf9b0ec190066d45b6d67db5270da ("KVM: x86: handle
> >missing MPX in nested
> On Thu, Mar 27, 2014 at 10:13:48AM +0800, Xiubo Li-B47053 wrote:
> > > + regmap_read(sai->regmap, FSL_SAI_TCSR, );
> > > + regmap_write(sai->regmap, FSL_SAI_TCSR, xcsr);
> > > +
> > > + if (xcsr & FSL_SAI_CSR_WSF)
> > > + dev_dbg(dev, "isr: Start of Tx word detected\n");
> > > +
> > > +
On 2014/3/20 21:49, Viresh Kumar wrote:
> For networking applications platforms need to provide one CPU per each user
> space data plane thread. These CPUs should not be interrupted by kernel at all
> unless userspace has requested for some syscalls. Currently, there are
> background kernel
On Wed, 26 Mar 2014 17:23:24 -0700
Andy Lutomirski wrote:
> Hi various people who care about user-space NFS servers and/or
> security-relevant APIs.
>
> I propose the following set of new syscalls:
>
> int credfd_create(unsigned int flags): returns a new credfd that
> corresponds to current's
On Thu, Mar 27, 2014 at 10:13:48AM +0800, Xiubo Li-B47053 wrote:
> > + regmap_read(sai->regmap, FSL_SAI_TCSR, );
> > + regmap_write(sai->regmap, FSL_SAI_TCSR, xcsr);
> > +
> > + if (xcsr & FSL_SAI_CSR_WSF)
> > + dev_dbg(dev, "isr: Start of Tx word detected\n");
> > +
> > + if
Hi all,
This is continued after the first RFC about splitting the scheduler. Still
work-in-progress, and call for feedback.
The question addressed here is how load balance should be changed. And I think
the question then goes to how to *reuse* common code as much as possible and
meanwhile be
On Thu, Mar 27, 2014 at 01:14:24AM +, Mark Brown wrote:
> On Wed, Mar 26, 2014 at 11:59:53AM +, David Laight wrote:
> > From: Nicolin Chen
>
> > > + regmap_read(sai->regmap, FSL_SAI_TCSR, );
> > > + regmap_write(sai->regmap, FSL_SAI_TCSR, xcsr);
>
> > Assuming these are 'write to clear'
(Just came back from travelling)
On 2014/3/22 7:37, Catalin Marinas wrote:
> Hi Li,
>
> On 17 Mar 2014, at 04:07, Li Zefan wrote:
>> Currently if kmemleak is disabled, the kmemleak objects can never be freed,
>> no matter if it's disabled by a user or due to fatal errors.
>>
>> Those objects
On 03/26/2014 10:10 PM, Felipe Balbi wrote:
Hi,
On Wed, Mar 26, 2014 at 08:39:11PM -0400, Peter Hurley wrote:
On 03/25/2014 02:28 PM, Tony Lindgren wrote:
* Felipe Balbi [140320 12:39]:
This reverts commit 0324a821029e1f54e7a7f8fed48693cfce42dc0e.
That commit tried to fix a deadlock
On Wed, Mar 26, 2014 at 07:35:01PM -0400, Sasha Levin wrote:
> On 03/26/2014 07:18 PM, Daniel Borkmann wrote:
> >On 03/26/2014 06:12 PM, Sasha Levin wrote:
> >>Commit 4af712e8df ("random32: add prandom_reseed_late() and call when
> >>nonblocking pool becomes initialized") has added a late reseed
On 03/26/2014 10:09 PM, Felipe Balbi wrote:
I just noticed this patch wasn't addressed to Marcel;
seems like this should go through the bluetooth tree (but not
through bluetooth-next because it fixes an oops).
read the archives:
http://marc.info/?l=linux-bluetooth=139534449409583=2
Sorry. I
> + regmap_read(sai->regmap, FSL_SAI_TCSR, );
> + regmap_write(sai->regmap, FSL_SAI_TCSR, xcsr);
> +
> + if (xcsr & FSL_SAI_CSR_WSF)
> + dev_dbg(dev, "isr: Start of Tx word detected\n");
> +
> + if (xcsr & FSL_SAI_CSR_SEF)
> + dev_dbg(dev, "isr: Tx Frame
Hi,
On Wed, Mar 26, 2014 at 08:39:11PM -0400, Peter Hurley wrote:
> On 03/25/2014 02:28 PM, Tony Lindgren wrote:
> >* Felipe Balbi [140320 12:39]:
> >>This reverts commit 0324a821029e1f54e7a7f8fed48693cfce42dc0e.
> >>
> >>That commit tried to fix a deadlock problem when using
> >>hci_ldisc, but
Hi Jay,
What's your opinion about the new patch.
Thanks,
Zheng Li
于 2014年03月26日 08:53, Ding Tianhong 写道:
> On 2014/3/25 16:36, zheng.li wrote:
>> 于 2014年03月25日 11:42, Ding Tianhong 写道:
>>> On 2014/3/25 11:00, Zheng Li wrote:
In bond mode tlb and alb, inactive slaves should keep inactive
Hi,
On Wed, Mar 26, 2014 at 08:47:15PM -0400, Peter Hurley wrote:
> [ +to Marcel Holtmann ]
>
> On 03/20/2014 03:30 PM, Felipe Balbi wrote:
> >LDISCs shouldn't call tty->ops->write() from within
> >->write_wakeup().
> >
> >->write_wakeup() is called with port lock taken and
> >IRQs disabled,
Hi List!
Hope some one can help me, we had a big issue in our cloud the other
day, a couple of our openstack regions ( +2000 kvm guests with qcow2 )
went read only filesystem from the guest side because the backing
files directory (the openstack _base directory) was compromised and
the data was
There are a number of things wrong with this post, but I'll respond in detail
when I get to a keyboard.
On March 26, 2014 6:11:53 PM PDT, Andy Lutomirski wrote:
>[cc: Greg Price, might be working on this stuff]
>
>On Wed, Mar 26, 2014 at 6:03 PM, H. Peter Anvin wrote:
>> I'm wondering more
2014-03-27 3:51 GMT+09:00 Aaron Sierra :
> - Original Message -
>> From: "Daeseok Youn"
>> Sent: Tuesday, March 25, 2014 10:01:48 PM
>> Subject: [PATCH] staging: vme: fix memory leak in vme_user_probe()
>>
>>
>> If vme_master_request() returns NULL when it failed,
>> it need to free
Hi,
On Wed, Mar 26 2014, Ulf Hansson wrote:
> On 26 March 2014 17:42, Georgi Djakov wrote:
>> Hello Chris, Ulf,
>>
>> Do you have any comments on the patches?
>> The arch code that will use this driver is already in mainline. The
>> regulators support seem to be still on its way, but this driver
On Tue, Mar 25, 2014 at 05:02:35PM -0700, Arun Shamanna Lakshmi wrote:
> + }
> + if (!match) {
> + dev_err(codec->dev, "ASoC: Failed to find matched enum
> value\n");
> + return -EINVAL;
> + } else
> + ucontrol->value.enumerated.item[0] = i;
On Wed, Mar 26, 2014 at 11:59:53AM +, David Laight wrote:
> From: Nicolin Chen
> > + regmap_read(sai->regmap, FSL_SAI_TCSR, );
> > + regmap_write(sai->regmap, FSL_SAI_TCSR, xcsr);
> Assuming these are 'write to clear' bits, you might want
> to make the write (above) and all the traces
[cc: Greg Price, might be working on this stuff]
On Wed, Mar 26, 2014 at 6:03 PM, H. Peter Anvin wrote:
> I'm wondering more about the default. We default to 50% for
> arch_get_random_seed, and this is supposed to be the default for in effect
> unverified hwrngs...
TBH I'm highly skeptical
On 3/27/2014 4:20 AM, Dmitry Torokhov wrote:
> On Wed, Mar 26, 2014 at 05:04:04PM +, One Thousand Gnomes wrote:
>> On Wed, 26 Mar 2014 13:01:36 +0800
>> "Zhu, Lejun" wrote:
>>
>>> This patch adds support for the GPIO buttons on some Intel Bay Trail
>>> tablets originally running Windows 8.
On Wed, Mar 26, 2014 at 08:38:47PM +0100, Lars-Peter Clausen wrote:
> On 03/26/2014 01:02 AM, Arun Shamanna Lakshmi wrote:
> The way you describe this it seems to me that a value array for this kind of
> mux would look like.
> 0x, 0x, 0x0001
> 0x, 0x,
2014-03-16 11:19 GMT+01:00 Samuel Thibault :
> Pali Rohár, le Sun 16 Mar 2014 11:16:25 +0100, a écrit :
>> Hello, what happened with this patch? Is there any problem with accepting it?
>
> Dmitry finding time to review it, I guess.
>
> Samuel
Dmitry, can you look and review this patch?
--
Pali
On Thursday, March 27, 2014 9:09 AM, Bryan Wu wrote:
> On Tue, Mar 25, 2014 at 10:01 PM, Alexandre Courbot wrote:
> > Ping Thierry, can you have a look at this series? It is quite similar
> > to the same change you merged for panel-simple (although I cannot see
> > it in -next neither).
> >
>
>
I'm wondering more about the default. We default to 50% for
arch_get_random_seed, and this is supposed to be the default for in effect
unverified hwrngs...
On March 26, 2014 5:50:09 PM PDT, Andy Lutomirski wrote:
>On 03/21/2014 07:33 AM, Torsten Duwe wrote:
>> This can be viewed as the
On Friday 21 March 2014, Lee Jones wrote:
> As requested by Arnd:
>
> ARM-SoC Maintainers,
>
> Please apply these two patches directly to ARM-SoC for inclusion
> into the v3.15 merge window. All maintainer Acks are applied.
>
> Kind regards,
Applied to next/dt branch. I had a trivial conflict
On Wed, Mar 26, 2014 at 5:42 PM, Serge Hallyn wrote:
> Quoting Andy Lutomirski (l...@amacapital.net):
>> Hi various people who care about user-space NFS servers and/or
>> security-relevant APIs.
>>
>> I propose the following set of new syscalls:
>>
>> int credfd_create(unsigned int flags):
Add the binding description for the Kona PWM controller found on Broadcom's
mobile SoCs.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
.../devicetree/bindings/pwm/bcm-kona-pwm.txt | 21
1 file changed, 21 insertions(+)
create
This series introduces the driver for the Kona PWM controller found in
Broadcom mobile SoCs like bcm281xx and updates the device tree and the
defconfig to enable use of this hardware on the bcm28155 AP board.
Changes since v4:
- Added in real polarity support
- Labeled trigger bits as such
On 03/21/2014 07:33 AM, Torsten Duwe wrote:
> This can be viewed as the in-kernel equivalent of hwrngd;
> like FUSE it is a good thing to have a mechanism in user land,
> but for some reasons (simplicity, secrecy, integrity, speed)
> it may be better to have it in kernel space.
Nice.
[...]
>
Add support for the six-channel Kona PWM controller found on Broadcom
mobile SoCs like bcm281xx.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
drivers/pwm/Kconfig|9 ++
drivers/pwm/Makefile |1 +
drivers/pwm/pwm-bcm-kona.c | 319
Mark the PWM as enabled on the bcm28155 AP board.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
arch/arm/boot/dts/bcm28155-ap.dts |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/bcm28155-ap.dts
b/arch/arm/boot/dts/bcm28155-ap.dts
Enable PWM drivers and the PWM-based backlight driver.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
arch/arm/configs/bcm_defconfig |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/bcm_defconfig b/arch/arm/configs/bcm_defconfig
index
Add the device tree node for the PWM on bcm11351 SoCs.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
arch/arm/boot/dts/bcm11351.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/bcm11351.dtsi
[ +to Marcel Holtmann ]
On 03/20/2014 03:30 PM, Felipe Balbi wrote:
LDISCs shouldn't call tty->ops->write() from within
->write_wakeup().
->write_wakeup() is called with port lock taken and
IRQs disabled, tty->ops->write() will try to acquire
the same port lock and we will deadlock.
Quoting Andy Lutomirski (l...@amacapital.net):
> Hi various people who care about user-space NFS servers and/or
> security-relevant APIs.
>
> I propose the following set of new syscalls:
>
> int credfd_create(unsigned int flags): returns a new credfd that
> corresponds to current's creds.
>
>
On 03/21/2014 07:50 AM, jimmie.da...@l-3com.com wrote:
>
>
> From: Mike Galbraith [umgwanakikb...@gmail.com]
> Sent: Friday, March 21, 2014 9:41 AM
> To: Davis, Bud @ SSG - Link
> Cc: oneu...@suse.de; artem_fetis...@epam.com; pet...@infradead.org;
>
On 03/25/2014 02:28 PM, Tony Lindgren wrote:
* Felipe Balbi [140320 12:39]:
This reverts commit 0324a821029e1f54e7a7f8fed48693cfce42dc0e.
That commit tried to fix a deadlock problem when using
hci_ldisc, but it turns out the bug was in hci_ldsic
all along where it was calling ->write() from
On Wed, 26 Mar 2014, Mitchel Humpherys wrote:
> printk is meant to be used with an associated log level. There are some
> instances of printk scattered around the mm code where the log level is
> missing. Add a log level and adhere to suggestions by
> scripts/checkpatch.pl by moving to the pr_*
Hi various people who care about user-space NFS servers and/or
security-relevant APIs.
I propose the following set of new syscalls:
int credfd_create(unsigned int flags): returns a new credfd that
corresponds to current's creds.
int credfd_activate(int fd, unsigned int flags): Change current's
Hi,
On Wed, Mar 26, 2014 at 07:04:50PM -0500, Felipe Balbi wrote:
> @@ -1867,6 +1879,37 @@ static inline struct omap_mmc_platform_data
> }
> #endif
>
> +static void omap_hsmmc_set_max_blk_size(struct omap_hsmmc_host *host)
> +{
> + struct mmc_host *mmc = host->mmc;
> +
> + if
Yes. The drive was found fine on other controllers I tried it on.
On Mon, Mar 24, 2014 at 8:27 AM, Bartlomiej Zolnierkiewicz
wrote:
>
> + linux-ide mailing list on Cc:
>
> On Monday, March 24, 2014 02:15:58 PM One Thousand Gnomes wrote:
>> On Sat, 22 Mar 2014 16:32:54 -0700
>> "David F."
On Tue, Mar 25, 2014 at 10:01 PM, Alexandre Courbot wrote:
> Ping Thierry, can you have a look at this series? It is quite similar
> to the same change you merged for panel-simple (although I cannot see
> it in -next neither).
>
I think Jingoo can help to review this as well. Jingoo, can you
we introduce new accessors which provide for register
access with and without offsets.
This is just to make sure newer versions of the IP
can access the new registers prepended at the beginning
of the address space.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/omap_hsmmc.c | 36
by saving reg_offset inside our host structure
we can ioremap the correct area, make use of
resource_size() and make sure newer versions
of the IP have access to the new set of registers
which were added back in OMAP4.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/omap_hsmmc.c | 14
This patch is in preparation for a larger series
of cleanups on the omap_hsmmc.c driver.
In newer instances of this IP, there's a lot of
configuration details which we can grab by reading
some new registers which were prepended to the
address space.
Signed-off-by: Felipe Balbi
---
Hi,
this series lets us access the newer registers introduced
back in OMAP4 which give us some valid information about
the OMAP HSMMC IP like max block size, support for ADMA,
support for Retention.
Right now, only setting max_blk_size correctly as supporting
ADMA and Retention will take a lot
now that we can finally read the new registers for
new versions of the mmc IP, we can set max_blk_size
correctly depending on the version of the IP we're
running on.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/omap_hsmmc.c | 45 ++-
1 file changed,
the newly introduced accessor funtions will help
dealing with register access which shouldn't be
done with offset in consideration.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/omap_hsmmc.c | 200 --
1 file changed, 96 insertions(+), 104 deletions(-)
On Wed, 2014-03-26 at 16:49 -0700, Mitchel Humpherys wrote:
> printk is meant to be used with an associated log level. There are some
> instances of printk scattered around the mm code where the log level is
> missing. Add a log level and adhere to suggestions by
> scripts/checkpatch.pl by moving
David Ahern wrote:
>> Ramkumar Ramachandra (4):
>>perf kmem: introduce --list-cmds for use by scripts
>>perf mem: introduce --list-cmds for use by scripts
>>perf lock: introduce --list-cmds for use by scripts
>>perf sched: introduce --list-cmds for use by scripts
>>
>
> All 4 look
While adding usage information, 44d742e (perf list: Add usage,
2013-10-30) broke
$ perf list --raw-dump
Remove this option, and use parse_options_subcommand() to provide a
'--list-cmds'. The argument to 'perf list' is now treated like a
subcommand. Update the completion script to reflect this
printk is meant to be used with an associated log level. There are some
instances of printk scattered around the mm code where the log level is
missing. Add a log level and adhere to suggestions by
scripts/checkpatch.pl by moving to the pr_* macros.
Signed-off-by: Mitchel Humpherys
---
This series cleans up some printks in the mm code that were missing
log levels.
Mitchel Humpherys (1):
mm: convert some level-less printks to pr_*
mm/bounce.c| 5 +++--
mm/mempolicy.c | 3 ++-
mm/mmap.c | 19 ++-
mm/nommu.c | 3 ++-
mm/slub.c | 7 ---
On 03/27/2014 12:35 AM, Sasha Levin wrote:
On 03/26/2014 07:18 PM, Daniel Borkmann wrote:
On 03/26/2014 06:12 PM, Sasha Levin wrote:
Commit 4af712e8df ("random32: add prandom_reseed_late() and call when
nonblocking pool becomes initialized") has added a late reseed stage
that happens as soon
On 03/26/2014 07:18 PM, Daniel Borkmann wrote:
On 03/26/2014 06:12 PM, Sasha Levin wrote:
Commit 4af712e8df ("random32: add prandom_reseed_late() and call when
nonblocking pool becomes initialized") has added a late reseed stage
that happens as soon as the nonblocking pool is marked as
1 - 100 of 1008 matches
Mail list logo
