Hello Rob,
On 04/04/2017 12:54 PM, Rob Herring wrote:
> On Tue, Apr 4, 2017 at 10:30 AM, Javier Martinez Canillas
> wrote:
>> There are Device Tree source files defining a device node for the
>> retu/tahvo I2C chip, but there isn't a DT binding document for it.
>>
>> Signed-off-by: Javier Martine
On imx6qp-sabresd LDO_ARM is connected to a different PMIC output than
the other imx6qdl-sabresd boards.
Setting cpu0 arm-supply to sw2_reg is wrong, this must have mistakenly
slipped out of the vendor tree where this is are used for LDO bypass.
Signed-off-by: Leonard Crestez
Reviewed-by: Lucas
From: Irina Tirdea
If there are any errors in getting the cpu0 regulators, the driver returns
-ENOENT. In case the regulators are not yet available, the devm_regulator_get
calls will return -EPROBE_DEFER, so that the driver can be probed later.
If we return -ENOENT, the driver will fail its initi
Setting the LDO regulator parent is optional but beneficial. It will cause
the PMIC output voltage to be dynamically set to the minimum input for the
LDOs, this should be more efficient.
This propagation was introduced by:
commit fc42112c0eaa ("regulator: core: Propagate voltage changes to supply
From: Colin King
Date: Mon, 3 Apr 2017 11:19:10 +0100
> From: Colin Ian King
>
> Trival fix, rename HW_INTERRUT_ASSERT_SET_* to HW_INTERRUPT_ASSERT_SET_*
>
> Signed-off-by: Colin Ian King
Applied.
On Tue, 2017-04-04 at 11:51 +0200, Lucas Stach wrote:
> Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> >
> > If the cpufreq driver tries to modify voltage/freq during suspend/resume
> > it might need to control an external PMIC via I2C or SPI but those
> > devices might be alre
Setting the supply is optional but beneficial, it will cause PMIC
voltages to be dynamically changed with cpu frequency.
Signed-off-by: Leonard Crestez
Reviewed-by: Lucas Stach
---
arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/
If the cpufreq driver tries to modify voltage/freq during suspend/resume
it might need to control an external PMIC via I2C or SPI but those
devices might be already suspended. This issue is likely to happen
whenever the LDOs have their vin-supply set.
To avoid this scenario we just increase cpufre
On Tue, Apr 04, 2017 at 03:06:17PM +0200, Martin Kepplinger wrote:
> sparse says:
>
> sur40.c:372:40: warning: restricted __le32 degrades to integer
>
> the header's data is __le32 so we need to convert it before comparing.
>
> Signed-off-by: Martin Kepplinger
Applied, thank you.
> ---
> d
Hi Masaki,
Yes, I think I have a 044E:120C. Is there a way to find out for sure?
It's not listed by e.g. lspci.
The touchpad is definitely not reacting to anything. evemu-record does
not show any events either.
I have attached the dmesg output.
Best,
-Nikolaus
On Apr 04 2017, Masaki Ota wrot
On Tue, Apr 4, 2017 at 7:59 PM, Tom Zanussi wrote:
> On Tue, 2017-04-04 at 00:05 +0300, Andy Shevchenko wrote:
> Yes, in a previous project, I had been working toward getting a < 1M
> system to boot on Galileo hardware (which it did, but using more than
> that - the Galileo2 has 256MB, but it was
On Tue, Apr 04, 2017 at 12:25:46PM -0400, Jeff Layton wrote:
> That said, I think giving more specific errors where we can is useful.
> When your program is erroring out and writing 'I/O error' to the logs,
> then how much time will your admins burn before they figure out that it
> really failed be
On Tue, Apr 04, 2017 at 07:33:30PM +0300, Andy Shevchenko wrote:
> On Tue, Apr 4, 2017 at 7:31 PM, Darren Hart wrote:
> > On Tue, Apr 04, 2017 at 07:08:28PM +0300, Andy Shevchenko wrote:
> >> On Tue, Apr 4, 2017 at 7:05 PM, Darren Hart wrote:
> >> > On Tue, Apr 04, 2017 at 04:45:05PM +0300, Andy
On Tue, Apr 04, 2017 at 06:29:06PM +0200, Paul Menzel wrote:
> Unfortunately, there seems to have been a regression between Linux 3.16
> and 4.8 and 4.9, so that the Linux kernel doesn’t create the TPM
> device.
That old kernel did not check error codes when reading burst count,
the new one does
Sukadev Bhattiprolu [sukadevatlinux.vnet.ibm.com] wrote:
> Define macros for the VAS hardware registers and bit-fields as well
> as couple of data structures needed by the VAS driver.
>
> Signed-off-by: Sukadev Bhattiprolu
> +++ b/arch/powerpc/platforms/powernv/vas.h
> @@ -0,0 +1,387 @@
> +/*
Some minor erratum may not be fixed in further revisions of a core,
leading to a situation where the workaround needs to be updated each
time an updated core is released.
Introduce a MIDR_ALL_VERSIONS match helper that will work for all
versions of that MIDR, once and for all.
Acked-by: Mark Rutl
In order to work around Cortex-A73 erratum 858921 in a subsequent
patch, add the required capability that advertise the erratum.
As the configuration option it depends on is not present yet,
this has no immediate effect.
Acked-by: Daniel Lezcano
Signed-off-by: Marc Zyngier
---
Documentation/ar
It has recently become obvious that a number of arm64 systems have
been blessed with a set of timers that are slightly less than perfect,
and require a bit of hand-holding. We already have a bunch of
errata-specific code to deal with this, but as we're adding more
potential detection methods (DT, A
On Tue, 4 Apr 2017 16:21:20 +0530 George Cherian
wrote:
>
> Hi Alexey,
>
> On 04/03/2017 11:07 PM, Alexey Klimov wrote:
> > (adding Prashanth to c/c)
> >
> > Hi George,
> >
> > On Fri, Mar 31, 2017 at 06:24:02AM +, George Cherian wrote:
> >> Based on Section 14.1 of ACPI specification, it is
We're currently stuck with DT when it comes to handling errata, which
is pretty restrictive. In order to make things more flexible, let's
introduce an infrastructure that could support alternative discovery
methods. No change in functionality.
Reviewed-by: Hanjun Guo
Signed-off-by: Marc Zyngier
Just as we're able to identify a broken platform using some DT
information, let's enable a way to spot the offenders with ACPI.
The difference is that we can only match on some OEM info instead
of implementation-specific properties. So in order to avoid the
insane multiplication of errata structur
Userspace being allowed to use read CNTVCT_EL0 anytime (and not
only in the VDSO), we need to enable trapping whenever a cntvct
workaround is enabled on a given CPU.
Signed-off-by: Marc Zyngier
---
drivers/clocksource/arm_arch_timer.c | 45 +---
1 file changed, 32
Since people seem to make a point in breaking the userspace visible
counter, we have no choice but to trap the access. Add the required
handler.
Acked-by: Mark Rutland
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/esr.h | 2 ++
arch/arm64/kernel/traps.c| 14 ++
2 files
Instead of applying a CPU-specific workaround to all CPUs in the system,
allow it to only affect a subset of them (typical big-little case).
This is done by turning the erratum pointer into a per-CPU variable.
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/arch_timer.h | 31 +++
In order to deal with ACPI enabled platforms suffering from the
HISILICON_ERRATUM_161010101, let's add the required OEM data that
allow the workaround to be enabled.
Tested-by: dann frazier
Tested-by: Hanjun Guo
Reviewed-by: Hanjun Guo
Signed-off-by: Marc Zyngier
---
drivers/clocksource/arm_a
The I2C core always reports a MODALIAS of the form i2c: even if the
device was registered via OF, this means that exporting the OF device ID
table device aliases in the module is not needed. But in order to change
how the core reports modaliases to user-space, it's better to export it.
While there
As we're about to allow per CPU cntkctl_el1 configuration, we cannot
rely on the register value to be common when performing power
management.
Let's turn saved_cntkctl into a per-cpu variable.
Signed-off-by: Marc Zyngier
---
drivers/clocksource/arm_arch_timer.c | 6 +++---
1 file changed, 3 ins
Cortex-A73 (all versions) counter read can return a wrong value
when the counter crosses a 32bit boundary.
The workaround involves performing the read twice, and to return
one or the other depending on whether a transition has taken place.
Signed-off-by: Marc Zyngier
---
drivers/clocksource/Kco
Sukadev Bhattiprolu [sukadevatlinux.vnet.ibm.com] wrote:
> Implement vas_init() and vas_exit() functions for a new VAS module.
> This VAS module is essentially a library for other device drivers
> and kernel users of the NX coprocessors like NX-842 and NX-GZIP.
> In the future this will be extended
As we're about to move things around, let's start with the low
level read/write functions. This allows us to use these functions
in the errata handling code without having to use forward declaration
of static functions.
Acked-by: Mark Rutland
Acked-by: Daniel Lezcano
Signed-off-by: Marc Zyngier
In order to access clocksource_counter from the errata handling code,
move it (together with the related structures and functions) towards
the top of the file.
Signed-off-by: Marc Zyngier
---
drivers/clocksource/arm_arch_timer.c | 62 ++--
1 file changed, 31 inser
The way we work around errata affecting set_next_event is not very
nice, at it imposes this workaround on errata that do not need it.
Add new workaround hooks and let the existing workarounds use them.
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/arch_timer.h | 4
drivers/clock
On 04/04/17 04:59 AM, Sagi Grimberg wrote:
> We can never ever get here from an IO command, and that is a good thing
> because it would have been broken if we did, regardless of what copy
> method we use...
Yes, I changed this mostly for admin commands. I did notice connect
commands do end up re
Not all errata need to workaround all access types. Allow them to
be optional.
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/arch_timer.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/include/asm/arch_timer.h
b/arch/arm64/include/asm/arch_timer.h
i
Let's move the handling of workarounds affecting set_next_event
to the affected function, instead of overriding the pointers
as an afterthough. Yes, this is an extra indirection on the
erratum handling path, but the HW is busted anyway.
This will allow for some more flexibility later.
Signed-off-
Should we ever have a workaround for an erratum that is detected using
a capability and affecting a particular CPU, it'd be nice to have
a way to probe them directly.
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/arch_timer.h | 1 +
drivers/clocksource/arm_arch_timer.c | 28 ++
this_cpu_has_cap() only checks the feature array, and not the errata
one. In order to be able to check for a CPU-local erratum, allow it
to inspect the latter as well.
This is consistent with cpus_have_cap()'s behaviour, which includes
errata already.
Acked-by: Daniel Lezcano
Reviewed-by: Suzuki
As we're about to introduce a new workaround that is specific to
Cortex-A73, let's define the coresponding MIDR.
Acked-by: Mark Rutland
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/cputype.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/include/asm/cputype.h b/arch/
From: Yazen Ghannam
We have support for the new SMCA MCA_DE{STAT,ADDR} registers in Linux. So
we've used these registers in place of MCA_{STATUS,ADDR} on SMCA systems.
However, the guidance for current implementations of SMCA is to continue
using MCA_{STATUS,ADDR} and to use MCA_DE{STAT,ADDR} onl
From: Yazen Ghannam
Scalable MCA systems have a new MCA_CONFIG register that we use to
configure each bank. We currently use this when we set up thresholding.
However, this is logically separate.
Group all SMCA-related initialization into a single, separate function.
This includes setting MCA_CO
It looks like arm-charlcd.c belongs to auxdisplay subsystem.
Move it to drivers/auxdisplay folder.
No functional changes intended.
Reviewed-by: Linus Walleij
Signed-off-by: Andy Shevchenko
---
drivers/auxdisplay/Kconfig | 10 ++
drivers/auxdisplay/Makefile
Hi All,
The production board I'm using doesn't have a JTAG available,
upgrading to 4.8 from 4.1,.and need to understand why Linux 4.8.3
doesn't boot on a x86_64 corei7-64. Boots with no issues with 4.1.
Hangs at the last message of u-boot, the typical "Starting kernel."
The bootcmd and arguments
On 04/04/17 04:46 AM, Sagi Grimberg wrote:
>
>> +p2pmem_debugfs_root = debugfs_create_dir("p2pmem", NULL);
>> +if (!p2pmem_debugfs_root)
>> +pr_info("could not create debugfs entry, continuing\n");
>> +
>
> Why continue? I think it'd be better to just fail it.
Yup, agreed. This
It looks like panel.c belongs to auxdisplay subsystem.
Move it to drivers/auxdisplay folder.
No functional changes intended.
Acked-by: Geert Uytterhoeven
Signed-off-by: Andy Shevchenko
---
drivers/auxdisplay/Kconfig | 280 +++
drivers/auxdisplay/Makefi
From: Vinícius Tinti
Add rules to kbuild in order to generate LLVM bitcode files with the .ll
extension when using clang.
# from c code
CC=clang make kernel/pid.ll
# from asm code
CC=clang make arch/x86/kernel/preempt.ll
From: Vinícius Tinti
Signed-off-by: Vinícius Tinti
Signed-off-b
When performing load balancing, numabalancing only looks at
task->cpus_allowed to see if the task can run on the target cpu. If
isolcpus kernel parameter is set, then isolated cpus will not be part of
mask task->cpus_allowed.
For example: (On a Power 8 box running in smt 1 mode)
isolcpus=56,64,72
On Tue, Apr 4, 2017 at 9:28 PM, Andrey Konovalov wrote:
> Hi,
>
> I've got the following error report while fuzzing the kernel with syzkaller.
>
> On commit a71c9a1c779f2499fb2afc0553e543f18aff6edf (4.11-rc5).
>
> A reproducer and .config are attached.
The script is pretty hard to reproduce the is
On Tue, Apr 04, 2017 at 07:11:17PM +0300, Andy Shevchenko wrote:
> On Wed, 2017-03-29 at 18:04 +0300, Andy Shevchenko wrote:
> > On Wed, 2017-03-29 at 00:12 -0700, Dmitry Torokhov wrote:
> > > On Tue, Mar 28, 2017 at 07:39:23PM +0300, Andy Shevchenko wrote:
> > > > On Thu, 2017-03-23 at 13:28 -0700
From: Kalle Valo
Date: Mon, 03 Apr 2017 14:26:10 +0300
> here few really small fixes. I'm hoping this to be the last pull request
> for 4.11.
>
> Please let me if there are any problems.
Pulled, thanks.
But I will warn you, you say fixes, but your Subject line and
GIT tag says "-next" so I pul
On 3/30/17 3:50 PM, Benjamin Herrenschmidt wrote:
On Thu, 2017-03-30 at 13:15 -0500, Christopher Bostic wrote:
+static void serial_in(struct fsi_master_gpio *master, struct fsi_gpio_msg *msg,
+ uint8_t num_bits)
+{
+ uint8_t bit, in_bit;
+
+ set_sda_input(mast
From: Tony Lindgren
Date: Tue, 4 Apr 2017 09:01:06 -0700
> You may need to resend the davinci_mdio.c patch alone
> for Dave as he usually won't pick individual patches I
> think.
Correct.
Hi,
On Tue, Apr 04, 2017 at 11:30:28AM -0400, Javier Martinez Canillas wrote:
> This series add OF device ID tables to mfd I2C drivers whose devices are
> either used in Device Tree source files or are listed in binding docs as
> a compatible string.
For patches 1-5 you can add:
Acked-by: Aaro K
On 2017-03-28 19:23, Ard Biesheuvel wrote:
> On 28 March 2017 at 18:17, Ard Biesheuvel wrote:
>> On 28 March 2017 at 17:18, Jan Kiszka wrote:
>>> On 2017-03-28 17:52, Ard Biesheuvel wrote:
On 28 March 2017 at 16:43, Jan Kiszka wrote:
> On 2017-03-28 17:13, Jan Kiszka wrote:
>> On 20
On Tue, 2017-04-04 at 18:30 +0300, Michael S. Tsirkin wrote:
> I couldn't reproduce it - let's make sure we are using the
> same tree. Could you pls try
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
>
> It's currently at cc79d42a7d7e57ff64f406a1fd3740afebac0b44
Thi
On Wed, Mar 29, 2017 at 03:45:01PM +0530, Arushi Singhal wrote:
> Replace explicit NULL comparison with ! operator to simplify code.
>
> Signed-off-by: Arushi Singhal
> ---
> net/netfilter/ipvs/ip_vs_ctl.c | 8 ++---
> net/netfilter/ipvs/ip_vs_proto.c | 8 ++---
I count 18 instan
* Javier Martinez Canillas [170404 08:33]:
> Most patches can be applied independently, with the exception of patches
> 2 to 4 that should be applied in the same tree to keep bisect-ability.
Probably best to merge this all via MFD or i2c:
Acked-by: Tony Lindgren
Dear Jason,
Thank you for your reply.
On 2017-04-04 19:15, Jason Gunthorpe wrote:
On Tue, Apr 04, 2017 at 06:29:06PM +0200, Paul Menzel wrote:
Unfortunately, there seems to have been a regression between Linux
3.16
and 4.8 and 4.9, so that the Linux kernel doesn’t create the TPM
device.
Hello Tony,
On 04/04/2017 01:43 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas [170404 08:33]:
>> Most patches can be applied independently, with the exception of patches
>> 2 to 4 that should be applied in the same tree to keep bisect-ability.
>
> Probably best to merge this all via MFD
Implement specific usage of verify_pre_usermode_state for user-mode
returns for x86.
Signed-off-by: Thomas Garnier
---
Based on next-20170404
---
arch/x86/Kconfig| 1 +
arch/x86/entry/common.c | 3 +++
arch/x86/entry/entry_64.S | 8
Implement specific usage of verify_pre_usermode_state for user-mode
returns for arm64.
Signed-off-by: Thomas Garnier
---
Based on next-20170404
---
arch/arm64/Kconfig| 1 +
arch/arm64/kernel/entry.S | 15 +++
2 files changed, 16 insertions(+)
diff --git a/arch/arm64
CONFIG_ARCH_NO_SYSCALL_VERIFY_PRE_USERMODE_STATE option is also
added so each architecture can optimize this change.
Signed-off-by: Thomas Garnier
Tested-by: Kees Cook
---
Based on next-20170404
---
arch/s390/Kconfig| 1 +
include/linux/syscalls.h | 26 +-
init/Kconfig
On Tue, Mar 28, 2017 at 06:56:48PM +0530, Arushi Singhal wrote:
> Rmoved parentheses on the right hand side of assignment, as they are
> not required. The following coccinelle script was used to fix this
> issue:
>
> @@
> local idexpression id;
> expression e;
> @@
>
> id =
> -(
> e
> -)
>
> Sig
Implement specific usage of verify_pre_usermode_state for user-mode
returns for arm.
Signed-off-by: Thomas Garnier
---
Based on next-20170404
---
arch/arm/Kconfig | 1 +
arch/arm/kernel/entry-common.S | 16 +++-
2 files changed, 16 insertions(+), 1 deletion(-)
diff
David Miller writes:
> From: Kalle Valo
> Date: Mon, 03 Apr 2017 14:26:10 +0300
>
>> here few really small fixes. I'm hoping this to be the last pull request
>> for 4.11.
>>
>> Please let me if there are any problems.
>
> Pulled, thanks.
>
> But I will warn you, you say fixes, but your Subject
From: Carlo Caione
The latest USB keyboards shipped on several ASUS laptop models
(including ROG laptop models such as GL702VMK) have the keyboards
backlight controlled by the keyboard firmware.
The firmware implements at least 3 different commands:
- Init command (to use when the system starts)
On Tue, Apr 04, 2017 at 10:25:46AM -0700, Tracy Smith, CEO wrote:
> Hi All,
>
> The production board I'm using doesn't have a JTAG available,
> upgrading to 4.8 from 4.1,.and need to understand why Linux 4.8.3
> doesn't boot on a x86_64 corei7-64. Boots with no issues with 4.1.
>
> Hangs at the l
From: Kan Liang
Spurious NMIs will be observed when applying the following command.
while true ; do sudo perf record -b -a -e
"cpu/umask=0x01,event=0xcd,ldlat=0x80/pp,cpu/umask=0x03,event=0x0/,
cpu/umask=0x02,event=0x0/,cycles,branches,cache-misses,
cache-references" -- sleep 10 ; d
On Tue, Apr 04, 2017 at 10:34:14PM +1000, Dave Chinner wrote:
> On Mon, Apr 03, 2017 at 04:00:55PM +0200, Jan Kara wrote:
> > What filesystems can or cannot easily do obviously differs. Ext4 has a
> > recovery flag set in superblock on RW mount/remount and cleared on
> > umount/RO remount.
>
> Eve
On Tue, 2017-04-04 at 19:40 +0200, Mike Galbraith wrote:
> On Tue, 2017-04-04 at 18:30 +0300, Michael S. Tsirkin wrote:
>
> > I couldn't reproduce it - let's make sure we are using the
> > same tree. Could you pls try
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux
> > -
On Tue, Apr 04, 2017 at 01:41:11PM -0400, Simon Horman wrote:
> On Wed, Mar 29, 2017 at 03:45:01PM +0530, Arushi Singhal wrote:
> > Replace explicit NULL comparison with ! operator to simplify code.
> >
> > Signed-off-by: Arushi Singhal
> > ---
> > net/netfilter/ipvs/ip_vs_ctl.c | 8 ++-
From: Thor Thayer
The peripherals EDACs only exist on the Arria10 SoCFPGA. The Cyclone5
initialization has EDAC warnings when the peripherals aren't found
in the device tree. Fix by checking for Arria10 in the init functions.
Signed-off-by: Thor Thayer
---
v2 Change valid_model() return value
On Tue, 2017-04-04 at 20:08 +0300, Andy Shevchenko wrote:
> On Tue, Apr 4, 2017 at 7:59 PM, Tom Zanussi
> wrote:
> > On Tue, 2017-04-04 at 00:05 +0300, Andy Shevchenko wrote:
>
> > Yes, in a previous project, I had been working toward getting a < 1M
> > system to boot on Galileo hardware (which
On Tue, 2017-04-04 at 10:31 -0700, Dmitry Torokhov wrote:
> On Tue, Apr 04, 2017 at 07:11:17PM +0300, Andy Shevchenko wrote:
> > On Wed, 2017-03-29 at 18:04 +0300, Andy Shevchenko wrote:
> > > On Wed, 2017-03-29 at 00:12 -0700, Dmitry Torokhov wrote:
> > > > On Tue, Mar 28, 2017 at 07:39:23PM +0300
On Wed, Mar 29, 2017 at 03:25:17AM +0530, simran singhal wrote:
> For string without format specifiers, use seq_puts(). For
> seq_printf("\n"), use seq_putc('\n').
>
> Signed-off-by: simran singhal
> ---
> net/netfilter/ipvs/ip_vs_ctl.c | 8
Simran, I would be happy to pick up
On Tue, Apr 04, 2017 at 07:54:36PM +0200, Mike Galbraith wrote:
> On Tue, 2017-04-04 at 19:40 +0200, Mike Galbraith wrote:
> > On Tue, 2017-04-04 at 18:30 +0300, Michael S. Tsirkin wrote:
> >
> > > I couldn't reproduce it - let's make sure we are using the
> > > same tree. Could you pls try
> > >
On Mon, 3 Apr 2017 15:06:13 -0400
Luiz Capitulino wrote:
> On Mon, 3 Apr 2017 17:23:17 +0200
> Frederic Weisbecker wrote:
>
> > Do you observe aligned ticks with trace events (hrtimer_expire_entry)?
> >
> > You might want to enforce the global clock to trace that:
> >
> > echo "global" >
Allwinner A64 have a RSB controller like the one on A23/A33 SoCs.
Add it and its pinmux.
Signed-off-by: Icenowy Zheng
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
b/arc
The Pine64 (including Pine64+) boards have an AXP803 PMIC, which is a PMIC
similar to AXP288, but tweaked to use with Allwinner SoCs rather than Intel
tablets (with DCIN and Vbus re-splitted like other AXP PMICs, and RSB bus
support added).
This patchset adds support for it and enabled it in Pine6
Allwinner A64 SoC features a NMI controller, which is usually connected
to the AXP PMIC.
Add support for it.
Signed-off-by: Icenowy Zheng
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
On Tue, Apr 4, 2017 at 8:59 PM, Tom Zanussi wrote:
> On Tue, 2017-04-04 at 20:08 +0300, Andy Shevchenko wrote:
>> On Tue, Apr 4, 2017 at 7:59 PM, Tom Zanussi
>> wrote:
>> > On Tue, 2017-04-04 at 00:05 +0300, Andy Shevchenko wrote:
>> > I was focused at that point mainly on the kernel static siz
On Tue, Apr 04, 2017 at 10:54:06AM -0700, Fenghua Yu wrote:
> On Tue, Apr 04, 2017 at 10:25:46AM -0700, Tracy Smith, CEO wrote:
> > Hi All,
> >
> > The production board I'm using doesn't have a JTAG available,
> > upgrading to 4.8 from 4.1,.and need to understand why Linux 4.8.3
> > doesn't boot o
AXP803 is a PMIC produced by Shenzhen X-Powers, with either I2C or RSB
bus.
Add a compatible for it.
Signed-off-by: Icenowy Zheng
---
Documentation/devicetree/bindings/mfd/axp20x.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/axp2
AXP803 is a new PMIC chip produced by X-Powers, usually paired with A64
via RSB bus. The PMIC itself is like AXP288, but with RSB support and
dedicated VBUS and ACIN.
Add support for it in the axp20x mfd driver.
Currently only power key function is supported.
Signed-off-by: Icenowy Zheng
---
d
The Pine64 (including Pine64+) boards have an AXP803 as its main PMIC.
Add its device node.
Signed-off-by: Icenowy Zheng
---
arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts
AXP803 have the most regulators in currently supported AXP PMICs.
Add info for the regulators in the dt-bindings document.
Signed-off-by: Icenowy Zheng
---
Documentation/devicetree/bindings/mfd/axp20x.txt | 27
1 file changed, 27 insertions(+)
diff --git a/Documentatio
AXP803 PMIC also have a series of regulators (DCDCs and LDOs)
controllable via I2C/RSB bus.
Add support for them.
Signed-off-by: Icenowy Zheng
---
drivers/regulator/axp20x-regulator.c | 135 +++
include/linux/mfd/axp20x.h | 37 ++
2 files chang
As axp20x-regulator now supports AXP803, add a cell for it.
Signed-off-by: Icenowy Zheng
---
drivers/mfd/axp20x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index e468e08d84db..9065be056b39 100644
--- a/drivers/mfd/axp20x.c
+++ b/drivers/mfd
As nearly all A64 boards are using AXP803 PMIC, add a DTSI file for it,
like the old DTSI files for AXP20x/22x, for the common parts of the
PMIC.
Signed-off-by: Icenowy Zheng
---
arch/arm64/boot/dts/allwinner/axp803.dtsi | 150 ++
1 file changed, 150 insertions(+)
cr
The Wi-Fi modules of Pine64 is powered via DLDO4 and ELDO1 (the latter
one provides I/O voltage).
Add device node for it.
Signed-off-by: Icenowy Zheng
---
arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dt
Add support of AXP803 regulators in the Pine64 device tree, in order to
enable many future functionalities, e.g. Wi-Fi.
Signed-off-by: Icenowy Zheng
---
.../arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 109 +
1 file changed, 109 insertions(+)
diff --git a/arch/arm64/boot
From: Mark Charlebois
cmd in COMPATIBLE_IOCTL is always a u32, so cast it so there isn't a
warning about an overflow in XFORM.
From: Mark Charlebois
Signed-off-by: Mark Charlebois
Signed-off-by: Behan Webster
Signed-off-by: Matthias Kaehlcke
Acked-by: Arnd Bergmann
---
Resending https://pat
On Tue, 2017-04-04 at 10:09 -0700, Matthew Wilcox wrote:
> On Tue, Apr 04, 2017 at 12:25:46PM -0400, Jeff Layton wrote:
> > That said, I think giving more specific errors where we can is useful.
> > When your program is erroring out and writing 'I/O error' to the logs,
> > then how much time will y
On Tue, Apr 04, 2017 at 08:59:11PM +0300, Andy Shevchenko wrote:
> On Tue, 2017-04-04 at 10:31 -0700, Dmitry Torokhov wrote:
> > On Tue, Apr 04, 2017 at 07:11:17PM +0300, Andy Shevchenko wrote:
> > > On Wed, 2017-03-29 at 18:04 +0300, Andy Shevchenko wrote:
> > > > On Wed, 2017-03-29 at 00:12 -0700
On 04/04/2017 11:34 AM, Marc Kleine-Budde wrote:
> On 03/24/2017 06:20 PM, Akshay Bhat wrote:
>> Hi Marc,
>>
>> On 03/17/2017 05:10 PM, Akshay Bhat wrote:
>>> This patch adds support for the Holt HI-311x CAN controller. The HI311x
>>> CAN controller is capable of transmitting and receiving standa
On Tue, Apr 4, 2017 at 10:52 AM, wrote:
> From: Kan Liang
>
> Spurious NMIs will be observed when applying the following command.
>while true ; do sudo perf record -b -a -e
>"cpu/umask=0x01,event=0xcd,ldlat=0x80/pp,cpu/umask=0x03,event=0x0/,
> cpu/umask=0x02,event=0x0/,cycles,branche
On Tue, Apr 04, 2017 at 01:53:15PM +0200, Jason A. Donenfeld wrote:
> Herbert applied this to his tree. It's probably a good stable
> candidate, since it's a two line change to fix a race condition.
>
> On Fri, Mar 24, 2017 at 3:16 PM, Herbert Xu
> wrote:
> > Jason A. Donenfeld wrote:
> >> Unde
On 03/20, Vivek Gautam wrote:
> diff --git a/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt
> b/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt
> new file mode 100644
> index ..a6d19acde9e0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.
On Tue, Apr 04, 2017 at 03:14:03PM +0530, Pushkar Jambhlekar wrote:
> Replacing 'unsigned' with 'unsigned int'
Why? You need to explain why you do something, not just say what you
did (that should be obvious if you read the patch...)
thanks,
greg k-h
On Tue, Apr 04, 2017 at 06:44:53PM +0200, Michal Hocko wrote:
Thanks for your testing! This is highly appreciated.
Can I assume your Tested-by?
Of course! Not quite done, though. I think I found another edge case.
You get an oops when removing all of a node's memory:
__nr_to_section
__pfn_t
On Tue, Apr 04, 2017 at 02:15:13PM +0100, John Keeping wrote:
> Hi Sean,
>
> On Sun, 12 Mar 2017 07:06:59 -0500, Rob Herring wrote:
>
> > On Fri, Mar 03, 2017 at 11:39:45AM +, John Keeping wrote:
> > > This reset is required in order to fully reset the internal state of the
> > > MIPI control
501 - 600 of 944 matches
Mail list logo
