SEC1 and SEC2 have different EU base addresses, so define base addresses
as #define
SEC1 and SEC2 have different bit masks for ISR registers, so create a
macro to define them
Signed-off-by: Christophe Leroy
---
drivers/crypto/talitos.h | 85 ++--
1
2015-03-06 17:42 GMT+03:00 Stanimir Varbanov :
> On 02/19/2015 07:41 PM, Matwey V. Kornilov wrote:
>> spear13xx_pcie_driver.driver is allocated in text.init section
>> and then the pointer to it is passed futher. This patch is to avoid
>> crashes like the following, when freed memory is used.
>>
>
On Fri, Mar 06, 2015 at 09:16:44AM -0600, Rob Herring wrote:
> On Fri, Mar 6, 2015 at 9:09 AM, Matt Porter wrote:
> > The imx-pwm binding contains language indicating compatible
> > strings to be used that is not valid for all supported parts
> > e.g. Should be "fsl,-pwm". Fix this by enumerating
On Fri, Mar 06, 2015 at 09:50:02AM -0600, Christoph Lameter wrote:
> On Thu, 5 Mar 2015, Serge E. Hallyn wrote:
>
> > > > So I'd say drop this change ^
> > >
> > > Then the ambient caps get ignored for a executables that have capabilities
> > > seton the file?
> >
> > Yes. Those are assumed to
On 03/06, David Vrabel wrote:
>
> On 06/03/15 15:36, Oleg Nesterov wrote:
> >
> > This needs more discussion, but in short so far I think that fpu_alloc()
> > from #NM exception is fine if user_mode(regs) == T.
>
> I think a memory allocation here, where the only behaviour on a failure
> is to
On Mar 4, 2015, at 11:45 PM, Emil Medve wrote:
> From: Igal Liberman
>
> The Freescale Data Path Acceleration Architecture (DPAA) is a set of
> hardware components on specific QorIQ P and T series multicore processors.
> This architecture provides the infrastructure to support simplified
>
On 3/2/2015 2:27 AM, Suravee Suthikulpanit wrote:
Device drivers typically use ACPI _HIDs/_CIDs listed in struct device_driver
acpi_match_table to match devices. However, for generic drivers, we do not
want to list _HID for all supported devices. Also, certain classes of devices
do not have _CID
The commit f06e5153f4ae2e2f3b0300f0e260e40cb7fefd45 introduced
"crash_kexec_post_notifiers" kernel boot option, which toggles
wheather panic() calls crash_kexec() before panic_notifiers and dump
kmsg or after.
The problem is that the commit overlooks panic_on_oops kernel boot
option. If it is
On 03/06/2015 02:06 AM, Hans de Goede wrote:
Hi,
On 05-03-15 15:58, Aleksey Makarov wrote:
The OCTEON SATA controller is currently found on cn71XX devices.
Signed-off-by: David Daney
Signed-off-by: Vinita Gupta
Signed-off-by: Aleksey Makarov
---
[...]
diff --git
Jim Davis writes:
>>> However, that commit is in next-20150304 and we still get the error
>>> (see, for example,
>>> http://kisskb.ellerman.id.au/kisskb/buildresult/12376688/).
>>
>> I applied few fixes from Rafal and Chen:
>>
>> 1ca2760fb2c1 bcma: prepare Kconfig symbol for PCI driver
>>
On 03/04/2015 10:32 PM, Francois Romieu wrote:
> Nicolas Schichan :
>> @@ -1050,7 +1049,7 @@ static int txq_reclaim(struct tx_queue *txq, int
>> budget, int force)
>> __netif_tx_lock_bh(nq);
>>
>> reclaimed = 0;
>> -while (reclaimed < budget && txq->tx_desc_count > 0) {
>> +
Hi,
* Rafael J. Wysocki [150305 17:38]:
> Please always CC linux-pm on CC patches.
Sure will do for the next rev, sorry forgot to add that.
> On Thursday, March 05, 2015 04:34:06 PM Tony Lindgren wrote:
> > +/**
> > + * handle_dedicated_wakeirq - Handler for device wake-up interrupts
> > + *
On Thu, Mar 05, 2015 at 10:30:34PM -0800, Greg Kroah-Hartman wrote:
> On Thu, Mar 05, 2015 at 04:08:44PM +, James Hogan wrote:
> > [ Upstream commit 3ce465e04bfd8de9956d515d6e9587faac3375dc ]
> >
> > Export the _save_fp asm function used by the lose_fpu(1) macro to GPL
> > modules so that KVM
On 06/03/15 15:36, Oleg Nesterov wrote:
> On 03/06, David Vrabel wrote:
>>
>> On 06/03/15 14:01, Oleg Nesterov wrote:
>>
>>> Not sure I understand it correctly after the first quick look, but
>>>
>>> 1. It conflicts with the recent changes in tip/x86/fpu
>>>
>>> 2. fpu_ini() initializes
On Mar 5, 2015, at 7:51 PM, Kenneth Westfield wrote:
> On Thu, Mar 05, 2015 at 12:52:30PM -0600, Kumar Gala wrote:
>>
>> On Mar 3, 2015, at 6:21 PM, Kenneth Westfield
>> wrote:
>>
>>> +++ b/Documentation/devicetree/bindings/sound/qcom,lpass-cpu.txt
>>> @@ -0,0 +1,49 @@
>>> +* Qualcomm
Touchpads that have only one button are called clickpads and should
be advertised as such by the kernel.
Signed-off-by: Benjamin Tissoires
---
Hi,
this has been on my local tree for nearly a year now, but I never really
managed to take the time to make it working properly.
Jason raised the
On 06/03/15 04:13, Yun Wu wrote:
> The field of page size in register GITS_BASERn might be read-only
> if an implementation only supports a single, fixed page size. But
> currently the ITS driver will throw out an error when PAGE_SIZE
> is less than the minimum size supported by an ITS. So
Julia Lawall writes:
> On Fri, 6 Mar 2015, Jes Sorensen wrote:
>
>> Quentin Lambert writes:
>> > This patch reduces the kernel size by removing error messages that
>> > duplicate
>> > the normal OOM message.
>> >
>> > A simplified version of the semantic patch that finds this problem is as
>> >
On 03/05/2015 10:13 AM, Rob Herring wrote:
> On Wed, Mar 4, 2015 at 11:24 AM, Peter Hurley
> wrote:
>> The OF device name of the earlycon is never used because there is no
>> device; re-purpose the name field to store the earlycon name in
>> the OF earlycon table. Earlycon will use the table
On Mar 5, 2015, at 7:59 PM, Olof Johansson wrote:
> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala wrote:
>>
>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman wrote:
>>
>>> Kumar Gala writes:
>>>
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM
At Fri, 06 Mar 2015 16:59:00 +0100,
Maciej S. Szmigiero wrote:
>
> Patch to add an VT1613 AC97 codec support.
>
> This codec has additional DC offset removal control,
> headphone output and no video input.
>
> Signed-off-by: Maciej Szmigiero
Applied, thanks.
Takashi
>
> diff --git
On Wed, Mar 04, 2015 at 05:47:03PM -0800, Luis R. Rodriguez wrote:
> On Wed, Mar 4, 2015 at 6:36 AM, Andrey Ryabinin
> wrote:
> > On 03/03/2015 07:02 PM, Konrad Rzeszutek Wilk wrote:
> >> If it is like that - then just using what had to be implemented
> >> for the stack protection as a template
Patch to add an VT1613 AC97 codec support.
This codec has additional DC offset removal control,
headphone output and no video input.
Signed-off-by: Maciej Szmigiero
diff --git a/sound/pci/ac97/ac97_codec.c b/sound/pci/ac97/ac97_codec.c
index 5ee2f17..5bca1a3 100644
---
On 6 Mar 2015, ste...@agner.ch wrote:
> On 2015-03-06 07:15, Sascha Hauer wrote:
>> Hi Stefan,
>> On Thu, Mar 05, 2015 at 12:10:20AM +0100, Stefan Agner wrote:
>>> +
>>> +static int vf610_nfc_probe_dt(struct device *dev, struct
>>> vf610_nfc_config *cfg)
>>> +{
>>> + struct device_node *np =
On 03/06/2015 01:18 PM, Kirill A. Shutemov wrote:
> On Thu, Mar 05, 2015 at 01:55:15PM +0100, Jerome Marchand wrote:
>> On 03/04/2015 05:32 PM, Kirill A. Shutemov wrote:
>>> Hello everybody,
>>>
>>> It's bug-fix update of my thp refcounting work.
>>>
>>> The goal of patchset is to make refcounting
Remove extra space in MODULE_ALIAS.
Signed-off-by: Axel Lin
---
drivers/phy/phy-omap-control.c | 2 +-
drivers/phy/phy-omap-usb2.c| 2 +-
drivers/phy/phy-ti-pipe3.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/phy/phy-omap-control.c
On Fri, Mar 06, 2015 at 10:14:26AM -0500, Konrad Rzeszutek Wilk wrote:
> Would you be willing to fold in the description in the patch #4 and repost it?
>
> Andrew - are you OK picking it up or would you prefer me as the maintainer
> to feed it to Linus? [either option is fine with me]
AFAICS
On Tue, Mar 03, 2015 at 10:08:02PM +0800, Yaowei Bai wrote:
> As we have moved to 4.x, it should be reflected in README.
>
> Signed-off-by: Yaowei Bai
> ---
> README | 34 +-
> 1 file changed, 17 insertions(+), 17 deletions(-)
How about this more
On Thu, 5 Mar 2015, Serge E. Hallyn wrote:
> > > So I'd say drop this change ^
> >
> > Then the ambient caps get ignored for a executables that have capabilities
> > seton the file?
>
> Yes. Those are assumed to already know what they're doing.
Ok can we get this patch merged now if I do this
On 03/06/2015 09:45 AM, Sasha Levin wrote:
> On 03/06/2015 09:34 AM, Rafael David Tinoco wrote:
>> Are you sure about this ? I have a core dump locked on the same place
>> (state machine for powering cpu down for the task swap) from a 3.13 (+
>> upstream patches) and this commit wasn't backported
On 03/06/2015 10:13 AM, Murali Karicheri wrote:
On 03/06/2015 01:06 AM, Fengguang Wu wrote:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
commit 0b2af171520e5d5e7d5b5f479b90a6a5014d9df6
On Thu, 5 Mar 2015, Andy Lutomirski wrote:
> > Yes due to the library issues.
>
> You can't LD_PRELOAD and fP together. And I'm still unconvinced that
> ambient caps can ever be safe in conjunction with fP. I'll grill you
> next week on what you're trying to do that makes you want this :)
[Sorry for the late response]
This is basically the same code posted by KY Srinivasan posted late last
year (http://marc.info/?l=linux-mm=141782228129426=2). I had
objections to the implementation
http://marc.info/?l=linux-mm=141805109216700=2
On Thu 12-02-15 11:23:51, Vitaly Kuznetsov wrote:
>
When drivers didn't provide setup() method, SPI core should ensure
that CS line is driven in non-active state after spi_setup().
Signed-off-by: Ivan T. Ivanov
---
drivers/spi/spi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index c64a3e5..bfba2d9
Treat x32 ABI variants of execve[at] the same as x86_64
variants.
Slightly speculative as the audit subsystem doesn't currently
work with x32 ABI syscalls. If and when audit+x32 does work,
this should correctly classify exec calls.
Signed-off-by: David Drysdale
---
arch/x86/kernel/audit_64.c
To match different firmware file format, we replace original firmware file size
checking with the signature metadata comparison when update firmware, If failed,
the update will be aborted.
Signed-off-by: Duson Lin
---
drivers/input/mouse/elan_i2c.h |6 +++---
New execveat syscall from v3.19 is missing from
audit_classify_compat_syscall().
Reported-by: Brian Gerst
Signed-off-by: David Drysdale
---
lib/compat_audit.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/compat_audit.c b/lib/compat_audit.c
index 873f75b640ab..a49469f0511d 100644
Add a couple of missing execve variants to the syscall
classification code in the audit system.
- Patch 1 is potentially suitable for 3.19 stable.
- Patch 2 need not be back-applied, as audit doesn't yet work
with x32 syscalls in general.
David Drysdale (2):
audit: add execveat to syscall
On 03/05/2015 10:17 AM, Andrea Arcangeli wrote:
> Add documentation.
>
> Signed-off-by: Andrea Arcangeli
> ---
> Documentation/vm/userfaultfd.txt | 97
>
> 1 file changed, 97 insertions(+)
> create mode 100644 Documentation/vm/userfaultfd.txt
Just a
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching.git for-linus
to receive
- patch fixing a RCU unlock misplacement in live patching infrastructure,
from Peter Zijlstra
Thanks.
Peter
On 03/06, David Vrabel wrote:
>
> On 06/03/15 14:01, Oleg Nesterov wrote:
>
> > Not sure I understand it correctly after the first quick look, but
> >
> > 1. It conflicts with the recent changes in tip/x86/fpu
> >
> > 2. fpu_ini() initializes current->thread.fpu.state. This looks unneeded,
> >
I have business finance proposition for you. Reply for details
--
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 Fri 2015-03-06 08:54:23, Josh Poimboeuf wrote:
> On Fri, Mar 06, 2015 at 03:00:13PM +0100, Petr Mladek wrote:
> > This brings me back to the original idea with that boolean that
> > marks the state before and after the coming notifier (module_init).
> > We could use a bitfield instead of the
On Fri, 6 Mar 2015, Jes Sorensen wrote:
> Quentin Lambert writes:
> > This patch reduces the kernel size by removing error messages that duplicate
> > the normal OOM message.
> >
> > A simplified version of the semantic patch that finds this problem is as
> > follows:
The jz4780 and jz4740 have very similar i2s blocks.
The slight difference is in Rx/Tx fifos.
And the bitclocks for input/output are different.
This patch adds jz4780 support to the driver
Signed-off-by: Zubair Lutfullah Kakakhel
---
Patch based on 4.0-rc2
Tested on the MIPS Creator CI20.
---
Linus,
please pull sound fixes for v4.0-rc3 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.0-rc3
The topmost commit is 4fda87df09bee2b1bf236aba408c3236d4f1fbca
sound fixes for 4.0-rc3
In
Quentin Lambert writes:
> This patch reduces the kernel size by removing error messages that duplicate
> the normal OOM message.
>
> A simplified version of the semantic patch that finds this problem is as
> follows: (http://coccinelle.lip6.fr)
This patch removes useful warnings about what
Ensure that driver is owner of the GPIO's used for CS signals.
Signed-off-by: Ivan T. Ivanov
---
drivers/spi/spi-qup.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/spi-qup.c b/drivers/spi/spi-qup.c
index 2b2c359..a07ba46 100644
---
num-cs is 32 bit property, don't read just upper 16 bits.
Fixes: 4a8573abe965 "spi: qup: Remove chip select function"
Signed-off-by: Ivan T. Ivanov
---
drivers/spi/spi-qup.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/spi/spi-qup.c
BTW I am getting doubles of your messages, both addressed to the
mailings lists, but only one also addressed to me. You should just
send one copy, with everyone on CC.
Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Fri, Mar 06, 2015 at 10:50:08AM +, Stathis Voukelatos wrote:
> Although the PTP way appears to be the best from an architectural point
> of view, we have some questions as whether it is suitable for the audio
> use cases that this module is mainly intended for.
> To use the PTP terminology
. snip..
> Format: { ,force,,} is suitable I think.
> And fixing "force" is follow the code design previously in
> setup_io_tlb_npages.
It is a bug. It should have been smart enough to deal with the 'force' being
in any order.
If you are willing to make a patch to fix this - either folded
The omap_serial.txt binding documentation lacks a number of properties
that are used in DTS files for platforms incorporating this peripheral.
Fix this by documenting the missing required and optional fields and
add an example.
Signed-off-by: Matt Porter
---
Rework the clk_gate helpers to either use an iomem base address or a
regmap.
Signed-off-by: Antoine Tenart
---
drivers/clk/clk-gate.c | 94 +---
include/linux/clk-provider.h | 12 --
2 files changed, 80 insertions(+), 26 deletions(-)
diff --git
The Berlin clock documentation was part of the Marvell Berlin SoC
documentation because the Berlin clock configuration was inside the
chip controller. With the recent rework of the chip and system
controller handling (now all sub-devices of the soc and system
controller nodes are registred with
With the introduction of the Berlin mfd controller driver, all drivers
previously sharing the chip and system controller nodes now have their
own sub-node.
Signed-off-by: Antoine Tenart
---
arch/arm/boot/dts/berlin2q.dtsi | 53 ++---
1 file changed, 29
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-4.0-rc3
to receive power management and ACPI fixes for v4.0-rc1 with top-most
commit e178e7d6df38dab67f51df4282927c4c7392879f
Merge branches 'pm-domains' and 'pm-cpufreq'
on top of commit
On Thu, Mar 05, 2015 at 07:46:36PM +0300, Vladimir Davydov wrote:
> On Wed, Mar 04, 2015 at 04:22:30PM -0500, Konrad Rzeszutek Wilk wrote:
> > On Tue, Feb 24, 2015 at 01:34:06PM +0300, Vladimir Davydov wrote:
> > > On Mon, Feb 23, 2015 at 11:12:22AM -0500, Konrad Rzeszutek Wilk wrote:
> > > >
The commit 7572d3b29896 (lib/string_helpers.c: change semantics of
string_escape_mem) updates qword_add() to follow the changes in
lib/string_helpers.c. This patch simplifies the approach.
Signed-off-by: Andy Shevchenko
---
Andrew, I think this one can be folded in the mentioned commit by
Marvell Berlin SoCs have a chip control register set providing several
individual registers dealing with various controllers (pinctrl, reset,
clk). This chip controller is described by a single DT node since the
individual registers are spread among the chip control register bank.
Marvell Berlin
Now that the rework to have one sub-node per device in the chip and
system controllers is done, their dedicated compatible can be removed.
Signed-off-by: Antoine Tenart
---
arch/arm/boot/dts/berlin2q.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
With the introduction of the Berlin mfd controller driver, all drivers
previously sharing the chip and system controller nodes now have their
own sub-node.
Signed-off-by: Antoine Tenart
---
arch/arm/boot/dts/berlin2cd.dtsi | 39 ++-
1 file changed, 22
The Berlin clock driver was sharing a DT node with the pin controller
and the reset driver. All these device are now a sub-node of the chip
and system controllers and a regmap is available thanks to syscon to
access the registers safely.
Rework the Berlin clock driver to use the regmap provided
Now that the rework to have one sub-node per device in the chip and
system controllers is done, their dedicated compatible can be removed.
Signed-off-by: Antoine Tenart
---
arch/arm/boot/dts/berlin2cd.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Now that the rework to have one sub-node per device in the chip and
system controllers is done, their dedicated compatible can be removed.
Signed-off-by: Antoine Tenart
---
Documentation/devicetree/bindings/arm/marvell,berlin.txt | 16
1 file changed, 4 insertions(+), 12
On Fri, Mar 6, 2015 at 9:09 AM, Matt Porter wrote:
> The imx-pwm binding contains language indicating compatible
> strings to be used that is not valid for all supported parts
> e.g. Should be "fsl,-pwm". Fix this by enumerating the
> valid compatible strings that represent the two versions of
>
With the introduction of the Berlin mfd controller driver, all drivers
previously sharing the chip and system controller nodes now have their
own sub-node.
Signed-off-by: Antoine Tenart
---
arch/arm/boot/dts/berlin2.dtsi | 43 +++---
1 file changed, 24
On 03/06/2015 01:06 AM, Fengguang Wu wrote:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
commit 0b2af171520e5d5e7d5b5f479b90a6a5014d9df6
Author: Murali Karicheri
AuthorDate: Tue Mar 3
Before commit b3fd4f03ca0b995(locking/rwsem: Avoid deceiving lock
spinners), rwsem_spin_on_owner() returns false if the owner is changed.
This commit just returns true under the situation, then kernel
softlock can be triggered easily in xfstest.
So this patch recovers to previous behaviour, and
Now that the rework to have one sub-node per device in the chip and
system controllers is done, their dedicated compatible can be removed.
Signed-off-by: Antoine Tenart
---
arch/arm/boot/dts/berlin2.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On 3/6/15 2:12 AM, Peter Zijlstra wrote:
On Thu, Mar 05, 2015 at 09:05:28PM -0700, David Ahern wrote:
Socket(s): 32
NUMA node(s): 4
Urgh, with 32 'cpus' per socket, you still do _8_ sockets per node, for
a total of 256 cpus per node.
Per the response to Mike, the system
Rework the clk_mux helpers to either use an iomem base address or a
regmap.
Signed-off-by: Antoine Tenart
---
drivers/clk/clk-mux.c| 72 +---
include/linux/clk-provider.h | 39 +++-
2 files changed, 93 insertions(+), 18
On 3/6/15 2:07 AM, Peter Zijlstra wrote:
On Thu, Mar 05, 2015 at 09:05:28PM -0700, David Ahern wrote:
Since each domain is a superset of the lower one each pass through
load_balance regularly repeats the processing of the previous domain (e.g.,
NODE domain repeats the cpus in the CPU domain).
Hi,
Marvell Berlin SoCs have a chip control register set providing several
individual registers dealing with various controllers (pinctrl, reset,
clk). This chip controller is described by a single DT node since the
individual registers are spread among the chip control register bank.
Marvell
On Mon 02-03-15 17:18:14, Mike Kravetz wrote:
> On 03/02/2015 03:10 PM, Andrew Morton wrote:
> >On Fri, 27 Feb 2015 14:58:08 -0800 Mike Kravetz
> >wrote:
> >
> >>hugetlbfs allocates huge pages from the global pool as needed. Even if
> >>the global pool contains a sufficient number pages for the
The imx-pwm binding contains language indicating compatible
strings to be used that is not valid for all supported parts
e.g. Should be "fsl,-pwm". Fix this by enumerating the
valid compatible strings that represent the two versions of
this peripheral in use.
The binding is also missing the
Hi Emil,
On 03/05/15 10:04, Emil Medve wrote:
Hello Jamal,
On 03/05/2015 08:35 AM, Jamal Hadi Salim wrote:
Hi Emil,
No. All the kernel drivers/code we want to upstream is meant to stand on
its own and be used the "normal" Linux/Unix way
Ok, thanks - that was my only concern.
Note there
On 03/05/2015 09:28 PM, Rob Clark wrote:
> On Thu, Mar 5, 2015 at 8:59 PM, Olof Johansson wrote:
>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala wrote:
>>>
>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman wrote:
>>>
Kumar Gala writes:
> The top level qcom,msm-id and qcom,board-id are
Hello Inki,
On 03/06/2015 02:32 PM, Inki Dae wrote:
>>
>> Another interesting data point is that the error in next-20150303 for
>> these 2 boards was the NULL pointer dereference in exynos_plane_destroy
>> that I got with 4.0-rc2 (when IOMMU is disabled) in Snow and Peach Pit.
>
> I think the
The chip and system controller nodes handle sub-devices, such as the
clock, pinctrl or reset controllers. The drivers handling them need a
regmap provided by syscon. Select it by default when using a Berlin SoC.
Signed-off-by: Antoine Tenart
---
arch/arm/mach-berlin/Kconfig | 1 +
1 file
The Berlin pinctrl documentation was part of the Marvell Berlin SoC
documentation because the Berlin pinctrl configuration was inside the
chip and the system controllers. With the recent rework of the chip and
system controller handling (now an MFD driver registers all sub-devices
of the two soc
The chip and system controller nodes are now handled by the Berlin
controller mfd driver. Its sub-devices are then registered by the mfd
driver and let the drivers be probed properly, using their own
sub-nodes.
Rework the device tree to take this changes into account.
Signed-off-by: Antoine
The chip and system controller nodes are now handled by the Berlin
controller mfd driver. Its sub-devices are then registered by the mfd
driver and let the drivers be probed properly, using their own
sub-nodes.
Rework the device tree to take this changes into account.
Signed-off-by: Antoine
The Berlin pin controller nodes are now sub-nodes of the soc-controller
and the system-controller nodes. The register bank is managed by syscon,
which provides a regmap.
Remove the regmap setup from the Berlin pinctrl driver and use the one
provided by syscon.
Signed-off-by: Antoine Tenart
---
The Berlin reset documentation was part of the Marvell Berlin SoC
documentation because the Berlin reset configuration was inside the chip
controller. With the recent rework of the chip and system controller
handling (now an MFD driver registers all sub-devices of the two soc and
system controller
The Berlin pin-controller driver was sharing the chip and system
controller nodes with the clock and the reset drivers. They all shared
the same compatible. With the introduction of the Marvell Berlin MFD
controller, the Berlin pin-controller driver has now its own node.
Update its compatibles to
The Berlin reset controller was introduced without being a platform
driver because of a needed DT rework: the node describing the reset
controller also describes the pinctrl and clk controllers...
The DT issue being solved thanks to the addition of the Berlin
controller mfd driver, it is now
The chip and system controller nodes are now handled by the Berlin
controller mfd driver. Its sub-devices are then registered by the mfd
driver and let the drivers be probed properly, using their own
sub-nodes.
Rework the device tree to take this changes into account.
Signed-off-by: Antoine
We're moving from a single node for multiple devices to a node with one
sub-node per sub-device, registered by simple-mfd. Update the
documentation to reflect the changes.
Signed-off-by: Antoine Tenart
---
.../devicetree/bindings/arm/marvell,berlin.txt | 26 +-
1 file
On 3/6/15 1:51 AM, Peter Zijlstra wrote:
On Thu, Mar 05, 2015 at 09:05:28PM -0700, David Ahern wrote:
Hi Peter/Mike/Ingo:
Does that make sense or am I off in the weeds?
How much of your story pertains to 3.18? I'm not particularly interested
in anything much older than that.
No. All of
On 3/5/15 9:52 PM, Mike Galbraith wrote:
CPU970 attaching sched-domain:
domain 0: span 968-975 level SIBLING
groups: 8 single CPU groups
domain 1: span 968-975 level MC
groups: 1 group with 8 cpus
domain 2: span 768-1023 level CPU
groups: 4 groups with 256 cpus per
On Fri, 06 Mar 2015 15:18:42 +1100
Benjamin Herrenschmidt wrote:
> Can you shoot me the DT (/proc/device-tree in a tarball) ?
Attached.
-- Steve
device-tree.tar.bz2
Description: application/bzip
On 06/03/15 14:01, Oleg Nesterov wrote:
> On 03/06, Ingo Molnar wrote:
>>
>> * Oleg Nesterov wrote:
>>
>>> On 03/06, Ingo Molnar wrote:
* Oleg Nesterov wrote:
> [...] The patch above looks "obviously safe", but perhaps I am
> paranoid too much...
IMHO your hack
The commit 7572d3b29896 (lib/string_helpers.c: change semantics of
string_escape_mem) updates qword_add() to follow the changes in
lib/string_helpers.c. This patch simplifies the approach.
Andrew, I think this one can be folded in the mentioned commit by Rasmus.
Signed-off-by: Andy Shevchenko
On Fri, Mar 06, 2015 at 03:00:13PM +0100, Petr Mladek wrote:
> This brings me back to the original idea with that boolean that
> marks the state before and after the coming notifier (module_init).
> We could use a bitfield instead of the two booleans when requested.
Yeah, that would work. Though
Hello.
On 3/6/2015 1:48 PM, yong...@mediatek.com wrote:
From: Yong Wu
This patch add smi binding document.
Signed-off-by: Yong Wu
---
.../devicetree/bindings/soc/mediatek/mediatek,smi.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644
On Fri, Mar 06, 2015 at 11:41:57AM +, Kweh, Hock Leong wrote:
> # cat /any/path/capsule.bin > /sys/devices/platform/efi_capsule/capsule_load
This is straight-forward and clean.
> or doing:
> # echo "/any/path/capsule.bin" >
> /sys/devices/platform/efi_capsule/capsule_load
This is strange
On 03/06/2015 09:34 AM, Rafael David Tinoco wrote:
> Are you sure about this ? I have a core dump locked on the same place
> (state machine for powering cpu down for the task swap) from a 3.13 (+
> upstream patches) and this commit wasn't backported yet.
bisect took me to that same commit twice,
On Fri, Mar 06, 2015 at 08:37:26PM +0900, Masami Hiramatsu wrote:
> Actually, we can suppose this module unloading context is
> not changing universe. thus it is expected behavior, isn't it?
In the case of my proposed consistency model RFC, if the module
unloading task gets preempted, or if
On 03/06/15 06:39, Steve Capper wrote:
On 17 February 2015 at 23:11, David Long wrote:
From: Sandeepa Prabhu
Kprobes needs simulation of instructions that cannot be stepped
from different memory location, e.g.: those instructions
that uses PC-relative addressing. In simulation, the behaviour
401 - 500 of 1860 matches
Mail list logo
