3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Linus Torvalds
commit b9a532277938798b53178d5a66af6e2915cb27cf upstream.
As reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before
having initialized the IPC object sta
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Paul Burton
commit 7a63076d9a31a6c2073da45021eeb4f89d2a8b56 upstream.
The CONFIG_MIPS_MT symbol can be selected by CONFIG_MIPS_VPE_LOADER in
addition to CONFIG_MIPS_MT_SMP. We only w
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Paul Burton
commit 1e5fb282f8eda889776ee83f9214d5df9edaa26d upstream.
The has_mt macro ended with a branch, leaving its callers with a delay
slot that would be executed if Config3.MT
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Hogan
commit 53960059d56ecef67d4ddd546731623641a3d2d1 upstream.
If there is a DMA zone (usually 24bit = 16MB I believe), but no DMA32
zone, as is the case for some 32-bit kerne
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Paul Burton
commit a5b0f6db0e6cf6224e50f6585e9c8f0c2d38a8f8 upstream.
The MT-specific code in mips_cps_boot_vpes can safely be omitted from
kernels which don't support MT, with the d
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andreas Schwab
commit 8474ba74193d302e83401e16c85cc4b98caf upstream.
Make sure the compiler does not modify arguments of syscall functions.
This can happen if the compiler genera
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit ae93580ee59c02395c1711d3e6b90546b8137b86 upstream.
If driver backlight control is disabled, either by driver
parameter or default per-asic setting, revert to the
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: shengyong
commit 7c7feb2ebfc9c0552c51f0c050db1d1a004faac5 upstream.
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI error: init_volumes: not enough PEBs, required 706, avai
Hi Linus,
One urgent fix for an oops under console lock in some drivers, one uapi
fix, and one revert to fix rockchip regression.
I've got the sti driver pull request that I'll send out in a minute, don't
think it'll have any issues.
Dave.
The following changes since commit a18e2fa5e670a1b8
On 11/12, Rob Herring wrote:
> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote:
> > On 11/12, Rob Herring wrote:
> >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote:
>
> >> > +Some qcom based bootloaders identify the dtb blob based on a set of
> >> > +device properties like SoC,
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Kapileshwar Singh
commit c2e4b24ff848bb180f9b9cd873a38327cd219ad2 upstream.
When a trace recorded on a 32-bit device is processed with a 64-bit
binary, the higher 32-bits of the addr
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit 4cee6a9057d5e13911f0cb6e143d11dc1a3245dd upstream.
So that the bl encoder will be null if the GPU does not
control the backlight.
Reviewed-by: Michel Dänzer
Sig
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Michel=20D=C3=A4nzer?=
commit 4281f46ef839050d2ef60348f661eb463c21cc2e upstream.
Instead of only enabling the backlight (which seems to set it to max
brightness), just re-s
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Salva=20Peir=C3=B3?=
commit 4b6184336ebb5c8dc1eae7f7ab46ee608a748b05 upstream.
The dgnc_mgmt_ioctl() code fails to initialize the 16 _reserved bytes of
struct digi_dinfo af
Hi Linus,
The sti driver had a requirement on some patches in Greg's tree, they are
in, so I see no problems just merging this one now. But if it's too late
I don't mind either.
Dave.
The following changes since commit a18e2fa5e670a1b84e66522b221c42875b02028a:
Merge tag 'arm64-fixes' of
gi
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Hutchings
commit 4ab42d78e37a294ac7bc56901d563c642e03c4ae upstream.
Currently slhc_init() treats out-of-range values of rslots and tslots
as equivalent to 0, except that if tslot
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Hutchings
commit 0baa57d8dc32db78369d8b5176ef56c5e2e18ab3 upstream.
Compile-tested only.
Signed-off-by: Ben Hutchings
Signed-off-by: David S. Miller
Reference: CVE-2015-7799
S
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Adrian Hunter
commit b5cabbcbd157a4bf5a92dfc85134999a3b55342d upstream.
A copy of /proc/kcore containing the kernel text can be made to the
buildid cache. e.g.
perf buildid-
On 11/12, Olof Johansson wrote:
> On Mon, Oct 26, 2015 at 2:25 PM, Stephen Boyd wrote:
> > +Examples:
> > +
> > + "qcom,msm8916-v1-cdp-pm8916-v2.1"
>
> This is just awkward, but this...
>
> > +
> > +A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC of
> > version
> > +2
On 11/12/2015 06:06 PM, Al Stone wrote:
If it is a NAK, that's fine, but I also want to be sure I understand what the
objections are. Based on my understanding of the discussion so far over the
multiple versions, I think the primary objection is that the use of pretimeout
makes this driver too c
+++ Miroslav Benes [12/11/15 14:22 +0100]:
On Thu, 12 Nov 2015, Petr Mladek wrote:
On Thu 2015-11-12 00:33:12, Jessica Yu wrote:
> +++ Miroslav Benes [11/11/15 15:17 +0100]:
> >On Mon, 9 Nov 2015, Jessica Yu wrote:
> >
> >>diff --git a/include/linux/module.h b/include/linux/module.h
> >>index 3
On 11/12/2015 04:06 PM, Al Stone wrote:
On 11/05/2015 09:41 AM, Guenter Roeck wrote:
On 11/05/2015 07:00 AM, Fu Wei wrote:
Hi Timur,
On 5 November 2015 at 22:40, Timur Tabi wrote:
Fu Wei wrote:
Did you really read the "Note" above OK, let me paste it again
and again:
SBSA 2.3 Page
On 04/11/15 18:56, David Miller wrote:
>> Fixes: fd867d51f889 ("net/core: generic support for disabling netdev
>> features down stack")
> ...
>> Reported-by: Nikolay Aleksandrov
>> Signed-off-by: Jarod Wilson
>> ---
>> v2: Based on suggestions from Alex, and with not changing err to ret, this
>
I'm having trouble getting sound working on a Meegopad T02[1]. I'm
running Arch with a 4.3 kernel[2] with patches[3] for wifi stability.
So far, the drivers appear to load, but produce the following dmesg output:
> [5.579629] baytrail-pcm-audio baytrail-pcm-audio: ipc: error DSP boot
> timeo
On Thu, Nov 12, 2015 at 10:22 PM, Peter Hurley wrote:
> On 11/12/2015 02:57 PM, One Thousand Gnomes wrote:
> An illustrative (kernel-space) example is the mess that is dmaengine_pause().
> Some DMA implementations provide the means to stop and restart DMA without
> losing data and some DMA implem
try_to_unmap_one() should be able to handle hugetlb, but page_remove_rmap()
in that function takes false as a compound flag, which breaks hugepage migration
with the following message.
Soft offlining page 0x1d4a00 at 0x7ff634a0
soft offline: 0x1d4a00: migration failed 1, type 60040
Rewrite `arch_elf_pt_proc' and `arch_check_elf' using a union to access
the ELF file header.
Signed-off-by: Maciej W. Rozycki
---
linux-mips-elf-ehdr.diff
Index: linux-sfr-test/arch/mips/kernel/elf.c
===
--- linux-sfr-test.orig/arch
Hi,
As many of you have been aware it has been a long practice for software
using IEEE 754 floating-point arithmetic run on MIPS processors to use an
encoding of Not-a-Number (NaN) data different to one used by software run
on other processors. And as of IEEE 754-2008 revision [1] this encoding
Implement IEEE Std 754-2008 non-arithmetic ABS.fmt and NEG.fmt emulation
wired to the state of the FCSR.ABS2008 bit. In the non-arithmetic mode
the sign bit is altered according to the operation requested regardless
of the datum encoded in the input operand, no other bits are changed,
the resu
Allocate CPU option bits and define macros for the legacy-NaN and
2008-NaN IEEE Std 754 MIPS architecture features. Unconditionally mark
the legacy-NaN feature as present across hardware and emulated
floating-point configurations.
Signed-off-by: Maciej W. Rozycki
---
linux-mips-nan-legacy.dif
Implement IEEE Std 754-2008 NaN encoding wired to the state of the
FCSR.NAN2008 bit. Make the interpretation of the quiet bit in NaN data
as follows:
* in the legacy mode originally defined by the MIPS architecture the
value of 1 denotes an sNaN whereas the value of 0 denotes a qNaN,
* in t
Add an `ieee754=' kernel parameter to control IEEE Std 754 conformance
mode.
Use separate flags copied from the respective CPU feature flags, and
adjusted according to the conformance mode selected, to make binaries
requesting individual NaN encoding modes accepted or rejected as needed.
Upda
Update the ELF personality macros used for individual ABIs to make
actions in the same order across all of them and match formatting too.
Signed-off-by: Maciej W. Rozycki
---
linux-mips-set-personality-shuffle.diff
Index: linux-sfr-test/arch/mips/include/asm/elf.h
===
Also pass any interpreter's file header to `arch_check_elf' so that any
architecture handler can have a look at it if needed.
Signed-off-by: Maciej W. Rozycki
---
linux-arch-check-elf-interp.diff
Index: linux-sfr-test/arch/mips/include/asm/elf.h
==
Determine the presence of and the amount of control available over IEEE
Std 754-2008 features.
In the case of a hardware FPU being used examine the FIR register for
the presence of the HAS2008 bit and then the FCSR register for the
writability of the ABS2008 and NAN2008 bits and the hardwired s
Handle the EF_MIPS_NAN2008 ELF file header flag and refuse execution
where there is no support in the FPU for the NaN encoding mode requested
by a binary invoked. Ensure that the setting of the bit in the binary
matches one in any intepreter used. Set the thread's initial FCSR
contents accord
Propagate sNaN payload in quieting in the legacy-NaN mode as well. If
clearing the quiet bit would produce infinity, then set the next lower
trailing significand field bit, matching the SB-1 and BMIPS5000 hardware
implementations. Some other MIPS FPU hardware implementations do
produce the de
On 2015/11/11, 10:21, "lustre-devel on behalf of Shivani Bhardwaj"
wrote:
>On Wed, Nov 11, 2015 at 4:24 PM, kbuild test robot wrote:
>> Hi Shivani,
>>
>> [auto build test ERROR on staging/staging-testing]
>> [also build test ERROR on v4.3 next-2015]
>>
>> url:
>>https://github.com/0day-c
Hi Nicholas,
Today's linux-next merge of the target-merge tree got conflicts in
several files. It looks like a newer version of all the commits in the
target-merge tree has been applied to the scsi tree, so I just dropped
the target-merge tree for today. You might like to tidy it up with
respect
Thanks Albino
On Thu, Nov 12, 2015 at 4:43 PM, Albino B Neto wrote:
> 2015-11-12 21:46 GMT-02:00 Satay Epic :
>> Hello,
>>
>> I've an ARM SL3516 board with Linux 2.6.15 and I've tool-chain setup.
>> I could able to compile the GPL source. This board has red-boot.
>>
>> I would like to update th
On Thu, Nov 12, 2015 at 4:14 PM, Arnd Bergmann wrote:
> The dw_mmc driver stores the physical address of the MMIO registers
> in a pointer, which requires the use of type casts, and is actually
> broken if anyone ever has this device on a 32-bit SoC in registers
> above 4GB. Gcc warns about this p
On 11/12/2015 07:41 PM, Andy Shevchenko wrote:
> On Thu, Nov 12, 2015 at 10:22 PM, Peter Hurley
> wrote:
>> On 11/12/2015 02:57 PM, One Thousand Gnomes wrote:
>
>> An illustrative (kernel-space) example is the mess that is dmaengine_pause().
>> Some DMA implementations provide the means to stop
2015-11-12 21:46 GMT-02:00 Satay Epic :
> Hello,
>
> I've an ARM SL3516 board with Linux 2.6.15 and I've tool-chain setup.
> I could able to compile the GPL source. This board has red-boot.
>
> I would like to update the kernel to 3.8.24. My first attempt so not
> sure about anything I should kn
On Fri, Nov 13, 2015 at 3:11 AM, Peter Hurley wrote:
> On 11/12/2015 07:41 PM, Andy Shevchenko wrote:
>> On Thu, Nov 12, 2015 at 10:22 PM, Peter Hurley
>> wrote:
>>> On 11/12/2015 02:57 PM, One Thousand Gnomes wrote:
>>
>>> An illustrative (kernel-space) example is the mess that is
>>> dmaengin
On 11/13/2015 12:20 AM, Alan Stern wrote:
On Thu, 12 Nov 2015, Lu Baolu wrote:
Commit 8306095fd2c1 ("USB: Disable USB 3.0 LPM in critical sections.")
adds usb3_lpm_enabled member to struct usb_device. There is no reference
to this member now. Hence, it could be removed.
Signed-off-by: Lu Bao
On Thu, Nov 12, 2015 at 3:21 PM, Heikki Krogerus
wrote:
> 8250_mid uses rational_best_approximation() function, so the
> driver needs to select CONFIG_RATIONAL option.
>
> This fixes build error when CONFIG_RATIONAL is not enabled:
>
> drivers/built-in.o: In function `mid8250_set_termios':
> 8250_
Guten Tag,
Ich brauche einen ausländischen Partner für einen gemeinsamen Geschäfts
Vorschlag, der auf die Übertragung von einer großen Geldsumme an einem
ausländischen Konto bezieht, als Empfänger der Mittel. Alles an dieser
Transaktion rechtlich ohne Brücke der Finanzbehörde sowohl in meinem L
Hi James,
After merging the scsi tree, today's linux-next build (powerpc
allyesconfig) failed like this:
In file included from drivers/scsi/mpt3sas/mpt3sas_scsih.c:59:0:
drivers/scsi/mpt3sas/mpt3sas_scsih.c: In function '_scsih_io_done':
drivers/scsi/mpt3sas/mpt3sas_base.h:1414:1: error: inlining
On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote:
> On 11/12, Rob Herring wrote:
>> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote:
>> > On 11/12, Rob Herring wrote:
>> >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote:
>>
>> >> > +Some qcom based bootloaders identify the dt
Hi,
I am seeing random crashes on my home security camera server with
linux 3.10.92 and 3.14.56. Both have been compiled with gcc 5.2.
Searching points me at possible bad RAM (I have not had a chance to
run memtest yet). The machine usually locks up within half hour, but
what is odd is 4.1.13 has
On 11/12/2015 08:26 PM, Andy Shevchenko wrote:
> On Fri, Nov 13, 2015 at 3:11 AM, Peter Hurley
> wrote:
>> On 11/12/2015 07:41 PM, Andy Shevchenko wrote:
>>> On Thu, Nov 12, 2015 at 10:22 PM, Peter Hurley
>>> wrote:
On 11/12/2015 02:57 PM, One Thousand Gnomes wrote:
>>>
An illustrativ
Rewrite the abs macro such that it return type does not depend on the
architecture and no unexpected type conversion happen inside of it. The
only conversion is from unsigned to signed type. char is left as
a return type but treated as a signed type regradless of it’s actual
signedness.
With the
Hi Dave,
On 11/12/2015 02:01 PM, Dave Young wrote:
Hi, Baolu
On 11/12/15 at 10:45am, Lu, Baolu wrote:
>Hi Dave,
>
>Which device are you testing with? This implementation was developed
>and tested on Intel Skylake devices.
>
>It doesn't surprise me if it doesn't work with other silicons. But it
On 12 November 2015 at 20:59, Jan Kara wrote:
> On Thu 12-11-15 20:51:10, Baolin Wang wrote:
>> On 12 November 2015 at 20:24, Jan Kara wrote:
>> > On Thu 12-11-15 19:46:26, Baolin Wang wrote:
>> >> On 12 November 2015 at 19:06, Jan Kara wrote:
>> >> > On Thu 12-11-15 17:40:59, Baolin Wang wrote:
On 2015/11/13 0:31, Laura Abbott wrote:
> On 11/12/2015 03:55 AM, zhong jiang wrote:
>> On 2015/11/11 9:57, Laura Abbott wrote:
>>> Currently, the set_memory_* functions that are implemented for arm64
>>> are restricted to module addresses only. This was mostly done
>>> because arm64 maps normal zo
On 12 November 2015 at 23:26, Jens Axboe wrote:
> On 11/12/2015 03:04 AM, Mark Brown wrote:
>>
>> On Thu, Nov 12, 2015 at 04:20:41PM +0800, Baolin Wang wrote:
>>
>>> 3. perforamence data
>>> It is just a simple dd test result, and will provide the formal report
>>> in future. But from the simple t
This patch fixes explain the occasion of "hisilcon,mdio" according to
Arnd's comments. specify it is only used for hip04.
First, please give your commnents.
Signed-off-by: huangdaode
---
Documentation/devicetree/bindings/net/hisilicon-hns-mdio.txt | 4 +++-
1 file changed, 3 insertions(+), 1 de
On 11/12, Rob Herring wrote:
> On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote:
> > On 11/12, Rob Herring wrote:
> >> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote:
> >> > On 11/12, Rob Herring wrote:
> >> >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote:
> >>
> >> >> > +
On 2015/11/12 23:27, Paolo Bonzini wrote:
On 12/11/2015 12:56, Takuya Yoshikawa wrote:
diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
index 9d21b44..f414ca6 100644
--- a/arch/x86/kvm/paging_tmpl.h
+++ b/arch/x86/kvm/paging_tmpl.h
@@ -598,7 +598,7 @@ static int FNAME(fetch)
On Fri, 13 Nov 2015, Michal Nazarewicz wrote:
> Rewrite the abs macro such that it return type does not depend on the
> architecture and no unexpected type conversion happen inside of it. The
> only conversion is from unsigned to signed type. char is left as
> a return type but treated as a sign
Hi all,
Please do *not* add any material intended for v4.5 to your linux-next
included branches until after v4.4-rc1 has been released.
Changes since 20151112:
Dropped tree: target-merge (many conflicts)
The clockevents tree gained a conflict against the h8300 tree.
The scsi tree gained a
This is preparation step to report test failed pfn in new tracepoint
to analyze cma allocation failure problem. There is no functional change
in this patch.
Acked-by: David Rientjes
Acked-by: Michal Nazarewicz
Signed-off-by: Joonsoo Kim
---
mm/page_isolation.c | 13 ++---
1 file change
cma allocation should be guranteeded to succeed, but, sometimes,
it could be failed in current implementation. To track down
the problem, we need to know which page is problematic and
this new tracepoint will report it.
Acked-by: Michal Nazarewicz
Signed-off-by: Joonsoo Kim
---
include/trace/ev
Now, we have tracepoint in test_pages_isolated() to notify
pfn which cannot be isolated. But, in alloc_contig_range(),
some error path doesn't call test_pages_isolated() so it's still
hard to know exact pfn that causes allocation failure.
This patch change this situation by calling test_pages_isol
On 11/13/15 at 10:04am, Lu, Baolu wrote:
> Hi Dave,
>
> On 11/12/2015 02:01 PM, Dave Young wrote:
> >Hi, Baolu
> >
> >On 11/12/15 at 10:45am, Lu, Baolu wrote:
> >>>Hi Dave,
> >>>
> >>>Which device are you testing with? This implementation was developed
> >>>and tested on Intel Skylake devices.
> >
On 2015/11/12 19:55, zhong jiang wrote:
> On 2015/11/11 9:57, Laura Abbott wrote:
>> Currently, the set_memory_* functions that are implemented for arm64
>> are restricted to module addresses only. This was mostly done
>> because arm64 maps normal zone memory with larger page sizes to
>> improve TL
Dear RT Folks,
I'm pleased to announce the 3.4.110-rt138 stable release.
This release is just an update to the new stable 3.4.110 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-r
Thanks Arnd, this looks ok to me
Zhou Wang can you please Ack?
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Arnd Bergmann
> Sent: 12 November 2015 12:22
> To: linux-arm-ker...@lists.infradead.org
> Cc: Jisheng
On 11/11/2015 10:34 AM, Douglas Anderson wrote:
> In some cases, like when you've got a "Microsoft Wireless Keyboard 2000"
> connected to dwc2 with a hub, expected that we'll get some transfer
> errors sometimes. The controller is expected to try at least 3 times
> before giving up. See figure "F
get_seconds() API is not y2038 safe on 32 bit systems and the API
is deprecated. Replace it with calls to ktime_get_real_seconds()
API instead. Change mddev structure types to time64_t accordingly.
32 bit signed timestamps will overflow in the year 2038.
Change the user interface mdu_array_info_s
+devicetree-spec
On Thu, Nov 12, 2015 at 5:53 PM, Greg Hackmann wrote:
> ramoops is one of the remaining places where ARM vendors still rely on
> board-specific shims. Device Tree lets us replace those shims with
> generic code.
I've had a version this in my tree forever to push upstream...
>
On Thu, Nov 12, 2015 at 1:57 PM, Yang Shi wrote:
> BPF fp should point to the top of the BPF prog stack. The original
> implementation made it point to the bottom incorrectly.
> Move A64_SP to fp before reserve BPF prog stack space.
>
> CC: Zi Shen Lim
> CC: Xi Wang
> Signed-off-by: Yang Shi
>
On Thu, Nov 12, 2015 at 3:42 PM, Peter Maydell wrote:
> On 12 November 2015 at 21:33, Rob Herring wrote:
>> On Thu, Nov 12, 2015 at 04:24:50PM +, Peter Maydell wrote:
>>> The existing device tree bindings assume that we are only trying to
>>> describe a single address space with a device tree
On 12 November 2015 at 20:57, Arnd Bergmann wrote:
> On Thursday 12 November 2015 20:51:10 Baolin Wang wrote:
>> On 12 November 2015 at 20:24, Jan Kara wrote:
>> > On Thu 12-11-15 19:46:26, Baolin Wang wrote:
>> >> On 12 November 2015 at 19:06, Jan Kara wrote:
>> >> > Well, one question is "can
On 12 November 2015 at 23:02, Mark Brown wrote:
> On Thu, Nov 12, 2015 at 01:57:27PM +0100, Arnd Bergmann wrote:
>> On Thursday 12 November 2015 20:51:10 Baolin Wang wrote:
>
>> > But it maybe not enough for HW engine which can handle maybe 10M/20M
>> > at one time.
>
>> Given that you have alread
On Thu, Nov 12, 2015 at 1:57 PM, Yang Shi wrote:
>
> Save and restore FP/LR in BPF prog prologue and epilogue, save SP to FP
> in prologue in order to get the correct stack backtrace.
>
> However, ARM64 JIT used FP (x29) as eBPF fp register, FP is subjected to
> change during function call so it m
On Thu, Nov 12, 2015 at 4:42 AM, Liviu Dudau wrote:
> On Wed, Nov 11, 2015 at 12:48:50PM -0600, Rob Herring wrote:
>> On Wed, Nov 11, 2015 at 04:06:47PM +, Liviu Dudau wrote:
>> > Cc: Rob Herring
>> > Cc: Pawel Moll
>> > Cc: Mark Rutland
>> > Cc: Ian Campbell
>> > Cc: Kumar Gala
>> >
>> >
> I don't have a device large enough to test for signedness errors, since
> passing
> huge values for start and len never make it past the i_size_read check.
If you have someone trying to bypass your sanity checks then if
start=18446744073709551104 and len=1024 the result of adding them togethe
At present scheduler resets task's wait start timestamp when the task
migrates to another rq. This misleads scheduler itself into reporting
less wait time than actual by omitting time spent for waiting prior to
migration and also more wait count than actual by counting migration as
wait end event
On Thu, Nov 12, 2015 at 11:33 AM, Shi, Yang wrote:
> On 11/11/2015 4:39 AM, Will Deacon wrote:
>>
>> Wait a second, we're both talking rubbish here :) The STR (immediate)
>> form is referring to the addressing mode, whereas this patch wants to
>> store an immediate value to memory, which does need
Hi everyone,
This is v2 of the AXP223 PMIC series.
Changes since v1:
- Dropped NMI interrupt controller dts patch (Merged)
- Change MFD_AXP20X to represent the axp20x core, and drop MFD_AXP20X_CORE
- Keep the axp20x core bits named axp20x.c
- Add patch 7 to add AXP223 to sun8i-q8-co
The axp20x driver assumes the device is i2c based. This is not the
case with later chips, which use a proprietary 2 wire serial bus
by Allwinner called "Reduced Serial Bus".
This patch follows the example of mfd/wm831x and splits it into
an interface independent core, and an i2c specific glue laye
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
Reviewed-by: Mark Brown
---
drivers/regulator/axp20x-regulator.c | 3
Some boards, such as tablets, have regulators providing power to parts
of the display pipeline, like signal converters and LCD panels.
Add labels to the simplefb device nodes so that we can reference them
in the board dts files to add regulator supply properties.
Signed-off-by: Chen-Yu Tsai
---
axp20x support has been split into 2 parts, I2C and RSB interface
variants.
Update the MFD_AXP20X symbol for I2C support, and also enable
MFD_AXP20X_RSB to support RSB variants.
Keep MFD_AXP20X enabled for now, to ease migration for automated boot
farms while the patches are being merged. This sh
axp20x support has been split into 2 parts, I2C and RSB interface
variants.
Update the MFD_AXP20X symbol for I2C support. Also enable SUNXI_RSB
MFD_AXP20X_RSB to support RSB variants. Build these drivers as
modules.
Keep MFD_AXP20X enabled for now, to ease migration for automated
boot farms while
axp20x support has been split into 2 parts, I2C and RSB interface
variants.
Update the MFD_AXP20X symbol for I2C support, and also enable
MFD_AXP20X_RSB to support RSB variants. Build these drivers as
modules.
Keep MFD_AXP20X enabled for now, to ease migration for automated
boot farms while the p
A23/A33 Q8 tablets have an X-Powers AXP223 PMIC connected via RSB. It's
regulators provide power to various parts of the SoC and the board.
Also add simplefb regulator supplies and update existing ones.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-q8-common.dtsi | 84
A23/A33 Q8 tablets have an X-Powers AXP223 PMIC connected via RSB. It's
regulators provide power to various parts of the SoC and the board.
Also add lcd regulator supply for simplefb and update the existing
vmmc-supply for mmc0.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-q8-common.
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
---
drivers/mfd/Kconfig| 11 ++
drivers/mfd/Makefile
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
Acked-by: Maxime Ripard
---
Documentation/devicetree/bindings/mfd/ax
This board has a X-Powers AXP223 PMIC connected via RSB. It's regulators
provide power to various parts of the SoC and the board.
Also update the regulator supply phandles.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts | 79 +-
1 file cha
On Fri, Nov 13, 2015 at 12:04 PM, Chen-Yu Tsai wrote:
> axp20x support has been split into 2 parts, I2C and RSB interface
> variants.
>
> Update the MFD_AXP20X symbol for I2C support, and also enable
> MFD_AXP20X_RSB to support RSB variants. Build these drivers as
> modules.
>
> Keep MFD_AXP20X en
On Fri, Nov 13, 2015 at 12:04 PM, Chen-Yu Tsai wrote:
> A23/A33 Q8 tablets have an X-Powers AXP223 PMIC connected via RSB. It's
> regulators provide power to various parts of the SoC and the board.
>
> Also add simplefb regulator supplies and update existing ones.
>
> Signed-off-by: Chen-Yu Tsai
On 10/07/2015 01:02 AM, Stephen Boyd wrote:
> On 10/01, Stephen Boyd wrote:
>> The oxili_cx GDSC is inside the power domain of the oxili GDSC.
>> Add the dependency so that the CX domain can properly power up.
>>
>> Reported-by: Rob Clark
>> Cc: Rajendra Nayak
>> Signed-off-by: Stephen Boyd
>>
Hi!
Thanks a lot for the help. I switched to vfio and got NIC working
again. Now I just have to figure out what I have to change to get this
to persist through the host boots. To tell the truth I couldn't quite
parse from that commit message that my device would stop working:).
The error messages
On Thu, 2015-11-12 at 18:41 -0500, Johannes Weiner wrote:
> @@ -711,6 +705,12 @@ static inline void mem_cgroup_wb_stats(struct
> bdi_writeback *wb,
> struct sock;
> void sock_update_memcg(struct sock *sk);
> void sock_release_memcg(struct sock *sk);
> +bool mem_cgroup_charge_skmem(struct cg_p
When the Device Tree source file got merged, some commented pinctrl lines
were left in the file. These are already defined so seems to be a cleanup
that was missed. Delete the unneeded lines from the file.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/am335x-baltos-ir5221.dts |
The header file defines a set of macros
for different SoCs families that falls under the OMAP sub-arch, that
allow to define the padconf register physical address instead of the
register offset from the padconf base.
But the am43xx and dra7xx SoCs families have their own pinctrl header
file so th
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/
801 - 900 of 983 matches
Mail list logo
