So this commit worries me.
This bug is a good find, and the fix is obviously needed and urgent, but I'm
not
sure about the implementation at all. (I've Cc:-ed a few more x86 low level
gents.)
* Matt Fleming wrote:
> /*
> + * Iterate the EFI memory map in reverse order because the regions
The Qualcomm WCNSS can crash by watchdog or a fatal software error. Add
these types to the list of remoteproc crash reasons.
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/remoteproc_core.c | 2 ++
include/linux/remoteproc.h | 4
2 files changed, 6 insertions(+)
diff
This introduces the peripheral image loader, for loading WCNSS firmware
and boot the core on e.g. MSM8974. The firmware is verified and booted
with the help of the Peripheral Authentication System (PAS) in
TrustZone.
Signed-off-by: Bjorn Andersson
---
The mdt loader is kept separate as it's
Remote processors like the ones found in the Qualcomm SoCs does not have
a resource table passed to them, so make it optional by only populating
it if it does exist.
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/remoteproc_core.c | 8 ++--
1 file changed, 2 insertions(+), 6
The document defines the binding for a component that loads firmware for
and boots the Qualcomm WCNSS core.
Signed-off-by: Bjorn Andersson
---
.../bindings/remoteproc/qcom,wcnss-pil.txt | 107 +
1 file changed, 107 insertions(+)
create mode 100644
This series provides the minimum changes needed to use remotproc on the
Qualcomm platform, it then introduces the Peripheral Image Loader for
the WCNSS core.
The implementation depends on https://lkml.org/lkml/2015/9/24/723
Bjorn Andersson (4):
remoteproc: core: Make the loaded resource table
1) When we run a tap on netlink sockets, we have to copy mmap'd SKBs
instead of cloning them. From Daniel Borkmann.
2) When converting classical BPF into eBPF, fix the setting of
the source reg to BPF_REG_X. From Tycho Andersen.
3) Fix igmpv3/mldv2 report parsing in the bridge multicast
From: Hubert Chrzaniuk
KNL increments APERF and MPERF every 1024 clocks.
This is compliant with the architecture specification,
which requires that only the ratio of APERF/MPERF need be valid.
However, turbostat takes advantage of the fact that these
two MSRs increment every un-halted clock
at
From: Len Brown
Staring in Linux-4.3-rc1,
commit 6fb3143b561c ("tools/power turbostat: dump CONFIG_TDP")
touches MSR 0x648, which is not supported on IVB-Xeon.
This results in "turbostat --debug" exiting on those systems:
turbostat: /dev/cpu/2/msr offset 0x648 read failed: Input/output error
From: Len Brown
On a Skylake with 1500MHz base frequency,
the TSC runs at 1512MHz.
This is because the TSC is no longer in the n*100 MHz BCLK domain,
but is now in the m*24MHz crystal clock domain. (24 MHz * 63 = 1512 MHz)
This adds error to several calculations in turbostat,
unless the TSC
Hi Rafael,
The following patches are available on my "intel_idle"
and "turbostat" branches, as usual, plus here for review.
[PATCH 1/4] intel_idle: Skylake Client Support - updated
Initial SKL intel_idle support went into 4.3-rc1.
That patch works, but this patch makes it more
From: Len Brown
Addition of PC9 state, and minor tweaks to existing PC6 and PC8 states.
Signed-off-by: Len Brown
---
drivers/idle/intel_idle.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
index
On Tue, 2015-09-15 at 09:07AM +0800, Shawn Lin wrote:
> On 2015/9/14 23:07, Sören Brinkmann wrote:
> >Hi Shawn,
> >
> >overall, it looks good to me. I have some questions though.
> >
> >On Mon, 2015-09-14 at 02:29PM +0800, Shawn Lin wrote:
>
> [...]
>
> >>+err_phy_exit:
> >>+ phy_init(phy);
>
Hello,
sometimes the Wifi adapter (Wireless-N 2230) in this Lenovo Thinkpad E431
"disappears" and cannot be fixed by re-loading the iwlwifi kernel module
either. Only a reboot will do.
When I was running 3.16.0-4-amd64 from Debian/stable, I noticed the
following message, but only _once_ and
From: huangdaode
Date: Fri, 25 Sep 2015 16:29:50 +0800
> @@ -191,9 +191,12 @@ static void hns_rcb_ring_init(struct ring_pair_cb
> *ring_pair, int ring_type)
> if (ring_type == RX_RING) {
> dsaf_write_dev(q, RCB_RING_RX_RING_BASEADDR_L_REG,
>
Herbert,
On 09/25/2015 08:55 AM, Herbert Xu wrote:
On Thu, Sep 24, 2015 at 10:34:10PM -0700, Guenter Roeck wrote:
Any idea what may be needed for 4.1 ?
I am currently trying https://patchwork.ozlabs.org/patch/473041/,
This patch should not make any difference on 4.1 and later because
4.1 is
$ objdump --dwarf drivers/powercap/intel_rapl.o |grep iosf
<65ad> DW_AT_name: (indirect string, offset: 0x3644):
iosf_mbi_read
<65f7> DW_AT_name: (indirect string, offset: 0x496):
iosf_mbi_write
5300iosf_mbi.h
0x0490 656c5f69 6400696f
On Fri, Sep 25, 2015 at 12:53:57PM +1000, Dave Chinner wrote:
> On Thu, Sep 24, 2015 at 09:50:29AM -0600, Ross Zwisler wrote:
> > On Thu, Sep 24, 2015 at 12:52:25PM +1000, Dave Chinner wrote:
> > > On Wed, Sep 23, 2015 at 02:40:00PM -0600, Ross Zwisler wrote:
> > > > Fix the deadlock exposed by
On 09/25/2015 02:37 PM, Steven Schlansker wrote:
On Sep 24, 2015, at 10:34 PM, Guenter Roeck wrote:
Herbert,
On 09/24/2015 09:58 PM, Herbert Xu wrote:
On Thu, Sep 24, 2015 at 09:36:53PM -0700, Guenter Roeck wrote:
http://comments.gmane.org/gmane.linux.network/363085
might explain your
Previously, we skip dentry block writes when wbc is SYNC_NONE with no memory
pressure and the number of dirty pages is pretty small.
But, we didn't skip for normal data writes, which gives us not much big impact
on overall performance.
Moreover, by skipping some data writes, kworker falls into
When using PSR, I see the screen freeze after only a few frames (sometimes a
split second; sometimes it seems like practically the first frame). Bisecting
led me to commit 3301d4092106 ("drm/i915: PSR: Fix DP_PSR_NO_TRAIN_ON_EXIT
logic") in v4.2. This patch is the simplest fix that gets it working
On Fri, Sep 25, 2015 at 02:29:04PM -0700, Paul E. McKenney wrote:
> On Wed, Sep 23, 2015 at 08:07:55AM +0800, Boqun Feng wrote:
> > On Tue, Sep 22, 2015 at 08:25:40AM -0700, Paul E. McKenney wrote:
> > > On Tue, Sep 22, 2015 at 07:37:04AM +0800, Boqun Feng wrote:
> > > > On Tue, Sep 22, 2015 at
On 09/25/15 09:38, Lee Jones wrote:
> This patch solves:
>
> on x86_64:
>
> when CONFIG_ACPI is not enabled:
>
> ../drivers/mfd/intel_soc_pmic_bxtwc.c: In function 'bxtwc_probe':
> ../drivers/mfd/intel_soc_pmic_bxtwc.c:342:2:
> error: implicit declaration of function 'acpi_evaluate_integer'
On Fri, Sep 25, 2015 at 7:24 AM, David Howells wrote:
> Here's my patch with the changes squashed into it for reference.
>
> David
> ---
> commit 81852354cf81402ae69fda4d67138accab2702d5
> Author: David Howells
> Date: Thu Sep 24 14:06:02 2015 +0100
>
> MODSIGN: Change from CMS to PKCS#7
Hi Enric,
FYI, build test results on v4.3-rc2 (pls ignore if it's inappropriate base for
your patch).
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>>
Signed-off-by: Fengguang Wu
---
slimport_tx_drv.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/bridge/anx78xx/slimport_tx_drv.c
b/drivers/gpu/drm/bridge/anx78xx/slimport_tx_drv.c
index 7721326..9afebab 100644
---
Hint to closest numa node for the placement of newly allocated pages.
As that is where the device's other allocations will originate by
default when it does not specify a NUMA node.
Cc: Christoph Hellwig
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
kernel/memremap.c |2 +-
1 file
Given we already have a device just use dev_to_node() to provide hint
allocations for devres. However, current devres_alloc() users will need
to explicitly opt-in with devres_alloc_node().
Signed-off-by: Dan Williams
---
drivers/base/devres.c | 19 ++-
include/linux/device.h
I noticed that pmem should be using blk_alloc_queue_node() and then I
wondered about the devm allocations... So, here is a quick conversion
of devm to use dev_to_node() for node local allocations by default and
as a result pmem to allocate all its driver infrastructure near to the
device.
---
Given that pmem ranges come with numa-locality hints, arrange for the
resulting driver objects to be obtained from node-local memory.
Signed-off-by: Dan Williams
---
drivers/nvdimm/pmem.c |5 +++--
kernel/memremap.c |7 ---
2 files changed, 7 insertions(+), 5 deletions(-)
diff
On Fri, Sep 25, 2015 at 04:29:44PM +0200, Thierry Reding wrote:
> On Thu, Sep 24, 2015 at 07:02:36PM +0200, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > Some modules register several sub-drivers. Provide a helper that makes
> > it easy to register and unregister a list of sub-drivers,
On Thu, Sep 24, 2015 at 8:10 AM, Christoph Hellwig wrote:
> On Wed, Sep 23, 2015 at 12:41:18AM -0400, Dan Williams wrote:
>> Switch avr32/include/asm/page.h to use the common defintions for
>> pfn_to_page(), page_to_pfn(), and ARCH_PFN_OFFSET.
>
> This was the last architecture not using
On Fri, Sep 25, 2015 at 4:34 PM, Bjorn Helgaas wrote:
> On Fri, Sep 18, 2015 at 09:59:56AM +0100, Marc Zyngier wrote:
>> On Wed, 16 Sep 2015 17:31:40 -0700
>> Duc Dang wrote:
>>
>> > With commit 8d63bc7beaee ("PCI/MSI: pci-xgene-msi: Get rid of
>> > struct msi_controller"), it is no longer
On Fri, Sep 25, 2015 at 9:18 AM, Alex Williamson
wrote:
>> > > Or do we want to keep a white list to say which device should have
>> > > ROM bar as mush have, and other is optional to have ?
>> >
>> > Subject: [RFC PATCH] PCI: Add pci_dev_need_rom_bar()
>> >
>> > Only set that for
>> > 1. if
On Wednesday, September 16, 2015 01:58:06 PM Sudeep Holla wrote:
> acpi_parse_entries passes the table end pointer to the sub-table entry
> handler. acpi_parse_entries itself could validate the end of an entry
> against the table end using the length in the sub-table entry.
>
> This patch adds
On 09/25/2015 11:27 AM, Paolo Bonzini wrote:
> Provide a UAPI version of the header in the kernel, making it easier
> for interested projects to use an up-to-date version of the header.
>
> The new headers are placed under uapi/linux/ so as not to conflict
> with the glibc-provided headers in
On 09/25/2015 11:27 AM, Paolo Bonzini wrote:
> Some are in scsi.h. Keep them together in preparation for exposing them
> in UAPI headers.
>
> Cc: James Bottomley
> Cc: Christoph Hellwig
> Cc: linux-s...@vger.kernel.org
> Reviewed-by: Bart Van Assche
> Signed-off-by: Paolo Bonzini
> ---
>
On 09/25/2015 11:27 AM, Paolo Bonzini wrote:
> SCSI_REMOVAL_* goes together with other SCSI command constants in
> include/scsi/scsi.h. It is also used outside the implementation
> of the ioctls (and it is not part of the user API).
>
> scsi_fctargaddress/Scsi_FCTargAddress has had no in-tree
On 09/25/2015 11:27 AM, Paolo Bonzini wrote:
> These will not be exported by the new linux/sg.h header, and scsi/sg.h will
> not have any user API after linux/sg.h is created. Since they have no
> user in the kernel, they can be zapped.
>
> Cc: James Bottomley
> Cc: Christoph Hellwig
> Cc:
On Thu, Sep 17, 2015 at 02:02:45PM +0800, Jiang Liu wrote:
> Avoid IRQs occupied by ISA IRQs when allocating IRQs for PCI link devices,
> otherwise it may cause interrupt storm due to incompatible pin attributes.
>
> This issue was triggered on a KVM virtual machine, which
> 1) uses IRQ9 for SCI
On Thu, Sep 17, 2015 at 02:02:46PM +0800, Jiang Liu wrote:
> Now we have dedicated interface acpi_penalize_sci_irq() to penalize
> ISA IRQ used by ACPI SCI, so remove duplicated code to penalize ACPI SCI
> in acpi_irq_penalty_init().
>
> Signed-off-by: Jiang Liu
Acked-by: Bjorn Helgaas
> ---
On Fri, Sep 18, 2015 at 09:59:56AM +0100, Marc Zyngier wrote:
> On Wed, 16 Sep 2015 17:31:40 -0700
> Duc Dang wrote:
>
> > With commit 8d63bc7beaee ("PCI/MSI: pci-xgene-msi: Get rid of
> > struct msi_controller"), it is no longer required to assign
> > msi_controller for X-Gene PCIe host bridge
On Fri, Sep 25, 2015 at 12:23:34PM -0600, Ross Zwisler wrote:
> On Fri, Sep 25, 2015 at 12:53:57PM +1000, Dave Chinner wrote:
> <>
> > We've already got block allocation serialisation at the filesystem
> > level, and the issue is the unserialised block zeroing being done by
> > the dax code. That
On Sunday, September 13, 2015 03:02:19 PM Marc Zyngier wrote:
The subject is slightly confusing IMO (there is a device probing infrastructure
in the ACPI subsystem, but not for the kind of devices in question here).
> IRQ controllers and timers are the two types of device the kernel
> requires
On Tue, Sep 15, 2015 at 05:39:14PM -0700, Ray Jui wrote:
> This patch series contains various fixes and outbound mapping support for
> the Broadcom iProc PCIe driver. Some of the critical fixes include 1) fix of
> PCIe core reset logic and therefore remove its dependency on the bootloader;
> 2)
On 09/25/2015 12:11 AM, Ingo Molnar wrote:
>>> > > Btw., how does pkey support interact with hugepages?
>> >
>> > Surprisingly little. I've made sure that everything works with huge pages
>> > and
>> > that the (huge) PTEs and VMAs get set up correctly, but I'm not sure I had
>> > to
>> >
On Sunday, September 13, 2015 03:02:18 PM Marc Zyngier wrote:
> IRQ controllers and timers are the two types of device the kernel
> requires before being able to use the device driver model.
>
> The Device Tree infrastructure makes it very easy to make these
> discoverable by the rest of the
When configuring input device via input_configured callback we may
encounter errors (for example input_mt_init_slots() may fail). Instead
of continuing with half-initialized input device let's allow driver
indicate failures.
Signed-off-by: Jaikumar Ganesh
Signed-off-by: Arve Hjønnevåg
> On Thu, Sep 24, 2015 at 09:42:38AM +1000, Aleksa Sarai wrote:
>> Does it make sense for the PIDs controller to allow a user to set a
>> limit of 0? Since we don't cancel attaches, a limit of 0 doesn't
>> affect anything (nothing stops attaches, and you need to have a
>> process in the PIDs
On 14/09/15 16:47, Florian Fainelli wrote:
> Hi,
>
> This patch series add PWM support for the Broadcom BCM7xxx
> chips which feature one or more PWM controllers capable of
> output periods from 148ns to ~622ms using a combination of
> variable and fixed frequency settings.
Thierry, are you
On Wednesday, September 16, 2015 05:26:40 PM Al Stone wrote:
> Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity
> check on the various subtables that are defined for the MADT. The check
> compares the size of the subtable data structure as defined by ACPICA to
> the length
On Friday, September 25, 2015 11:52:23 PM Rafael J. Wysocki wrote:
> On Friday, September 25, 2015 05:13:04 PM Alan Stern wrote:
> > On Fri, 25 Sep 2015, Rafael J. Wysocki wrote:
> >
> > > On Friday, September 25, 2015 10:29:55 AM Alan Stern wrote:
> > > > On Fri, 25 Sep 2015, Rafael J. Wysocki
This is much simpler.
Signed-off-by: Rasmus Villemoes
---
security/selinux/ss/services.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c
index 994c824a34c6..aa2bdcb20848 100644
---
security_context_to_sid() expects a const char* argument, so there's
no point in casting away the const qualifier of value.
Signed-off-by: Rasmus Villemoes
---
security/selinux/hooks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/selinux/hooks.c
sprintf returns the number of characters printed (excluding '\0'), so
we can use that and avoid duplicating the length computation.
Signed-off-by: Rasmus Villemoes
---
security/selinux/ss/services.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
Signed-off-by: Rasmus Villemoes
---
security/selinux/ss/services.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c
index c550df0e0ff1..994c824a34c6 100644
--- a/security/selinux/ss/services.c
+++
A few random things I stumbled on.
While I'm pretty sure of the change in 1/5, I'm also confused, because
the doc for the reverse security_sid_to_context state that
@scontext_len is set to "the length of the string", which one would
normally interpret as being what strlen() would give (i.e.,
There seems to be a little confusion as to whether the scontext_len
parameter of security_context_to_sid() includes the nul-byte or
not. Reading security_context_to_sid_core(), it seems that the
expectation is that it does not (both the string copying and the test
for scontext_len being zero hint
On Fri, Sep 25, 2015 at 11:44 PM, Viresh Kumar wrote:
> On 25-09-15, 22:58, Rafael J. Wysocki wrote:
>> Say you have three adjacent fields in a structure, x, y, z, each one byte
>> long.
>> Initially, all of them are equal to 0.
>>
>> CPU A writes 1 to x and CPU B writes 2 to y at the same time.
Contact us for your compensation consignment box
--
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 http://www.tux.org/lkml/
Hi Erik,
>
> Yeah, I'm still reading this email thread and learned lots from it.
> I'm working on something more meaningful, but it's not going to be
> ground breaking of course, there is a led on my capslock key on a new
> machine I won at work that does not switch off properly after it is
>
From: Ard Biesheuvel
The new Properties Table feature introduced in UEFIv2.5 may split
memory regions that cover PE/COFF memory images into separate code
and data regions. Since these regions only differ in the type (runtime
code vs runtime data) and the permission bits, but not in the memory
From: Matt Fleming
Beginning with UEFI v2.5 EFI_PROPERTIES_TABLE was introduced that
signals that the firmware PE/COFF loader supports splitting code and
data sections of PE/COFF images into separate EFI memory map entries.
This allows the kernel to map those regions with strict memory
From: Matt Fleming
Folks,
The patches in this pull request fix kernel crashes when booting Linux
on UEFI v2.5 machines with the Properties Table feature enabled.
Essentially, when this feature is enabled the firmware allocates
separate entries in the EFI memory map for the code and data
On Sep 25, 2015, at 2:37 PM, Steven Schlansker
wrote:
>
> On Sep 24, 2015, at 10:34 PM, Guenter Roeck wrote:
>
>> Herbert,
>>
>> On 09/24/2015 09:58 PM, Herbert Xu wrote:
>>> On Thu, Sep 24, 2015 at 09:36:53PM -0700, Guenter Roeck wrote:
On Wed, Sep 9, 2015 at 3:04 AM, Lee Jones wrote:
> On Wed, 09 Sep 2015, Masahiro Yamada wrote:
>> 2015-08-25 0:11 GMT+09:00 Rob Herring :
>> > On Mon, Aug 24, 2015 at 1:57 AM, Lee Jones wrote:
>> >> On Wed, 29 Jul 2015, Masahiro Yamada wrote:
>> >>
>> >>> Signed-off-by: Masahiro Yamada
>> >>>
On 25-09-15, 22:58, Rafael J. Wysocki wrote:
> Say you have three adjacent fields in a structure, x, y, z, each one byte
> long.
> Initially, all of them are equal to 0.
>
> CPU A writes 1 to x and CPU B writes 2 to y at the same time.
>
> What's the result?
But then two CPUs can update the
kvm_arch_vcpu_runnable now also checks whether the power_off
flag is set.
Signed-off-by: Eric Auger
Reviewed-by: Christoffer Dall
---
arch/arm/kvm/arm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index 2b19ef7..9d16f76 100644
In case a vcpu off PSCI call is called just after we executed the
vcpu_sleep check, we can enter the guest although power_off
is set. Let's check the power_off state in the critical section,
just before entering the guest.
Signed-off-by: Eric Auger
Reported-by: Christoffer Dall
Reviewed-by:
This series introduces the capability to synchronously exit the guest
and prevent it from being re-entered. This modality will be used by
IRQ forwarding series when changing the state of the IRQ.
Former pause flag used when starting the vcpu in KVM_ARM_VCPU_POWER_OFF
state, in PSCI calls and in
The kvm_vcpu_arch pause field is renamed into power_off to prepare
for the introduction of a new pause field. Also vcpu_pause is renamed
into vcpu_sleep since we will sleep until both power_off and pause are
false.
Signed-off-by: Eric Auger
Reviewed-by: Christoffer Dall
---
v1 -> v2:
- rename
We introduce kvm_arm_halt_guest and resume functions. They
will be used for IRQ forward state change.
Halt is synchronous and prevents the guest from being re-entered.
We use the same mechanism put in place for PSCI former pause,
now renamed power_off. A new flag is introduced in arch vcpu state,
On Wed, Sep 23, 2015 at 08:07:55AM +0800, Boqun Feng wrote:
> On Tue, Sep 22, 2015 at 08:25:40AM -0700, Paul E. McKenney wrote:
> > On Tue, Sep 22, 2015 at 07:37:04AM +0800, Boqun Feng wrote:
> > > On Tue, Sep 22, 2015 at 07:26:56AM +0800, Boqun Feng wrote:
> > > > On Mon, Sep 21, 2015 at
On Wed, Sep 23, 2015 at 08:43:21AM +0200, Martin Schwidefsky wrote:
> On Tue, 22 Sep 2015 08:28:22 -0700
> "Paul E. McKenney" wrote:
>
> > On Tue, Sep 22, 2015 at 04:33:07PM +0200, Martin Schwidefsky wrote:
> > > On Tue, 22 Sep 2015 21:29:14 +0800
> > > Boqun Feng wrote:
> > >
> > > > On Tue,
On Sep 24, 2015, at 10:34 PM, Guenter Roeck wrote:
> Herbert,
>
> On 09/24/2015 09:58 PM, Herbert Xu wrote:
>> On Thu, Sep 24, 2015 at 09:36:53PM -0700, Guenter Roeck wrote:
>>>
>>> http://comments.gmane.org/gmane.linux.network/363085
>>>
>>> might explain your problem.
>>>
>>> I thought
The Freescale Management Complex and all associated objects
use message interrupts, and thus an msi-parent is required.
Signed-off-by: Stuart Yoder
---
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git
On Friday, September 18, 2015 05:52:04 PM Stephen Boyd wrote:
> This patch series adds support for CPR on MSM8916. The first
> patch exposes a corner voting API to the CPR driver so that we can
> change the corner for the MX regulator. If possible I would
> like to make this patch prettier, but I
On Thu, 24 Sep 2015, Cyrille Pitchen wrote:
> This patch documents the DT bindings for the Atmel Flexcom which will be
> introduced by sama5d2x SoCs. These bindings will be used by the actual
> Flexcom driver to be sent in another patch.
>
> Signed-off-by: Cyrille Pitchen
> Acked-by: Boris
On Thu, 24 Sep 2015, Cyrille Pitchen wrote:
> This patch defines some macros to be used as value for the
> "atmel,flexcom-mode" DT property. This value is then written into
> the Operating Mode (OPMODE) bit field of the Flexcom Mode Register.
>
> Signed-off-by: Cyrille Pitchen
> Acked-by:
On Fri, 25 Sep 2015, Andrew F. Davis wrote:
> On 09/25/2015 11:50 AM, Lee Jones wrote:
> >On Thu, 24 Sep 2015, Andrew F. Davis wrote:
> >
> >>This patch adds support for TPS65912 mfd device. It provides
> >>communication through the I2C and SPI interfaces. It contains
> >>the following
On Friday, September 25, 2015 05:13:04 PM Alan Stern wrote:
> On Fri, 25 Sep 2015, Rafael J. Wysocki wrote:
>
> > On Friday, September 25, 2015 10:29:55 AM Alan Stern wrote:
> > > On Fri, 25 Sep 2015, Rafael J. Wysocki wrote:
> > >
> > > > We are missing the "no remote wakeup" bit now (well,
Update the binding for the Freescale Management Complex to include definition
of ranges, msi-parent, and dpmac subnodes.
Stuart Yoder (3):
Docs: dt: fsl-mc: update binding to include msi-parent
Docs: dt: fsl-mc update binding to include definition of ranges
Docs: dt: fsl-mc: update binding
Define a ranges property to specify the mapping between
the MC address space and the system address space.
Signed-off-by: Stuart Yoder
---
.../devicetree/bindings/misc/fsl,qoriq-mc.txt | 30 +-
1 file changed, 29 insertions(+), 1 deletion(-)
diff --git
The fsl-mc node may optionally have dpmac sub-nodes that describe
the relationship between the Ethernet MACs which belong to the MC
and the Ethernet PHYs on the system board.
Signed-off-by: Stuart Yoder
---
.../devicetree/bindings/misc/fsl,qoriq-mc.txt | 45 ++
1 file
> -Original Message-
> From: Bastien Nocera [mailto:had...@hadess.net]
> Sent: 25 September, 2015 17:41
> To: Tirdea, Irina; Dmitry Torokhov; Aleksei Mamlin;
> linux-in...@vger.kernel.org
> Cc: Mark Rutland; Purdila, Octavian; linux-kernel@vger.kernel.org;
> devicet...@vger.kernel.org
On Friday, September 25, 2015 07:10:19 AM Richard Guy Briggs wrote:
> On 15/09/24, Paul Moore wrote:
> > On Friday, September 18, 2015 03:59:58 AM Richard Guy Briggs wrote:
...
> > XXX
>
> ???
Sorry, ignore that. The "XXX" was a placeholder for me while I was reviewing
your patch; normally I
On Fri, 25 Sep 2015, Rafael J. Wysocki wrote:
> On Friday, September 25, 2015 10:29:55 AM Alan Stern wrote:
> > On Fri, 25 Sep 2015, Rafael J. Wysocki wrote:
> >
> > > We are missing the "no remote wakeup" bit now (well, there is a PM QoS
> > > flag,
> > > but it isn't very useful, so I'd
On Tuesday, September 22, 2015 09:51:27 AM Stephen Boyd wrote:
> On 09/22, Viresh Kumar wrote:
> > of_property_count_u32_elems() will never return 0, but a -ve error value
> > of a positive count. And so the current !count check is wrong.
> >
> > Also, a missing "opp-microvolt" property isn't a
On Thursday, September 24, 2015 01:58:21 PM Viresh Kumar wrote:
> On 24 September 2015 at 12:28, Stephen Boyd wrote:
> > Reported-by: Viresh Kumar
> > Signed-off-by: Stephen Boyd
> > ---
> > drivers/base/power/opp/core.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> >
On Fri, 2015-09-25 at 04:32 -0700, Christoph Hellwig wrote:
> On Thu, Sep 24, 2015 at 05:03:18PM -0700, Dan Williams wrote:
> > That makes sense to me, especially because drivers/nvdimm/blk.c is
> > broken in the same way as drivers/nvdimm/pmem.c and it would be
> > awkward to have it use
> -Original Message-
> From: Bastien Nocera [mailto:had...@hadess.net]
> Sent: 25 September, 2015 17:44
> To: Tirdea, Irina; linux-in...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; Rob Herring; Pawel Moll; Ian Campbell;
> Kumar Gala; Purdila, Octavian; Dmitry Torokhov; Mark
>
On 09/25/2015 03:35 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Sep 25, 2015 at 03:19:57PM -0400, Boris Ostrovsky wrote:
On 09/25/2015 03:01 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Sep 25, 2015 at 01:17:40PM -0400, Boris Ostrovsky wrote:
On 09/25/2015 12:07 PM, Vitaly Kuznetsov wrote:
Also, I
Dne 24.9.2015 v 00:16 Michael Ellerman napsal(a):
>
>
> On 23 September 2015 19:50:52 GMT+10:00, Michal Marek
> wrote:
>> On 2015-09-23 07:40, Michael Ellerman wrote:
>>> +else ifneq ($(wildcard
>> arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG)),)
>>> @$(kecho) "*** Default configuration is based
On 9/25/15 12:28 PM, Grygorii Strashko wrote:
This patch series contains patches which fixes wrong APIs usage in atomic
context on RT-kernel. The final goal is to make TI OMAP GPIO driver
compatible with -RT kernel as much as possible.
Patch 1: required to be compatible with -RT kernel, because
Before this change MAX_LOCAL_APIC had the fixed value of 32*1024.
Such a big value causes several data arrays to be quite oversized:
phys_cpu_present_map is 4 kbytes (one bit per apic id),
__apicid_to_node[] is 64 kbytes,
apic_version[] is 128 kbytes.
On "usual" systems, APIC ids simply go from
Hello, Linus.
Another cgroup fix pull. The cgroup writeback support got
inadvertently enabled for traditional hierarchies revealing two
regressions which are currently being worked on. It shouldn't have
been enabled on traditional hierarchies, so disable it on them. This
is enough for making
On Friday, September 25, 2015 01:25:49 PM Viresh Kumar wrote:
> On 25 September 2015 at 13:33, Rafael J. Wysocki wrote:
> > You're going to change that into bool in the next patch, right?
>
> Yeah.
>
> > So what if bool is a byte and the field is not word-aligned
>
> Its between two 'unsigned
ACK. Assuming Trond gets this.--b.
On Thu, Sep 24, 2015 at 04:00:09PM +0200, Andrzej Hajda wrote:
> Due to incorrect len type bc_send_request returned always zero.
>
> The problem has been detected using proposed semantic patch
> scripts/coccinelle/tests/assign_signed_to_unsigned.cocci [1].
>
On 25 September 2015 at 13:33, Rafael J. Wysocki wrote:
> You're going to change that into bool in the next patch, right?
Yeah.
> So what if bool is a byte and the field is not word-aligned
Its between two 'unsigned long' variables today, and the struct isn't packed.
So, it will be aligned,
On Fri, Sep 25, 2015 at 03:07:54PM -0400, Austin S Hemmelgarn wrote:
>
> Interestingly, based on what dieharder is already saying about performance,
> /dev/urandom is slower than AES_OFB (at least, on this particular system,
> happy to provide hardware specs if someone wants).
Yeah, not
1 - 100 of 1180 matches
Mail list logo
