Since xop and evex prefixes are extensions of vex mechanism,
they have similar bit layouts, and they can never be combined
(an instruction can have only one of them),
(ab)use insn->vex_prefix to store data of xop and evex too.
Users will need to conditionalize on insn->vex_prefix.bytes[0]
instead
Enable old link monitoring code and modify it:
- control LINK LED
- use separate timer so it does not interfere with ACT LED
- reset adapter on link loss to restart autonegotiation
(required to switch between 10/100 Mbps on OC-2326)
Tested with Olicom OC-2326.
Signed-off-by: Ondrej Zary
On Fri, May 16, 2014 at 11:34:13PM +0530, Himangi Saraogi wrote:
> Hi,
>
> In function hvc_opal_probe I find :
>
> hp = hvc_alloc(termno, 0, ops, MAX_VIO_PUT_CHARS);
> if (IS_ERR(hp))
> return PTR_ERR(hp);
>
> Earlier, hpc_opal_privs[termno] is assigned pv which
Olicom OC-2325 and OC-2326 ethernet cards have an activity LED but it does not
work with tlan driver as it's not enabled. Enable it.
Tested with OC-2326.
Signed-off-by: Ondrej Zary
---
drivers/net/ethernet/ti/tlan.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
On 05/15/2014 04:25 AM, Peter Zijlstra wrote:
> On Wed, May 14, 2014 at 04:59:58PM -0400, Carlos O'Donell wrote:
>> I will make my personal opinion clear:
>>
>> - Internal defects should raise immediate assertions.
>>
>> - Real problems like resource availability, deadlocks, and
>> other
On 05/15/2014 04:07 AM, Peter Zijlstra wrote:
> On Wed, May 14, 2014 at 05:17:35PM -0400, Carlos O'Donell wrote:
>>> No, its perfectly fine to have a lock sequence abort with -EDEADLK.
>>> Userspace should release its locks and re-attempt.
>>
>> I agree. If I can prove that it's actually a
This is already merged in wireless-next...
commit fe5d96246e9c4d266c4a8dca99f82ad82f2305b5
Author: Ondrej Zary
Date: Fri May 9 18:10:34 2014 +0200
orinoco_usb: Fix broken firmware load error checking
The check of ezusb_firmware_download() return value (added by commit
On Fri, 16 May 2014, Xiubo Li wrote:
> For each vmalloc area, there is one guard page at the end of it.
> so the vm->size = PAGE_ALIGN(offset + request size) + guard page size.
Nope. There is no guard page for statically created vmalloc areas.
> Signed-off-by: Richard Lee
> Signed-off-by:
(2014/05/17 1:27), Jiri Kosina wrote:
> On Tue, 6 May 2014, Steven Rostedt wrote:
>
>>> However, I also think if users can accept such freezing wait-time,
>>> it means they can also accept kexec based "checkpoint-restart" patching.
>>> So, I think the final goal of the kpatch will be live
This patch moves data allocated using kzalloc to managed data allocated
using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
functions.
The following Coccinelle semantic patch was used for making the change:
@platform@
identifier p, probefn, removefn;
@@
struct
This patch moves data allocated using kzalloc to managed data allocated
using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
functions.
The following Coccinelle semantic patch was used for making the change:
@platform@
identifier p, probefn, removefn;
@@
struct
The check of ezusb_firmware_download() return value (added by commit
488ec878034eccb852267b0e27ce9d511f75c587) is broken because
ezusb_firmware_download() returns 1 on success.
This causes the driver not to work with the following error:
orinoco_usb: probe of 3-3:1.0 failed with error -14
Check
On Fri, May 16, 2014 at 07:49:21PM +0200, Borislav Petkov wrote:
> Hi,
>
> so I was staring at
>
> 12544697f12e ("x86_64: be less annoying on boot, v2")
>
> and how naked numbers mean sh*t and how I have to grep sources to find
> out what this 10 thing means. So how about the following cleanup?
Roman Gushchin writes:
> At Thu, 15 May 2014 10:43:14 -0700,
> bseg...@google.com wrote:
>>
>> Roman Gushchin writes:
>>
>> > tg_set_cfs_bandwidth() sets cfs_b->timer_active to 0 to
>> > force the period timer restart. It's not safe, because
>> > can lead to deadlock, described in commit
On 05/14/2014 06:28 AM, Thomas Gleixner wrote:
> On Wed, 14 May 2014, Peter Zijlstra wrote:
>> On Wed, May 14, 2014 at 11:53:44AM +0200, Thomas Gleixner wrote:
What error would we return?
This particular case is a serious error for which we have no good error
code
to
On 05/14/2014 07:11 PM, Thomas Gleixner wrote:
> On Wed, 14 May 2014, Carlos O'Donell wrote:
>> On 05/14/2014 05:22 AM, Peter Zijlstra wrote:
> I believe the thinking goes that if we get to here, then the lock is in an
> inconsistent state (between kernel and userspace). I don't have an
On Fri, 16 May 2014, Frederic Weisbecker wrote:
> It works on a lower-level than the per WQ_SYSFS workqueues cpumask files
> such that the effective cpumask applied for a given unbound workqueue is
> the intersection of /sys/devices/virtual/workqueue/$WORKQUEUE/cpumask and
> the new
Hi Lejun,
On Wed, May 14, 2014 at 11:44:07PM +0800, Zhu, Lejun wrote:
> This patch adds support for the GPIO function in Crystal Cove.
in our device ACPI makes use of "virtual" GPIOs that have numbers from
0x20 to 0x5E to change various bits in the PMIC. Do you know if this
is officially
Hi,
so I was staring at
12544697f12e ("x86_64: be less annoying on boot, v2")
and how naked numbers mean sh*t and how I have to grep sources to find
out what this 10 thing means. So how about the following cleanup? We can
do it this way, we can do accessors and stuff, whatever. But the naked
On Fri, May 16 2014, Gioh Kim wrote:
> If CMA_SIZE_MBYTES is allowed to be zero, there should be defense code
> to check CMA is initlaized correctly. And atomic_pool initialization
> should be done by __alloc_remap_buffer instead of
> __alloc_from_contiguous if __alloc_from_contiguous is failed.
Hi Liviu,
Issue may not be only with SR-IOV resources.
I am not an expert with Linux PCI core. But i am trying to understand
how even for a non SR-IOV capable device's resource, gets a parent
associated with it.
When a PCI device driver calls pci_enable_device() which inturn calls
On 05/13/2014 07:14 PM, Reyad Attiyat wrote:
Dear IIO/HID maintainers,
I have a device, Surface Pro, that has the hid-sensor-hub and many
sensors attached. With the help of Srinivas I was able to get them all
working except for the magnometer. It uses the hid-magn-3d driver as
it should but it
On 05/16/2014 07:17 AM, Peter Ujfalusi wrote:
> From CCCFG register of eDMA3 we can get all the needed information for the
> driver about the IP:
> Number of channels: NUM_DMACH
> Number of regions: NUM_REGN
> Number of slots (PaRAM sets): NUM_PAENTRY
> Number of TC/EQ: NUM_EVQUE
>
> In case when
On Wed, May 14, 2014 at 5:44 PM, Zhu, Lejun wrote:
> Devices based on Intel SoC products such as Baytrail have a Power
> Management IC. In the PMIC there are subsystems for voltage regulation,
> A/D conversion, GPIO and PWMs. The PMIC in Baytrail-T platform is called
> Crystal Cove.
>
> This
Wed, 14 May 2014 23:10:39 +0200 от Alexander Holler :
> Am 14.05.2014 22:06, schrieb Grant Likely:
> > On Wed, 14 May 2014 16:49:05 +0200, Alexander Holler
> > wrote:
> >> Am 14.05.2014 16:05, schrieb Grant Likely:
> >>> On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
> >>> wrote:
>
> >>
On Fri, May 16 2014, Vlastimil Babka wrote:
> Compaction uses compact_checklock_irqsave() function to periodically check for
> lock contention and need_resched() to either abort async compaction, or to
> free the lock, schedule and retake the lock. When aborting, cc->contended is
> set to signal
On Fri, May 16, 2014 at 10:41 PM, Viresh Kumar wrote:
> On 16 May 2014 22:38, Inderpal Singh wrote:
+ while (!list_empty(_opp->opp_list)) {
+ opp = list_entry_rcu(dev_opp->opp_list.next,
+ struct dev_pm_opp, node);
>>>
>>>
On 16 May 2014 22:54, Inderpal Singh wrote:
> by the time "pos = list_entry_rcu(pos->member.
> next, typeof(*pos), member)" is executed, the pos would have been
> freed in the loop.
Oops!!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi Amit,
On Thu, May 08, 2014 at 03:37:57PM +0100, Amit Daniel Kachhap wrote:
> This patch adds notification support for those clients of cpu_cooling
> APIs which may want to do something interesting after receiving these
> cpu_cooling events. The notifier structure passed is of both Set/Get
On 05/15/2014 07:48 AM, Sekhar Nori wrote:
> On Thursday 15 May 2014 06:00 PM, Peter Ujfalusi wrote:
>
>> The second controller is not handled because in DT boot we only handle 1 cc
>> as
>> far as I know. I don't know why, but this is how the DT support has been
>> written and used.
>
> Its
On Fri, May 16, 2014 at 9:45 AM, Mark Salter wrote:
> On Mon, 2014-05-05 at 14:47 -0700, Iyappan Subramanian wrote:
>> +static int xgene_enet_probe(struct platform_device *pdev)
>> +{
>> + struct net_device *ndev;
>> + struct xgene_enet_pdata *pdata;
>> + struct device *dev =
Hi Miklos,
On Thu, May 15, 2014 at 4:25 PM, Miklos Szeredi wrote:
> On Fri, Apr 11, 2014 at 12:25 PM, Miklos Szeredi wrote:
>> From: Miklos Szeredi
>>
>> Signed-off-by: Miklos Szeredi
>> Cc: Chris Zankel
>
> Chris,
>
> I'll be sending a batch of patches with arch support for the renameat2
>
2014-05-16 13:53 GMT+02:00 Ville Syrjälä :
> On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
>> On Tue, May 13, 2014 at 05:21:49PM +0200, Jörg Otte wrote:
>> > 2014-05-13 15:22 GMT+02:00 Daniel Vetter :
>> > > On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
>> > >> On
On Fri, May 16, 2014 at 11:19:24AM -0600, Stephen Warren wrote:
> On 05/16/2014 11:09 AM, Tejun Heo wrote:
> > Can you try this one instead?
>
> Yes, this one works great, thanks.
> Tested-by: Stephen Warren
Thanks, I reverted the original one and applied the updated one w/
your Tested-by tag
On 05/16/2014 11:09 AM, Tejun Heo wrote:
> 9395a4500404 ("cgroup: enable refcnting for root csses") enabled
> reference counting for root csses (cgroup_subsys_states) so that
> cgroup's self csses can be used to manage the lifetime of the
> containing cgroups.
>
> Unfortunately, this change was
> How about get uptime by get_monotonic_boottime() directly, which's
> the same as /proc/uptime.
I don't know. get_monotonic_boottime() had existed for many releases
at the point the uptime trace clock was added - so it was an available
choice. Maybe not noticed by
Is this function safe to call
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd:
Linux 3.15-rc4 (2014-05-04 18:14:42 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
Hi Davidlohr,
On 05/15/2014 05:46 PM, Davidlohr Bueso wrote:
> On Thu, 2014-05-15 at 06:20 +0200, Manfred Spraul wrote:
>> Hi Davidlohr,
>>
>> On 05/14/2014 09:50 PM, Davidlohr Bueso wrote:
>>> Do you have any preferences? I can cook up a patch if you think that
>>> this merits Linux having
On Fri, May 16, 2014 at 06:27:27PM +0200, Jiri Kosina wrote:
> On Tue, 6 May 2014, Steven Rostedt wrote:
>
> > > However, I also think if users can accept such freezing wait-time,
> > > it means they can also accept kexec based "checkpoint-restart" patching.
> > > So, I think the final goal of
[Even more review feedback and some bugs addressed.]
[Only port to changes in perf/core. No other changes.]
[Rebase to latest perf/core]
This patchkit implements lbr-as-callgraphs in per freport,
as an alternative way to present LBR information.
Current perf report does a histogram over the
On 16 May 2014 22:38, Inderpal Singh wrote:
>>> + while (!list_empty(_opp->opp_list)) {
>>> + opp = list_entry_rcu(dev_opp->opp_list.next,
>>> + struct dev_pm_opp, node);
>>
>> list_for_each_entry_rcu ?
>>
>
> list_for_each_entry_rcu can
From: Andi Kleen
The srcline sort output ignored the width, which caused
various problems with displaying srcline in the tui
browser. Just cut it off at width.
Signed-off-by: Andi Kleen
---
tools/perf/util/sort.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Andi Kleen
For lbr-as-callgraph we need to see the line number in the history,
because many LBR entries can be in a single function, and just
showing the same function name many times is not useful.
When the history code is configured to sort by address, also try to
resolve the address to
9395a4500404 ("cgroup: enable refcnting for root csses") enabled
reference counting for root csses (cgroup_subsys_states) so that
cgroup's self csses can be used to manage the lifetime of the
containing cgroups.
Unfortunately, this change was incorrect. During early init,
cgrp_dfl_root self css
Hi Viresh,
Thanks for the review.
On Fri, May 16, 2014 at 3:36 PM, Viresh Kumar wrote:
> On 16 May 2014 14:39, Inderpal Singh wrote:
>> diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
>> +void dev_pm_opp_free_opp_table(struct device *dev)
>> +{
>> + struct device_opp
Is the numa maps gather_hugetbl_stats() buggy on s390? It uses the
normal pte_ variants.
--
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
From: Andi Kleen
With srcline key/sort'ing it's useful to have line numbers
in the annotate window. This patch implements this.
Use objdump -l to request the line numbers and
save them in the line structure. Then the browser
displays them for source lines.
The line numbers are not displayed by
From: Andi Kleen
When -v is specified always print the hex address for the srcline.
Signed-off-by: Andi Kleen
---
tools/perf/util/srcline.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/srcline.c b/tools/perf/util/srcline.c
index
From: Andi Kleen
For perf report with --sort srcline only print the base source file
name. This makes the results generally fit much better to the
screen. The path is usually not that useful anyways because it is
often from different systems.
Signed-off-by: Andi Kleen
---
From: Andi Kleen
When the source line is not found fall back to sym + offset.
This is generally much more useful than a raw address.
For this we need to pass in the symbol from the caller.
For some callers it's awkward to compute, so we stay
at the old behaviour.
Signed-off-by: Andi Kleen
---
From: Andi Kleen
Add a --branch-history option to perf report that changes all
the settings necessary for using the branches in callstacks.
This is just a short cut to make this nicer to use, it does
not enable any functionality by itself.
v2: Change sort order. Rename option to
From: Andi Kleen
Currently branch stacks can be only shown as edge histograms for
individual branches. I never found this display particularly useful.
This implements an alternative mode that creates histograms over complete
branch traces, instead of individual branches, similar to how normal
From: Andi Kleen
asprintf corrupts memory on some older glibc versions.
Provide a replacement. This fixes various segfaults
with --branch-history on older Fedoras.
Signed-off-by: Andi Kleen
---
tools/perf/Makefile.perf | 1 +
tools/perf/util/asprintf.c | 28
2
When consolidating the msm8660 GCC probe code I forgot to keep
around these temporary clock registrations. Put them back so the
clock tree is not entirely orphaned.
Fixes: 49fc825f0cc2 (clk: qcom: Consolidate common probe code)
Signed-off-by: Stephen Boyd
---
drivers/clk/qcom/gcc-msm8660.c | 12
On 05/16/2014 09:43 AM, Tejun Heo wrote:
> From 49035d695d8f1c4bbe4e37480e5d06812818947c Mon Sep 17 00:00:00 2001
> From: Tejun Heo
> Date: Fri, 16 May 2014 11:40:33 -0400
>
> 9395a4500404 ("cgroup: enable refcnting for root csses") enabled
> reference counting for root csses
Attn:
You have been selected for family resettlement to Australia , you are
among the list of nominated for 2014 resettlement visa to Australia from
our head of mission and we have granted your resettlement on the condition
that you meet some basic requirements.
Please confirm if you
Peter Zijlstra writes:
> On Thu, May 15, 2014 at 03:59:20PM -0700, Ben Segall wrote:
>> task_hot checks exec_start on any runnable task, but if it has been
>> migrated since the it last ran, then exec_start is a clock_task from
>> another cpu. If the old cpu's clock_task was sufficiently far
On 05/15/2014 02:20 PM, H. Peter Anvin wrote:
> I'm trying to wrap my head around any forward compatibility
> concerns... if we misidentify a fault as spurious that would be bad.
FWIW, I did go through the bullets in the SDM's "4.10.4.3 Optional
Invalidation". The only condition not covered by
On Thu, May 15, 2014 at 2:18 PM, Thierry Reding
wrote:
> On Thu, May 15, 2014 at 01:18:22PM -0700, Andrew Bresticker wrote:
>> Arnd,
>>
>> On Thu, May 15, 2014 at 1:17 AM, Arnd Bergmann wrote:
>> > On Wednesday 14 May 2014 17:33:02 Andrew Bresticker wrote:
>> >> +
>> >> +int
Linus,
On Fri, May 16, 2014 at 03:35:48PM +0200, Linus Walleij wrote:
> On Mon, May 5, 2014 at 7:27 AM, Antoine Ténart
> wrote:
>
> > Add the documentation related to the Berlin pin-controller driver and
> > explain how to configure this group based controller.
> >
> > Signed-off-by: Antoine
Looks good to me, especially the new comment.
Acked-by: Dave Hansen
--
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
On Mon, 2014-05-05 at 14:47 -0700, Iyappan Subramanian wrote:
> +static int xgene_enet_probe(struct platform_device *pdev)
> +{
> + struct net_device *ndev;
> + struct xgene_enet_pdata *pdata;
> + struct device *dev = >dev;
> + struct napi_struct *napi;
> + int ret =
On Mon, May 12, 2014 at 04:48:51PM +0100, Larry Bassel wrote:
> Support for arch_irq_work_raise() was missing from
> arm64 (a prerequisite for FULL_NOHZ).
>
> This patch is based on the arm32 patches ARM 7872/1
> and 7887/1.
Applied (with some clean-up of the commit log). Thanks.
--
Catalin
--
On 05/16/14 09:24, Linus Walleij wrote:
> On Wed, May 14, 2014 at 12:13 AM, Stephen Boyd wrote:
>
>> Please add a note that this id is fake in the commit text or in
>> the code as well.
> You just need one of your hardware engineers to add is to one instance
> of some test chip round so it exists
From: Lai Jiangshan
Changing the attributions of a workqueue imply the addition of new pwqs
to replace the old ones. But the current implementation doesn't handle
ordered workqueues because they can't carry multi-pwqs without breaking
ordering. Hence ordered workqueues currently aren't allowed
On Fri, 16 May 2014, Preeti Murthy wrote:
> Hi Nicolas,
> You might want to change the subject.
That was a tongue-in-cheek subject. I was wondering if anyone would
react to it. ;-)
> s/sched: remove remaining power to the CPU/
> sched: remove remaining usage of cpu *power* .
>
> The subject
Hello,
Today's cgroup/for-next contains aa190dd36dad ("cgroup: remove
css_parent()"). The wrapper was added while transitioning
cgroup-based hierarchy to css-based one. css-based hierarchy is
mostly getting into the shape now and the parent field is exported and
expected to remain stable, so
On 05/16/2014 06:36 PM, Swâmi Petaramesh wrote:
> Underlying is ecryptfs over BTRFS over LVM2 over LUKS (what else ?)
I recently switched one of my drives to BTRFS because I wanted
transparent compression. Since I also needed encryption, I chose:
BTRFS => LUKS (Device Mapper) => SCSI Block.
Is
On Sat, May 17, 2014 at 12:18:06AM +0800, Lai Jiangshan wrote:
> so the scheduler/set_cpus_allowed_ptr()/cpu_active_mask should be the first
> place to fix.
I'm not arguing about that, not to mention that this is userspace
exposed and nobody protects that.
But I was expecting kernel stuff that
On Fri, May 16, 2014 at 6:24 PM, Don Zickus wrote:
> On Fri, May 16, 2014 at 06:02:43PM +0200, Stephane Eranian wrote:
>> On Fri, May 16, 2014 at 5:59 PM, Peter Zijlstra wrote:
>> > On Fri, May 16, 2014 at 04:09:59PM +0200, Stephane Eranian wrote:
>> >> > +#define CACHE_LINESIZE 64
>> >> I
On Tue, 6 May 2014, Steven Rostedt wrote:
> > However, I also think if users can accept such freezing wait-time,
> > it means they can also accept kexec based "checkpoint-restart" patching.
> > So, I think the final goal of the kpatch will be live patching without
> > stopping the machine. I'm
Fix checkpatch warnings:
"WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable"
Cc: Thomas Gleixner
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
kernel/hrtimer.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index
On Fri, May 16, 2014 at 09:06:13AM -0700, H. Peter Anvin wrote:
> On 05/16/2014 08:34 AM, Peter Zijlstra wrote:
> >
> > While fuzzing to reproduce my issue I hit the below, its triggered loads
> > of times and then the machine wedged (needed a power cycle), I can
> > provide the full console log
On Wed, May 14, 2014 at 4:01 AM, wrote:
> From: Fan Wu
>
> The patch added params in disable_setting to differ the two possible usage,
> 1.Only want to disable the pin setting in SW aspect, param can be set to "0"
> 2.Want to disable the pin setting in both HW and SW aspect, param can be set
Create a cpumask that limit the affinity of all unbound workqueues.
This cpumask is controlled though a file at the root of the workqueue
sysfs directory.
It works on a lower-level than the per WQ_SYSFS workqueues cpumask files
such that the effective cpumask applied for a given unbound workqueue
On Fri, May 16, 2014 at 7:57 PM, Peter Zijlstra wrote:
> On Fri, May 16, 2014 at 11:50:42AM +0800, Lai Jiangshan wrote:
>> Hi, Peter and other scheduler Gurus:
>>
>> When I was trying to test wq-VS-hotplug, I always hit a problem in scheduler
>> with the following WARNING:
>>
>> [ 74.765519]
On Fri, May 16, 2014 at 06:02:43PM +0200, Stephane Eranian wrote:
> On Fri, May 16, 2014 at 5:59 PM, Peter Zijlstra wrote:
> > On Fri, May 16, 2014 at 04:09:59PM +0200, Stephane Eranian wrote:
> >> > +#define CACHE_LINESIZE 64
> >> I had something similar to your patch here in my original
Hello,
This series adds support for the USB cluster which is on the Armada
375 SoC. We can mainly see this device as a PHY muxer. After talking
with Antoine Ténart about it I found a better way than the previous
series to model it.
Only one controller can access to the PHY so instead trying to
Now that the USB cluster node has been added, use it as a PHY provider
for the USB controller linked to it: the first EHCI and the xHCI.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-375.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git
This commit extends the xhci-plat so that it can optionally be passed
a reference to a PHY through the Device Tree. It will be useful for
the Armada 375 SoCs. If no PHY is provided then the behavior of the
driver is unchanged.
As for the clock, to achieve this, it adds a 'struct phy *' member in
The Armada 375 SoC comes with an USB2 host and device controller and
an USB3 controller. The USB cluster control register allows to manage
common features of both USB controllers.
This commit adds a driver integrated in the generic PHY framework to
control this USB cluster feature.
On Armada 375, the USB cluster allows to control the cluster composed
of the USB2 and USB3 host controllers.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-375.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/armada-375.dtsi
On Wed, May 14, 2014 at 12:13 AM, Stephen Boyd wrote:
> Please add a note that this id is fake in the commit text or in
> the code as well.
You just need one of your hardware engineers to add is to one instance
of some test chip round so it exists in any hardware whatsoever and it
is not "fake"
Armada 375 comes with an USB2 host and device controller and an USB3
controller. The USB cluster control register allows to manage common
features of both USB controllers. This commit adds the Device Tree
binding documentation for this piece of hardware.
Signed-off-by: Gregory CLEMENT
---
On Wed, May 14, 2014 at 5:17 AM, Jingoo Han wrote:
> Use devm_ioremap_resource() because devm_request_and_ioremap() is
> obsoleted by devm_ioremap_resource().
>
> Signed-off-by: Jingoo Han
Acked-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line
On Fri, May 16, 2014 at 05:45:38PM +0200, Peter Zijlstra wrote:
> On Fri, May 16, 2014 at 09:33:00AM -0400, Don Zickus wrote:
> > On Fri, May 16, 2014 at 02:22:19PM +0200, Peter Zijlstra wrote:
> > > On Tue, May 13, 2014 at 12:48:12PM -0400, Don Zickus wrote:
> > > > From: Peter Zijlstra
> > > >
On Fri, May 16, 2014 at 04:54:11PM +0100, Mark Salter wrote:
> On Fri, 2014-05-16 at 11:04 +0100, Catalin Marinas wrote:
> > On Thu, May 15, 2014 at 03:19:22PM +0100, Mark Salter wrote:
> > > diff --git a/arch/arm64/mm/hugetlbpage.c b/arch/arm64/mm/hugetlbpage.c
> > > index 5e9aec3..9bed38f 100644
Allow to modify the low-level unbound workqueues cpumask through
sysfs. This is performed by traversing the entire workqueue list
and calling apply_workqueue_attrs() on the unbound workqueues with
the low level mask passed in.
Cc: Christoph Lameter
Cc: Kevin Hilman
Cc: Lai Jiangshan
Cc: Mike
The sysfs code usually belongs to the botom of the file since it deals
with high level objects. In the workqueue code it's misplaced and such
that we'll need to work around functions references to allow the sysfs
code to call APIs like apply_workqueue_attrs().
Lets move that block further in the
In order to allow overriding the unbound wqs low-level cpumask, we
need to be able to call apply_workqueue_attr() on all workqueues in
the pool list.
Now since traversing the pool list require to lock it, we can't currently
call apply_workqueue_attr() under the pool traversal.
So lets provide a
So in this version I actually save the cpumask belonging to wq (before
it's intersected against the low level cpumask) in its unbounds attrs.
But the attrs passed to pwq and worker pools have the low level cpumask
computed against the wq cpumask.
It makes it easier that way as the wq cpumask
On Fri, May 16, 2014 at 5:29 PM, Alexandre Courbot wrote:
> On 05/17/2014 12:25 AM, Linus Walleij wrote:
>> I got a horde of mails from Fengguang's autobuilder, I think you got
>> them as well ... else tell me and I'll dig them up.
>
> Mmm, it seems like I didn't get any mail. Could you follow
On Fri, 16 May 2014 16:49:37 +0200
Alexander Graf wrote:
>
> On 16.05.14 16:46, Michael Mueller wrote:
> > On Fri, 16 May 2014 13:55:41 +0200
> > Alexander Graf wrote:
> >
> >> On 13.05.14 16:58, Michael Mueller wrote:
> >>> The patch introduces facilities and cpu_ids per virtual machine.
>
On Fri, May 09, 2014 at 05:31:17PM -0400, Tejun Heo wrote:
> Hello,
>
> Currently, while csses (cgroup_subsys_states) have ->parent linkage
> too, only cgroups form full tree through their ->children and
> ->sibling fields and css iterations naturally is implemented by
> iterating cgroups and
On 05/16/2014 10:38 AM, Ben Hutchings wrote:
On Fri, 2014-05-16 at 09:20 -0500, Larry Finger wrote:
On 05/16/2014 07:47 AM, Ben Hutchings wrote:
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
Dmitry Semyonov reported that
>From 141fdfadf18c10fed33624bbd414fcc0cb74d7ca Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 16 May 2014 11:40:38 -0400
Implement css_tryget() which tries to grab a cgroup_subsys_state's
reference as long as it already hasn't reached zero. Combined with
the recent css iterator changes to
>From 55e2f1d4b69516f899712c04df6635309bf06983 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 16 May 2014 11:40:35 -0400
css iterations allow the caller to drop RCU read lock. As long as the
caller keeps the current position accessible, it can simply re-grab
RCU read lock later and
...and lines over 80 cols
Cc: Thomas Gleixner
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
kernel/hrtimer.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index 1eccb98..d2daf63 100644
--- a/kernel/hrtimer.c
+++
On 05/16/2014 08:34 AM, Peter Zijlstra wrote:
>
> While fuzzing to reproduce my issue I hit the below, its triggered loads
> of times and then the machine wedged (needed a power cycle), I can
> provide the full console log if people care.
>
> Anybody seen that one before?
>
I certainly
On Fri, May 16, 2014 at 04:09:59PM +0200, Stephane Eranian wrote:
> > +#define CACHE_LINESIZE 64
> I had something similar to your patch here in my original series for
> perf mem, but I never pushed it.
> I think this is a useful feature to have.
> However, I don't think you can hardcode the
201 - 300 of 1590 matches
Mail list logo
