From: Dave Hansen
The original motivation for these patches was for an Intel CPU
feature called MPX. The patch to add a disabled feature for it
will go in with the other parts of the support.
But, in the meantime, there are a few other features than MPX
that we can make assumptions about at
From: Dave Hansen
I believe the REQUIRED_MASK aproach was taken so that it was
easier to consult in assembly (arch/x86/kernel/verify_cpu.S).
DISABLED_MASK does not have the same restriction, but I
implemented it the same way for consistency.
We have a REQUIRED_MASK... which does two things:
1.
There were only minor changes here from the last version. I'd
like to get this in before the MPX patch set so that the MPX
patches can use this instead of 'cpu_has_mpx'.
Could this get queued up for 3.18?
Changes from v2:
* also axe PAE macro
* fix typo in comment
* put K6_MTRR in the right
From: Dave Hansen
cpu_has_pae is only referenced in one place: the X86_32 kexec
code (in a file not even built on 64-bit). It hardly warrants
its own macro, or the trouble we go to ensuring that it can't
be called in X86_64 code.
Axe the macro and replace it with a direct cpu feature check.
On Thu, Sep 11, 2014 at 1:53 PM, Dmitry Torokhov
wrote:
> On Thu, Sep 11, 2014 at 01:42:20PM -0700, Luis R. Rodriguez wrote:
>> On Thu, Sep 11, 2014 at 1:23 PM, Dmitry Torokhov
>> wrote:
>> >
>> >> There are elements in common, but by and
>> >> large the biggest headaches at least in large
* Felipe Balbi [140728 14:19]:
> OMAP INTC irqchip driver will be moved under
> drivers/irqchip/ soon but we still have a dependency
> with mach-omap2 when it comes to idle functions.
>
> In order to make it easy to share those function
> prototypes with OMAP PM code, we introduce this new
>
On 09/09/2014 04:47 PM, Antoine Tenart wrote:
> Enable timer 1 to be the source for the sched_clock, allowing to have a
> more precise value than 1/HZ.
>
> Signed-off-by: Antoine Tenart
Applied to berlin/dt.
For the record, I managed to configure UTF-8, so feel free to add the
accent back to
On 09/10/2014 11:15 AM, Antoine Tenart wrote:
> The berlin_pinctrl_dt_free_map function tries to free memory
> allocated and handled by the of subsystem. This is wrong and
> already handled by pinctrl_dt_free_maps() which calls
> of_node_put().
>
> This patch fixes the Berlin pinctrl way of
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Paul Zimmerman
> Sent: Thursday, September 11, 2014 1:10 PM
>
> > From: Paul Zimmerman
> > Sent: Thursday, September 11, 2014 12:11 PM
> >
> > > From: Robert Baldyga [mailto:r.bald...@samsung.com]
> >
From: Heiko Stübner
IO domain voltages on some Rockchip SoCs are variable but need to be
kept in sync between the regulators and the SoC using a special
register.
A specific example using rk3288:
- If the regulator hooked up to a pin like SDMMC0_VDD is 3.3V then
bit 7 of GRF_IO_VSEL needs to
Implement the zs_zpool_shrink() function, which previously just returned
EINVAL, by calling the zs_shrink() function to shrink the zs_pool by one
zspage. The zs_shrink() function is called in a loop until the requested
number of pages have been reclaimed, or an error occurs.
Signed-off-by: Dan
Add an atomic index that allows multiple threads to concurrently and
sequentially iterate through the zspages in all classes and fullness
groups. Add a function find_next_lru_class_fg() to find the next class
fullness group to check for a zspage. Add a function find_lru_zspage()
which calls
Add function obj_handle_is_free() which scans through the entire
singly-linked list of free objects inside the provided zspage to
determine if the provided object handle is free or not. This is
required by zspage reclaiming, which needs to evict each object
that is currently in use by the zs_pool
On 09/09/2014 at 12:14:20 +0200, Boris Brezillon wrote :
> Declare the SCKC (Slow Clock Configuration) block and its clks.
> Make use of the clk32k clk instead of slow_osc where appropriate.
>
> Signed-off-by: Boris BREZILLON
Acked-by: Alexandre Belloni
> ---
>
Move the code that frees a zspage object out of the zs_free()
function and into its own obj_free() function.
This is required by zsmalloc shrinking, which will also need to
free objects during zspage reclaiming.
Signed-off-by: Dan Streetman
Cc: Minchan Kim
---
mm/zsmalloc.c | 24
Add function reclaim_zspage() to evict each object in use in the provided
zspage, so that it can be freed. This is required to be able to shrink
the zs_pool. Check in zs_free() if the handle's zspage is in the reclaim
fullness group, and if so ignore it, since it will be freed during reclaim.
Add struct zs_ops with a evict() callback function. Add documentation
to zs_free() function clarifying that it cannot be called with a
zs_pool handle after that handle has been successfully evicted;
since evict calls into a function provided by the zs_pool creator,
the creator is therefore
Add function zs_shrink() to implement zs_pool shrinking. This allows
the pool owner to reduce the size of the zs_pool by one zspage, which
contains one or more struct pages. Once the zs_pool is shrunk, the
freed pages are available for system use.
This is used by zswap to limit its total system
When zsmalloc creates a new zspage, it initializes each object it contains
with a link to the next object, so that the zspage has a singly-linked list
of its free objects. However, the logic that sets up the links is wrong,
and in the case of objects that are precisely aligned with the page
Update ordering of a changed zspage in its fullness group LRU list,
even if it has not moved to a different fullness group.
This is needed by zsmalloc shrinking, which partially relies on each
class fullness group list to be kept in LRU order, so the oldest can
be reclaimed first. Currently, LRU
Move ZS_FULL into section of fullness_group entries that are tracked in
the class fullness_lists. Without this change, full zspages are untracked
by zsmalloc; they are only moved back onto one of the tracked lists
(ZS_ALMOST_FULL or ZS_ALMOST_EMPTY) when a zsmalloc user frees one or more
of its
Now that zswap can use zsmalloc as a storage pool via zpool, it will
try to shrink its zsmalloc zs_pool once it reaches its max_pool_percent
limit. These patches implement zsmalloc shrinking. The way the pool is
shrunk is by finding a zspage and reclaiming it, by evicting each of its
objects
While zone->name is currently hard coded, the call to kobject_init_and_add()
should follow the more defensive argument list usage (as already done in
other places in ttm_memory.c) where "%s" is used instead of directly passing
in a variable as a format string.
Signed-off-by: Kees Cook
---
On Thu, Sep 11, 2014 at 01:42:20PM -0700, Luis R. Rodriguez wrote:
> On Thu, Sep 11, 2014 at 1:23 PM, Dmitry Torokhov
> wrote:
> >
> >> There are elements in common, but by and
> >> large the biggest headaches at least in large device number boots have
> >> already been tackled by the enterprise
On Thu, Sep 11, 2014 at 2:33 PM, Dirk Gouders wrote:
> What I was currently trying was to construct a test-environment so that
> I do not need to do tests and diagnosis on a busy machine.
>
> I noticed that this problem seems to start with the narrow Root
> Bridge window (00-07) but every other
On Tue, 29 Jul 2014 09:25:14 -0400 Sasha Levin wrote:
> On some failure paths we may attempt to free user context even
> if it wasn't assigned yet. This will cause a NULL ptr deref
> and a kernel BUG.
Are you able to identify "some failure paths"? I spent some time
grepping, but it's a pain.
On Thu, 11 Sep 2014 16:01:10 -0400
Vivek Goyal wrote:
> On Fri, Sep 05, 2014 at 06:33:14PM +0200, Petr Tesarik wrote:
> > On architectures that use percpu-vm, the percpu region is not guaranteed
> > to be contiguous in physical space.
>
> Petr,
>
> Which are those arches?
All except nommu.
On Thu, Sep 11, 2014 at 12:26 PM, Yinghai Lu wrote:
>
> This is amd two node systems. amd_bus.c tell us bus [00, 7f] is from
> first socket, but _OSC says only [0,7] is from first socket.
That might also explain why Dirk doesn't see it on his other machine.
The other machine doesn't have a buggy
On Thu, Sep 11, 2014 at 1:23 PM, Dmitry Torokhov
wrote:
>
>> There are elements in common, but by and
>> large the biggest headaches at least in large device number boots have
>> already been tackled by the enterprise crowd (they don't like their
>> S390's or 1024 core NUMA systems taking half
Yinghai Lu writes:
> On Thu, Sep 11, 2014 at 10:30 AM, Bjorn Helgaas wrote:
>> [+cc linux-pci]
>>
>>
>> On Thu, Sep 11, 2014 at 7:43 AM, Dirk Gouders wrote:
>>> Andreas Noever writes:
>>>
On Wed, Sep 3, 2014 at 2:47 PM, Dirk Gouders wrote:
> Andreas Noever writes:
>
>> On
> From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, September 11, 2014 1:20 PM
>
> On Thu, Sep 11, 2014 at 07:11:20PM +, Paul Zimmerman wrote:
> > > From: Robert Baldyga [mailto:r.bald...@samsung.com]
> > > Sent: Thursday, September 11, 2014 5:53 AM
> > >
Em Thu, Sep 11, 2014 at 11:21:40AM -0700, Tong Shen escreveu:
> Hi Arnaldo,
>
> Thanks a lot for the comment!
>
> I fixed the coding style and added a helper function with comments, as
> you suggested :-)
> See attachment.
That is much better, I'm adding lkml to the CC list so that we can give
Yinghai Lu writes:
> On Thu, Sep 11, 2014 at 10:30 AM, Bjorn Helgaas wrote:
>> [+cc linux-pci]
>>
>>
>> On Thu, Sep 11, 2014 at 7:43 AM, Dirk Gouders wrote:
>>> Andreas Noever writes:
>>>
On Wed, Sep 3, 2014 at 2:47 PM, Dirk Gouders wrote:
> Andreas Noever writes:
>
>> On
On Thu, Sep 11, 2014 at 12:54 PM, Daniel Borkmann wrote:
> On 09/10/2014 10:21 PM, Alexei Starovoitov wrote:
> ...
char bpf_log_buf[LOG_BUF_SIZE];
>>>
>>>
>>> What happens if the size isn't LOG_BUF_SIZE?
>>
>>
>> would do you mean?
>> LOG_BUF_SIZE is just a user defined
On Thu, Sep 11, 2014 at 12:47 PM, Daniel Borkmann wrote:
> On 09/10/2014 07:32 PM, Alexei Starovoitov wrote:
>>
>> On Wed, Sep 10, 2014 at 2:03 AM, Daniel Borkmann
>> wrote:
struct { /* anonymous struct used by BPF_PROG_LOAD command
*/
enum
Some first impressions in glancing at the code, not a complete review at
all:
On Thu, Sep 11, 2014 at 09:49:08AM -0600, mathieu.poir...@linaro.org wrote:
> --- /dev/null
> +++ b/drivers/coresight/coresight.c
> @@ -0,0 +1,663 @@
> +/* Copyright (c) 2012, The Linux Foundation. All rights reserved.
On Thu, Sep 11, 2014 at 12:59:25PM -0700, James Bottomley wrote:
>
> On Tue, 2014-09-09 at 16:01 -0700, Dmitry Torokhov wrote:
> > On Tuesday, September 09, 2014 03:46:23 PM James Bottomley wrote:
> > > On Wed, 2014-09-10 at 07:41 +0900, Tejun Heo wrote:
> > > >
> > > > The thing is that we have
On Thu, Sep 11, 2014 at 07:11:20PM +, Paul Zimmerman wrote:
> > From: Robert Baldyga [mailto:r.bald...@samsung.com]
> > Sent: Thursday, September 11, 2014 5:53 AM
> >
> > These two patches breaks dwc2 driver. The first one causes build break,
> > the second breaks gadget at Samsung platforms.
On Tue, Sep 9, 2014 at 1:37 PM, wrote:
> From: Suravee Suthikulpanit
>
> This patch adds ACPI support for non-PCI SATA contoller in ahci_platform
> driver.
> It adds ACPI matching table in ahci_platform to support AMD Seattle SATA
> controller
> with following ASL structure in DSDT:
>
>
On Wed, Sep 10, 2014 at 5:56 PM, Rusty Russell wrote:
>
> Probably won't read mail. Linus, I'll have pull requests early
> next week; if there's anything needed I'm sure Michael Tsirkin can
> handle it.
So according to "normal timing", I would do the 3.17 release about
three weeks from
> From: Paul Zimmerman
> Sent: Thursday, September 11, 2014 12:11 PM
>
> > From: Robert Baldyga [mailto:r.bald...@samsung.com]
> > Sent: Thursday, September 11, 2014 5:53 AM
> >
> > These two patches breaks dwc2 driver. The first one causes build break,
> > the second breaks gadget at Samsung
On 09/11/2014 06:04 AM, One Thousand Gnomes wrote:
>>> Is *that* what we are talking about? I was added to this conversation
>>> in the middle where it had already generalized, so I had no idea.
>>
>> No, this is just what brought this craziness to my attention.
>
> None of it is craziness. It's
On Fri, Sep 05, 2014 at 06:33:14PM +0200, Petr Tesarik wrote:
> On architectures that use percpu-vm, the percpu region is not guaranteed
> to be contiguous in physical space.
Petr,
Which are those arches?
> However, fs/proc/vmcore.c expects
> all ELF notes to be contiguous. If the ELF note
On Tue, 2014-09-09 at 16:01 -0700, Dmitry Torokhov wrote:
> On Tuesday, September 09, 2014 03:46:23 PM James Bottomley wrote:
> > On Wed, 2014-09-10 at 07:41 +0900, Tejun Heo wrote:
> > >
> > > The thing is that we have to have dynamic mechanism to listen for
> > > device attachments no matter
On Wed, 10 Sep 2014 22:41:04 -0700 Peter Feiner wrote:
> On Wed, Sep 10, 2014 at 04:36:28PM -0700, Andrew Morton wrote:
> > On Wed, 10 Sep 2014 16:24:46 -0700 Peter Feiner wrote:
> > > @@ -1048,32 +1048,51 @@ static int pagemap_pte_range(pmd_t *pmd, unsigned
> > > long addr, unsigned long end,
On 09/10/2014 10:21 PM, Alexei Starovoitov wrote:
...
char bpf_log_buf[LOG_BUF_SIZE];
What happens if the size isn't LOG_BUF_SIZE?
would do you mean?
LOG_BUF_SIZE is just a user defined macro.
Can be anything.
I believe, Andy means, what would happen if log_level > 0 but
the
On 09/10/2014 07:32 PM, Alexei Starovoitov wrote:
On Wed, Sep 10, 2014 at 2:03 AM, Daniel Borkmann wrote:
struct { /* anonymous struct used by BPF_PROG_LOAD command */
enum bpf_prog_typeprog_type;
__u32 insn_cnt;
Anyone ???
On Sun, Sep 7, 2014 at 3:58 PM, Vidya Sagar wrote:
> From: Vidya Sagar
>
> As per PCIe spec, fast back-to-back transactions feature
> is not applicable to PCIe devices. Hence, do not print
> that fast back-to-back trasactions are disabled when
> there is a PCIe device found on the
Hi all,
is anything wrong with the patch below? Are there questions? I thought
this would be an easy one-line bugfix...
Regards,
Petr Tesarik
On Fri, 5 Sep 2014 18:33:14 +0200
Petr Tesarik wrote:
> On architectures that use percpu-vm, the percpu region is not guaranteed
> to be contiguous in
On Thu, Sep 11, 2014 at 03:03:50PM +0200, Javier Martinez Canillas wrote:
> This can be easily worked around (and probably why it never was an issue) if
> the OF and SPI tables are kept in sync but I don't know if that is a hard
> requirement for all use-cases (e.g: a SPI driver that is DT
cat /sys/…/pools followed by removal the device leads to:
|==
|[ INFO: possible circular locking dependency detected ]
|3.17.0-rc4+ #1498 Not tainted
|---
|rmmod/2505 is trying to acquire lock:
On Wed, Sep 10, 2014 at 04:19:21PM +0400, Sergey Ryazanov wrote:
> 2014-09-10 15:36 GMT+04:00, Jiri Slaby :
> > On 09/10/2014, 12:33 PM, Sergey Ryazanov wrote:
> >> 2014-09-09 22:27 GMT+04:00, John W. Linville :
> >>> On Fri, Sep 05, 2014 at 04:02:10PM +0400, Sergey Ryazanov wrote:
>
On Thu, Sep 11, 2014 at 10:30 AM, Bjorn Helgaas wrote:
> [+cc linux-pci]
>
>
> On Thu, Sep 11, 2014 at 7:43 AM, Dirk Gouders wrote:
>> Andreas Noever writes:
>>
>>> On Wed, Sep 3, 2014 at 2:47 PM, Dirk Gouders wrote:
Andreas Noever writes:
> On Wed, Sep 3, 2014 at 12:57 PM, Dirk
> hwc->idx is not 64 -- it's 0xd64
> The bt insn is causing a page fault 27 MB past c->idxmsk
Ah true. Thanks.
However I don't think it changes the conclusion. Likely
the box pointer is wrong.
-Andi
>
>
--
a...@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this
On Thu, Sep 11, 2014 at 08:48:16AM +0800, roy.qing...@gmail.com wrote:
> From: Li RongQing
>
> !likely() is hard to be understood, and I do not know if compiler can
> optimise this condition, but unlikely(!()) is clear
>
> Signed-off-by: Li RongQing
> ---
> kernel/signal.c |2 +-
> 1
On Thu, 11 Sep 2014, Peter Zijlstra wrote:
> On Thu, Sep 11, 2014 at 03:07:52PM +0200, Vincent Guittot wrote:
> > > Also I'm not entirely sure I like the usage, utilization names/metrics.
> > > I would suggest to reverse them. Call the pure running number
> > > 'utilization' and this scaled with
> From: Robert Baldyga [mailto:r.bald...@samsung.com]
> Sent: Thursday, September 11, 2014 5:53 AM
>
> These two patches breaks dwc2 driver. The first one causes build break,
> the second breaks gadget at Samsung platforms.
>
> Best regards
> Robert Baldyga
>
> Robert Baldyga (2):
> Revert
From: Kan Liang
This reverts commit 50e200f07948 ("perf tools: Default to cpu// for
events v5")
The fixup cannot handle the case that
new style format(which without //) mixed with
other different formats.
For example,
group events with new style format: {mem-stores,mem-loads}
some hardware
From: Kan Liang
There are two types of event formats for PMU events. E.g. el-abort OR
cpu/el-abort/. However, the lexer mistakenly recognizes the simple style
format as two events.
The parse_events_pmu_check function uses bsearch to search the name in
known pmu event list. It can tell the lexer
From: Kan Liang
There are two types of pmu event stytle formats, "pmu_event_name"
or "cpu/pmu_event_name/". However, there is a bug on supporting these
two formats, especially when they mixed with other perf events.
The patch set intends to fix this issue.
The patch set has been tested on my
From: Kan Liang
Add new rules for kernel PMU event.
Currently, the patch only want to handle the PMU event name as "a-b" and
"a".
event_pmu:
PE_KERNEL_PMU_EVENT
|
PE_PMU_EVENT_PRE '-' PE_PMU_EVENT_SUF
PE_KERNEL_PMU_EVENT token is for
cycles-ct/cycles-t/mem-loads/mem-stores.
The prefix cycles
On 09/10/2014 01:12 PM, Murali Karicheri wrote:
Keystone PCI hardware supports both RC and EP modes and devcfg
register has bits to boot strap the device to either of these modes.
It seems proper to add this functionality to the boot loader rather
than in the driver as device will be operating
On 09/08/2014 01:03 PM, Murali Karicheri wrote:
Keystone PCI controller has a limitation that memory read request
size must not exceed 256 bytes. This is a hardware limitation and
add a quirk to force this limit on all downstream devices by
updating mrrs.
Signed-off-by: Murali Karicheri
---
On Tue, 26 Aug 2014, Vincent Guittot wrote:
> This new field cpu_capacity_orig reflects the available capacity of a CPUs
s/a CPUs/a CPU/
> unlike the cpu_capacity which reflects the current capacity that can be
> altered
> by frequency and rt tasks.
Shouldn't this be described as the "highest
On Tue, 26 Aug 2014, Vincent Guittot wrote:
> Use the new arch_scale_cpu_capacity in order to reflect the original capacity
> of a CPU instead of arch_scale_freq_capacity which is more linked to a scaling
> of the capacity linked to the frequency.
>
> Signed-off-by: Vincent Guittot
Acked-by:
On Thu, 2014-09-11 at 12:34 -0500, J. German Rivera wrote:
> From: "J. German Rivera"
>
> Platform device driver that sets up the basic bus infrastructure
> for the fsl-mc bus type, including support for adding/removing
> fsl-mc devices, register/unregister of fsl-mc drivers, and bus
> match
Dave,
Please pull this batch of fixes intended for the 3.17 stream:
For the mac80211 bits, Johannes says:
"Two more fixes for mac80211 - one of them addresses a long-standing
issue that we only found when using vendor events more frequently;
the other addresses some bad information being
On Thu, 2014-09-11 at 12:34 -0500, J. German Rivera wrote:
> APIs to access the Management Complex (MC) hardware
> module of Freescale LS2 SoCs. This patch includes
> APIs to check the MC firmware version and to manipulate
> DPRC objects in the MC.
> diff --git a/drivers/bus/fsl-mc/dpmng.c
On 09/11/2014 06:45 AM, Mike Looijmans wrote:
> Our KSZ9031 appears to suffer from the same hardware bug as described
> for the KSZ9021 in commit 32fcafbcd1c9f6c7013016a22a5369b4acb93577,
> you have to unplug the cable and plug it back to get it to work.
>
> Remove the SUPPORTED_Asym_Pause flag
On Thu, Sep 11, 2014 at 11:42:18AM +0100, Nikesh Oswal wrote:
> + /* add kcontrol */
> + for (i = 0; i < w->num_kcontrols; i++) {
> + kcontrol = snd_soc_cnew(>kcontrol_news[i], w,
> + w->name, NULL);
> + ret = snd_ctl_add(card, kcontrol);
*sigh* As I
Hi Mateusz,
> I can implement that later if it sounds sane enough.
Note this behaviour seems to be a requirement for cross-rename to work.
At least restoring previous behaviour while keeping cross-rename is not hard,
I can write it later.
Have you find a proper solution for this very issue
Hi Philipp,
Thank you for the patch.
On Thursday 11 September 2014 17:33:04 Philipp Zabel wrote:
> This patch adds a function to get a port device tree node by port id,
> or reg property value.
>
> Signed-off-by: Philipp Zabel
Acked-by: Laurent Pinchart
> ---
> Changes since v2:
> - Fixed
On 09/11/2014 05:09 AM, Christoffer Dall wrote:
> On Mon, Sep 01, 2014 at 02:52:40PM +0200, Eric Auger wrote:
>> Fix multiple injection of level sensitive forwarded IRQs.
>> With current code, the second injection fails since the state bitmaps
>> are not reset (process_maintenance is not called
On Thu, Sep 11, 2014 at 05:51:31PM +0800, Chen Hanxiao wrote:
> Use marco instead of magic number
> for max user namespace level.
patch is ok, but you might want to do s/marco/macro/
--
Aristeu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Thu, 2014-09-11 at 19:10 +0200, Christoffer Dall wrote:
> On Wed, Sep 10, 2014 at 11:05:49PM -0600, Alex Williamson wrote:
> > On Thu, 2014-09-11 at 05:10 +0200, Christoffer Dall wrote:
> > > On Mon, Sep 01, 2014 at 02:52:47PM +0200, Eric Auger wrote:
>
> [...]
>
> > > >
> > > > +#ifdef
On Thu, 2014-09-11 at 19:05 +0200, Christoffer Dall wrote:
> On Thu, Sep 11, 2014 at 10:44:02AM +0200, Eric Auger wrote:
> > On 09/11/2014 05:10 AM, Christoffer Dall wrote:
> > > On Mon, Sep 01, 2014 at 02:52:43PM +0200, Eric Auger wrote:
> > >> In case the IRQ is forwarded, the VFIO platform IRQ
On Wed, Sep 10, 2014 at 11:42:12AM -0500, Seth Forshee wrote:
> On Wed, Sep 10, 2014 at 06:21:55PM +0200, Serge E. Hallyn wrote:
> > Quoting Seth Forshee (seth.fors...@canonical.com):
> > > On Tue, Sep 02, 2014 at 10:44:53AM -0500, Seth Forshee wrote:
> > > > Another issue mentioned by Eric was
This patch series introduces Linux support for the Freescale
Management Complex (fsl-mc) hardware.
The fsl-mc is a hardware resource manager that manages specialized
hardware objects used in network-oriented packet processing
applications. After the fsl-mc block is enabled, pools of hardware
On Thu, Sep 11, 2014 at 10:14 AM, Benjamin Tissoires
wrote:
>
> Currently, tablets connected to the WL receiver all share the same
> VID/PID. There is no way for the user space to know which one is which
> besides parsing the name. We can force the PID to be set to the
> actual hardware. This
Kever,
On Wed, Sep 10, 2014 at 3:05 AM, Kever Yang wrote:
> This patch add intmem node des which is needed by platsmp.c
> and enable the smp.
>
> Signed-off-by: Heiko Stuebner
> Signed-off-by: Kever Yang
> ---
>
> arch/arm/boot/dts/rk3288.dtsi | 18 ++
> 1 file changed, 18
On Tuesday, September 09, 2014 3:26 AM, Ian Abbott wrote:
> The `comedi_board` inline function takes a single parameter of type
> `struct comedi_device *` and merely returns the value of the `board_ptr`
> member therein. This is somewhat superfluous as the member can be
> accessed directly.
>
>
Hello Sasha,
I have CCed Jan, because he has been the only one working on this file
in the last 18 months.
A failure path in which group->inotify_data.user is not yet assigned
starts here:
static struct fsnotify_group *inotify_new_group(unsigned int max_events)
{
...
oevent =
From: Boris BREZILLON
Signed-off-by: Boris BREZILLON
Signed-off-by: Alexandre Belloni
---
Changes in v2:
- reworked the error path to really make the clock optional
- Documented the new optional property
.../devicetree/bindings/mtd/atmel-nand.txt | 1 +
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
Changes in RFC v4:
- Fixed
From: "J. German Rivera"
Platform device driver that sets up the basic bus infrastructure
for the fsl-mc bus type, including support for adding/removing
fsl-mc devices, register/unregister of fsl-mc drivers, and bus
match support to bind devices to drivers.
Signed-off-by: J. German Rivera
From: "J. German Rivera"
APIs to access the Management Complex (MC) hardware
module of Freescale LS2 SoCs. This patch includes
APIs to check the MC firmware version and to manipulate
DPRC objects in the MC.
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
From: "J. German Rivera"
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
MAINTAINERS |8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7e2eb4c..eb8597d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3841,6 +3841,14 @@ S:
Change miphy365x over to select GENERIC_PHY like all other phy drivers.
Also update the help message as the new stih410 SoC doesn't have this
phy (it is very similar to sti407), so the stih41x naming is sadly no
longer correct.
Signed-off-by: Peter Griffin
---
drivers/phy/Kconfig | 6 +++---
1
On Thu, Sep 11, 2014 at 04:02:45PM +, David Laight wrote:
> From: Aaron Tomlin
> > Currently in the event of a stack overrun a call to schedule()
> > does not check for this type of corruption. This corruption is
> > often silent and can go unnoticed. However once the corrupted
> > region is
* Nishanth Menon [140910 03:21]:
> Commit d4d8819e205854c ("bus: omap_l3_noc: fix masterid detection")
> did the right thing in dropping the LSB 2 bits which is not part
> of the ConnID for NTTP master address. However, as part of that
> change, we should also have ensured that existing list of
On 11/09/14 18:29, Doug Anderson wrote:
> Marc,
>
> On Thu, Sep 11, 2014 at 10:22 AM, Marc Zyngier wrote:
>>> We would need to run this code potentially at processor bringup and
>>> after suspend/resume, but that seems possible too.
>>
>> Note that this would be an ARMv7 only thing (you can't do
Hi Ulf,
thanks for the patch!
Am Mittwoch, den 10.09.2014, 15:43 +0200 schrieb Ulf Hansson:
> For several reasons it's good practice to leave devices in runtime PM
> active state while those have been probed.
It would be nice to mention those reasons.
> In this cases we also want to prevent
On 11/09/2014 at 15:53:08 +0200, Boris Brezillon wrote :
> The GPBR registers are not part of the RTT block and thus should not be
> defined in the reg property of the rtt node.
>
> Use syscon to provide a proper DT representation and reference the GPBR
> syscon device in a new "atmel,time-reg"
Kever,
On Wed, Sep 10, 2014 at 3:05 AM, Kever Yang wrote:
> -CPU_METHOD_OF_DECLARE(rk3066_smp, "rockchip,rk3066-smp", _smp_ops);
> +CPU_METHOD_OF_DECLARE(rk3288_smp, "rockchip,rk3288-smp",
> _smp_ops);
I haven't done a full review, but I think that the above means you
need to update
On Thu, Sep 11, 2014 at 03:52:46PM +0100, Nick Dyer wrote:
> On 15/08/14 17:13, Stephen Warren wrote:
> >>> Any comments on this? I would really appreciate if you can expand on how
> >>> this DT property is supposed to be used so I can re-spin the atmel support
> >>> patch for Peach boards.
> >>
>
On 09/11/2014 05:09 AM, Christoffer Dall wrote:
> On Mon, Sep 01, 2014 at 02:52:41PM +0200, Eric Auger wrote:
>> add a lock related to the rb tree manipulation. The rb tree can be
>
> Ok, I can't hold myself back any longer.
Please begin sentences with a
> capital letter. You don't do this in
On Thu, Sep 11, 2014 at 11:35:56AM +0200, Eric Auger wrote:
> On 09/11/2014 05:10 AM, Christoffer Dall wrote:
> > On Mon, Sep 01, 2014 at 02:52:47PM +0200, Eric Auger wrote:
[...]
> >> + if (!pfwd)
> >> + return -ENOMEM;
> >> + pfwd->index = fwd_irq->index;
> >> + pfwd->gsi =
[+cc linux-pci]
On Thu, Sep 11, 2014 at 7:43 AM, Dirk Gouders wrote:
> Andreas Noever writes:
>
>> On Wed, Sep 3, 2014 at 2:47 PM, Dirk Gouders wrote:
>>> Andreas Noever writes:
>>>
On Wed, Sep 3, 2014 at 12:57 PM, Dirk Gouders wrote:
> On a Tyan VX50 (B4985) I ran into problems
Marc,
On Thu, Sep 11, 2014 at 10:22 AM, Marc Zyngier wrote:
>> We would need to run this code potentially at processor bringup and
>> after suspend/resume, but that seems possible too.
>
> Note that this would be an ARMv7 only thing (you can't do that on ARMv8,
> at all).
Yes, of course.
>>
On 11 September 2014 18:15, Peter Zijlstra wrote:
> On Tue, Aug 26, 2014 at 01:06:54PM +0200, Vincent Guittot wrote:
>> +static inline int group_has_free_capacity(struct sg_lb_stats *sgs,
>> + struct lb_env *env)
>> {
>> + if ((sgs->group_capacity_orig * 100) >
>> +
201 - 300 of 2200 matches
Mail list logo
