On 10/27/2016 08:15 PM, kernel test robot wrote:
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
wb-buf-throttle
commit b1fa1b67c176e41eeae2bfcc7df38117976cd92d ("block: hook up writeback
throttling")
in testcase: boot
on test
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of Scott Wood
> Sent: Friday, October 28, 2016 12:46 PM
> To: Y.B. Lu; linux-...@vger.kernel.org; ulf.hans...@linaro.org; Arnd
> Bergmann
> Cc:
Hi,
On Fri, Oct 28, 2016 at 01:21:36PM +0200, Pavel Machek wrote:
> > Has this been tested on a system vulnerable to rowhammer, and if so, was
> > it reliable in mitigating the issue?
> >
> > Which particular attack codebase was it tested against?
>
> I have rowhammer-test here,
>
> commit
On Fri, Oct 28, 2016 at 03:05:22PM +0100, Mark Rutland wrote:
>
> > > * the precise semantics of performance counter events varies drastically
> > > across implementations. PERF_COUNT_HW_CACHE_MISSES, might only map to
> > > one particular level of cache, and/or may not be implemented on all
On 10/28/2016 03:32 AM, Linus Walleij wrote:
On Fri, Oct 28, 2016 at 12:27 AM, Linus Walleij
wrote:
On Thu, Oct 27, 2016 at 11:08 PM, Jens Axboe wrote:
blk-mq has evolved to support a variety of devices, there's nothing
special about mmc that can't
On Fri, Oct 28, 2016 at 3:58 PM, Peter Zijlstra wrote:
> On Fri, Oct 28, 2016 at 03:47:58PM +0200, Tom Gundersen wrote:
>> On Fri, Oct 28, 2016 at 3:33 PM, Peter Zijlstra wrote:
>> > On Fri, Oct 28, 2016 at 01:33:25PM +0200, Tom Gundersen wrote:
>
>> >
On Thu, Oct 27, 2016 at 05:33:57PM -0700, Andy Lutomirski wrote:
> Hi-
>
> I think this error on my laptop is new on 4.9 kernels:
>
> [ +0.014696] tpm_tis 00:09: 1.2 TPM (device-id 0xFE, rev-id 2)
> [ +0.012228] tpm tpm0: TPM self test failed
> [ +0.19] tpm_tis: probe of 00:09 failed with
On Thu, Oct 27, 2016 at 09:09:16PM -0600, Jason Gunthorpe wrote: > On Thu, Oct
27, 2016 at 05:33:57PM -0700, Andy Lutomirski wrote:
> > Hi-
> >
> > I think this error on my laptop is new on 4.9 kernels:
> >
> > [ +0.014696] tpm_tis 00:09: 1.2 TPM (device-id 0xFE, rev-id 2)
> > [ +0.012228]
On Wed, Oct 26, 2016 at 09:18:05PM +0200, David Herrmann wrote:
> From: Tom Gundersen
>
> The transaction engine is an object that lives on the stack and is used
> to stage and commit multicasts properly. Unlike unicasts, a multicast
> cannot just be queued on each destination, but
This is a workaround for VHT-enabled STAs which break the spec
and have the VHT-MCS Rx map filled in with value 3 for all eight
spacial streams.
As per spec, in section 22.1.1 Introduction to the VHT PHY
A VHT STA shall support at least single spactial stream VHT-MCSs
0 to 7 (transmit and
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.9-rc3
with top-most commit 8b2ada27dc1045e8191673bf769a1136ce8a0127
Merge branches 'pm-cpufreq-fixes' and 'pm-sleep-fixes'
on top of commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69
On Sat, 29 Oct 2016, Paul Bolle wrote:
> On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> > When POSIX timers are configured out, the PTP clock subsystem should be
> > left out as well. However a bunch of ethernet drivers currently *select*
> > the later in their Kconfig entries.
From: Brian Norris
If checkpatch.pl gets copied out of the tree, --no-tree shouldn't start
complaining:
Use of uninitialized value $root in concatenation (.) or string at
/path/to/checkpatch.pl line 764.
Let's just give the safe answer instead -- don't warn
Hi Sarangdhar,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.9-rc2 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenie
On Fri, Oct 28, 2016 at 2:53 PM, Hans Verkuil wrote:
> Hi Matt,
>
> On 28/10/16 22:14, Matt Ranostay wrote:
>>
>> So want to toss a few thoughts on adding support for thermopile
>> devices (could be used for FLIR Lepton as well) that output pixel
>> data.
>> These typically
On Fri, Oct 28, 2016 at 12:11:21PM -0500, David Lechner wrote:
> On 10/28/2016 07:39 AM, Alexandre Bailon wrote:
> >On 10/28/2016 04:56 AM, David Lechner wrote:
> >>On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
> >>>When the phy is forced in host mode, only the first hot plug and
> >>>hot remove
On Fri, Oct 28, 2016 at 03:12:32PM -0400, Tejun Heo wrote:
> Hello, Peter.
>
> On Fri, Oct 28, 2016 at 09:07:02PM +0200, Peter Zijlstra wrote:
> > One alternative is to inherit the iowait state of the task we block on.
> > That'll not get rid of the branches much, but it will remove the new
> >
Hi,
I've got the following error report while running the syzkaller fuzzer:
[ cut here ]
WARNING: CPU: 0 PID: 4608 at kernel/sched/core.c:7724
__might_sleep+0x14c/0x1a0 kernel/sched/core.c:7719
do not call blocking ops when !TASK_RUNNING; state=1 set at
[]
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-4.9-rc3
with top-most commit 21e2d9d5292f8a5cd1aa4e63891437589d233d35
Merge branches 'acpica-fixes', 'acpi-pci-fixes' and 'acpi-apei-fixes'
on top of commit
On Fri, Oct 28, 2016 at 07:26:31PM -0700, Brian Norris wrote:
> From: Brian Norris
>
> If checkpatch.pl gets copied out of the tree, --no-tree shouldn't start
> complaining:
>
> Use of uninitialized value $root in concatenation (.) or string at
>
If checkpatch.pl gets copied out of the tree, --no-tree shouldn't start
complaining:
Use of uninitialized value $root in concatenation (.) or string at
/path/to/checkpatch.pl line 764.
Let's just give the safe answer instead -- don't warn about "obsolete"
files.
Fixes: 85b0ee18bbf8
On Fri, Oct 28, 2016 at 1:40 PM, Marek Vasut wrote:
> On 10/28/2016 10:30 PM, Devin Heitmueller wrote:
>> Hi Matt,
>>
>>> Need some input for the video pixel data types, which the device we
>>> are using (see datasheet links below) is outputting pixel data in
>>> little endian
On Fri, Oct 28, 2016 at 1:30 PM, Devin Heitmueller
wrote:
> Hi Matt,
>
>> Need some input for the video pixel data types, which the device we
>> are using (see datasheet links below) is outputting pixel data in
>> little endian 16-bit of which a 12-bits signed value
On Thu, Oct 27, 2016 at 12:32 AM, Baolin Wang wrote:
> On 18 October 2016 at 14:47, Baolin Wang wrote:
>> From the trace log, we can find out the 'Binder:3292_2' process
>> set one alarm timer which resumes the system.
>>
>> Signed-off-by: Baolin
Since commit 761ed4a94582ab29 ("tty: serial_core: convert uart_close to
use tty_port_close"), the serial console is broken on various systems
and typing "reboot" splats the following on the serial console:
INIT: Sending p[ 427.863916] BUG: unable to handle kernel NULL pointer
dereference at
On 28/10/2016 13:08, Borislav Petkov wrote:
> On Fri, Oct 28, 2016 at 12:17:02PM +0200, Paolo Bonzini wrote:
>> Otherwise, if you add a cpuid_count_edx function to processor.h then one
>> can do:
>>
>> entry_>edx &= cpuid_count_edx(7, 0);
>>
>> which is decent too.
>
> If you think of
Greg,
As discussed, these are the 2 fixes needed to fix regressions with
761ed4a94582ab29 ("tty: serial_core: convert uart_close to use
tty_port_close"). Hopefully these fix all the fallout.
These apply on top of the previous patch from me which you applied.
Rob
Geert Uytterhoeven (1):
From: Geert Uytterhoeven
The port->console flag is always false, as uart_console() is called
before the serial console has been registered.
Hence for a serial port used as the console, uart_tty_port_shutdown()
will still be called when userspace closes the port,
On Thursday, October 27, 2016 8:13:08 PM CEST Ulf Hansson wrote:
> On 27 October 2016 at 19:43, Jens Axboe wrote:
> > On 10/27/2016 11:32 AM, Ulf Hansson wrote:
> >>
> >> [...]
> >>
> >>>
> >>> I'm hesistant to add a new scheduler because it's very easy to add, very
> >>>
On Fri, Oct 28, 2016 at 12:56:09PM +0200, Richard Genoud wrote:
> 2016-10-28 11:51 GMT+02:00 Uwe Kleine-König :
> > On Fri, Oct 28, 2016 at 01:13:31AM +0200, Alexandre Belloni wrote:
> >> On 27/10/2016 at 20:02:29 +0200, Uwe Kleine-König wrote :
> >> > Hello
On Fri, Oct 28, 2016 at 07:07:46AM -0500, Rob Herring wrote:
> Greg,
>
> As discussed, these are the 2 fixes needed to fix regressions with
> 761ed4a94582ab29 ("tty: serial_core: convert uart_close to use
> tty_port_close"). Hopefully these fix all the fallout.
>
> These apply on top of the
On Fri, Oct 28, 2016 at 2:07 PM, Arnd Bergmann wrote:
>> > I don't think that's an accurate statement. In terms of coverage, most
>> > drivers do support blk-mq. Anything SCSI, nvme, virtio-blk, SATA runs on
>> > (or can run on) top of blk-mq.
>>
>> Well, I just used "git grep" and
On Fri, Oct 28, 2016 at 08:52:49PM +0900, Jaehoon Chung wrote:
[...]
> >> Could you check the below thing..
> >>
> >> /* find reset controller when exist */
> >> - pdata->rstc = devm_reset_control_get_optional(dev, NULL);
> >> + pdata->rstc =
TPS65217 MFD driver supports the IRQ domain to handle the charger input
interrupts and push button status event. The interrupt controller enables
corresponding IRQ handling in the charger[*] and power button driver[**].
[*] drivers/power/supply/tps65217_charger.c
[**]
TPS65217 interrupt events include push button pressed/released, USB and AC
voltage status change. AM335x bone based boards (like BB, BBB, BBG) have
common PMIC interrupt pin (named NMI) of AM335x core.
This patchset support interrupts in device tree file.
v2:
Add missing a dt-binding header
On 10/28/2016 04:56 AM, David Lechner wrote:
> On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
>> When the phy is forced in host mode, only the first hot plug and
>> hot remove works. That is actually because the driver execute the
>> OTG workaround, whereas it is not applicable in host or device
Support the charger driver and disable it by default.
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/tps65217.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/tps65217.dtsi b/arch/arm/boot/dts/tps65217.dtsi
index 27935f8..8f77d0d 100644
---
On Fri, 28 Oct 2016 15:33:58 +0800
Jike Song wrote:
> On 10/27/2016 05:29 AM, Kirti Wankhede wrote:
> > Added blocking notifier to IOMMU TYPE1 driver to notify vendor drivers
> > about DMA_UNMAP.
> > Exported two APIs vfio_register_notifier() and vfio_unregister_notifier().
On 10/28/2016 1:03 PM, Jike Song wrote:
> On 10/27/2016 05:29 AM, Kirti Wankhede wrote:
>>
>> +/*
>> + * This function finds pfn in domain->external_addr_space->pfn_list for
>> given
>> + * iova range. If pfn exist, notify pfn to registered notifier list. On
>> + * receiving notifier
On Tue, Oct 25, 2016 at 09:06:34AM +0200, Jean-Francois Moine wrote:
> On Tue, 25 Oct 2016 07:38:55 +0200
> LABBE Corentin wrote:
>
> > > On Sat, Oct 22, 2016 at 03:53:28PM +0200, Corentin Labbe wrote:
> > > > Since SID's content is constant over reboot,
> > >
> > >
On Friday, October 28, 2016 2:46:42 PM CEST Peter Hutterer wrote:
> On Thu, Oct 27, 2016 at 03:24:55PM -0700, Deepa Dinamani wrote:
> > On Wed, Oct 26, 2016 at 7:56 PM, Peter Hutterer
> > wrote:
> > > On Mon, Oct 17, 2016 at 08:27:32PM -0700, Deepa Dinamani wrote:
> > >
[Add Steve Ellcey, thanks for testing on ThunderX]
Lmbench-3.0-a9 testing is performed on ThunderX machine to check that
ILP32 series does not add performance regressions for LP64. Test
summary is in the table below. Our measurements doesn't show
significant performance regression of LP64 if
On 27 October 2016 at 17:27, Laura Abbott wrote:
>
> Page mappings with full RWX permissions are a security risk. x86
> has an option to walk the page tables and dump any bad pages.
> (See e1a58320a38d ("x86/mm: Warn on W^X mappings")). Add a similar
> implementation for
The commit d8ff0c63fbcb ("drm/tilcdc: Adjust the FB_CEILING address")
added an adjustment of the FB_CEILING address. This is done by decrementing
the address by one.
On the AM335x (rev 0x4F201000) the framebuffer is rotated left over the
display border, because the ceiling address is 8f276fff
This error message will be printed when a FIFO underflow irq has
triggered. Since this happens sometimes and the error message will be
displayed on the console, it should have a correct spelling.
Signed-off-by: Daniel Schultz
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 2 +-
Hi,
On 10/28/2016 07:19 PM, Leo Yan wrote:
> On Fri, Oct 28, 2016 at 06:54:58PM +0900, Jaehoon Chung wrote:
>
> [...]
>
> Could you share the log? Is there any log about failure?
Sure, please see below log:
>>>
>>> It's related with -EPROBE_DEFER..I'm not sure but if
>>>
Hi!
> > I agree this needs to be tunable (and with the other suggestions). But
> > this is actually not the most important tunable: the detection
> > threshold (rh_attr.sample_period) should be way more important.
> >
> > And yes, this will all need to be tunable, somehow. But lets verify
> >
David, Tom,
On Wed, Oct 26, 2016 at 9:18 PM, David Herrmann wrote:
> +struct bus1_peer *bus1_peer_new(void)
> +{
> + static atomic64_t peer_ids = ATOMIC64_INIT(0);
> + const struct cred *cred = current_cred();
> + struct bus1_peer *peer;
> + struct
On Thu, Oct 27, 2016 at 3:03 AM, Eric Jeong
wrote:
> From: Eric Jeong
>
> This patch adds support for PV88080 PMIC GPIOs.
> PV88080 has two configurable GPIOs.
>
> Kconfig and Makefile are updated to reflect support
> for
On Fri, Oct 28, 2016 at 01:40:23PM +0200, Simon Horman wrote:
> On Fri, Oct 28, 2016 at 11:34:22AM +0200, Pablo Neira Ayuso wrote:
> > On Mon, Oct 24, 2016 at 10:47:54PM +0300, Julian Anastasov wrote:
> > >
> > > Hello,
> > >
> > > On Mon, 24 Oct 2016, Arnd Bergmann wrote:
> > >
> > > >
On 2016-10-19 14:31, Thierry Reding wrote:
> On Wed, Oct 19, 2016 at 02:27:50PM +0200, Thierry Reding wrote:
>> On Tue, Oct 04, 2016 at 05:29:21PM +0200, Peter Rosin wrote:
>>> From: Gustaf Lindström
>>>
>>> The Sharp 15" LQ150X1LG11 panel is an XGA TFT LCD panel.
>>>
>>> The
On Thu, Oct 27, 2016 at 3:03 AM, Eric Jeong
wrote:
> +++ b/drivers/mfd/pv88080-i2c.c
> +
> +static const struct of_device_id pv88080_of_match_table[] = {
> + { .compatible = "pvs,pv88080",.data = (void *)TYPE_PV88080_AA },
> + { .compatible =
On Thursday, October 27, 2016 4:12:54 PM CEST Dmitry Torokhov wrote:
> On Thu, Oct 27, 2016 at 03:25:43PM -0700, Deepa Dinamani wrote:
> > > If users are forced to update to adapt to the new event format, should
> > > we consider more radical changes? For example, does it make sense to
> > > send
On Fri, Oct 28, 2016 at 02:07:21PM +0200, Paolo Bonzini wrote:
> cpuid_count_edx would be just
>
> static inline unsigned int cpuid_count_edx(unsigned op, unsigned count)
> {
> unsigned int eax, ebx, ecx, edx;
>
> cpuid_count(op, count, , , , );
>
> return edx;
> }
Even
On Sat, Oct 22, 2016 at 06:36:05PM -0400, Paul Gortmaker wrote:
> This is basically the same as module_misc_device but without the
> presence of an exit/remove function. Similar in nature to the
> commit f309d4443130bf814e991f836e919dca22df37ae ("platform_device:
> better support builtin
2016-10-28 Daniel Vetter :
> On Thu, Oct 27, 2016 at 05:37:09PM -0200, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > There is now a new property called FENCE_FD attached to every plane
> > state that receives the sync_file fd from
AM335x bone based boards have the PMIC interrupt named NMI which is
connected to TPS65217 device. AM335x main interrupt controller provides it
and the number is 7.
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 4
1 file changed, 4
Enum value of 'tps65217_irq_type' is not matched with DT parsed hwirq
number[*].
The MFD driver gets the IRQ data by referencing hwirq, but the value is
different. So, irq_to_tps65217_irq() returns mismatched IRQ data.
Eventually, the power button driver enables not PB but USB interrupt
when it
This enables the charger driver gets corresponding IRQ number by using
platform_get_irq_byname() helper.
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 8
1 file changed, 8 insertions(+)
diff --git
This enables the power button driver gets corresponding IRQ number by
using platform_get_irq().
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi
TPS65217 supports three interrupt sources. This patch enables assigning
each IRQ number in the charger and power button node. Then corresponding
IRQ will be requested by each driver.
Signed-off-by: Milo Kim
---
include/dt-bindings/mfd/tps65217.h | 26
Support the power button driver and disable it by default.
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/tps65217.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/tps65217.dtsi b/arch/arm/boot/dts/tps65217.dtsi
index 8f77d0d..02de56b 100644
On Monday, October 17, 2016 8:27:32 PM CEST Deepa Dinamani wrote:
> @@ -55,24 +60,24 @@ struct ff_effect_compat {
>
> static inline size_t input_event_size(void)
> {
> - return (in_compat_syscall() && !COMPAT_USE_64BIT_TIME) ?
> - sizeof(struct input_event_compat) :
Some subsystem polices have a strict requirement that every patch must
have at least one reviewer before being approved for upstream. Since
encouraging review is good policy (great review is even better policy!)
enforce checking for a Reviewed-by when checkpath is run with --strict
(or with
Hi,
On 28 October 2016 at 06:00, NeilBrown wrote:
> On Thu, Oct 27 2016, Baolin Wang wrote:
>
>> Hi Felipe,
>>
>> On 19 October 2016 at 10:37, Baolin Wang wrote:
>>> Currently the Linux kernel does not provide any standard integration of this
>>> feature
Unfortunately the quirk crashed...
[3.985834] pnp 00:01: parse allocated resources
[3.986342] pnp 00:01: PNP0c02: calling
quirk_system_pci_resources+0x0/0x180
[3.987055] pnp 00:01: PNP0c02: calling quirk_intel_mch+0x0/0x1a0
[3.987613] pnp 00:01: PNP0c02: calling
On Fri, Oct 28, 2016 at 10:51:58AM -0500, Yazen Ghannam wrote:
> Currently, we assume that a system has multiple last level caches only if
> there are multiple nodes, and that the cpu_llc_id is equal to the node_id.
> This no longer applies since Fam17h can have multiple last level caches
> within
>>> So back to the original task for you: Show me in the generated output where
>>> the benefits are.
I can offer another bit of information for this software development discussion.
The following build settings were active in my "Makefile" for this Linux test
case.
…
HOSTCFLAGS = -Wall
Hi Matt,
> Need some input for the video pixel data types, which the device we
> are using (see datasheet links below) is outputting pixel data in
> little endian 16-bit of which a 12-bits signed value is used. Does it
> make sense to do some basic processing on the data since greyscale is
>
Implement the new mtd function 'max_bad_blocks'. Using the chip's
bb_per_lun and blocks_per_lun fields to determine the maximum bad blocks
to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/nand/nand_base.c |
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
ONFI compliant chips contain the values for the bb_per_lun and
blocks_per_lun fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
---
For ONFI-compliant NAND devices, the ONFI parameters report the maximum number
of bad blocks per LUN that will be encountered over the lifetime of the device,
so we can use that information to get a more accurate (and smaller) value for
the UBI bad PEB limit.
The ONFI parameter "maxiumum number
On Fri, Oct 28, 2016 at 4:22 PM, Jens Axboe wrote:
> On 10/28/2016 03:32 AM, Linus Walleij wrote:
>>
>> This is without using Bartlomiej's clever hack to pretend we have
>> 2 elements in the HW queue though. His early tests indicate that
>> it doesn't help much: the performance
On Fri, 28 Oct 2016 15:50:10 -0400
Steven Rostedt wrote:
> On Fri, 28 Oct 2016 15:49:22 -0400
> Steven Rostedt wrote:
>
> > Sorry it took so long to look at this, but I finally got around to
> > it ;-)
> >
>
> I did apply patches 1 and 2. I'm
On Fri, 28 Oct 2016 15:49:22 -0400
Steven Rostedt wrote:
> Sorry it took so long to look at this, but I finally got around to
> it ;-)
>
>
> On Fri, 7 Oct 2016 12:47:11 -0400
> Luiz Capitulino wrote:
>
> > With --cpu-list you can do:
> >
> > #
From: David Daney
On arm64 NUMA kernels we can pass "numa=off" on the command line to
disable NUMA. A side effect of this is that kmalloc_node() calls to
non-zero nodes will crash the system with an OOPS:
[0.00] ITS@0x9012: allocated 2097152 Devices
The global utilities block controls power management, I/O device
enabling, power-onreset(POR) configuration monitoring, alternate
function selection for multiplexed signals,and clock control.
This patch adds a driver to manage and access global utilities block.
Initially only reading SVR and
Move mpc85xx.h to include/linux/fsl and rename it to svr.h as a common
header file. This SVR numberspace is used on some ARM chips as well as
PPC, and even to check for a PPC SVR multi-arch drivers would otherwise
need to ifdef the header inclusion and all references to the SVR symbols.
From: Huang Ying
This patch make it possible to charge or uncharge a set of continuous
swap entries in the swap cgroup. The number of swap entries is
specified via an added parameter.
This will be used for the THP (Transparent Huge Page) swap support.
Where a swap cluster backing a THP may be
Add maintainer entry for Freescale SoC drivers including
the QE library and the GUTS driver now. Also add maintainer
for QE library.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
Acked-by: Qiang Zhao
---
Changes for v8:
- Added this patch
Changes for v9:
- Added linux-arm mail
From: Arnd Bergmann
We keep running into cases where device drivers want to know the exact
version of the a SoC they are currently running on. In the past, this has
usually been done through a vendor specific API that can be called by a
driver, or by directly accessing some kind of version
Add the dts node for device configuration unit that provides
general purpose configuration and status for the device.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
---
Changes for v5:
- Added this patch
Changes for v6:
- None
Changes for v7:
- None
Changes for v8:
The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version.
Acturally the right version numbers should be VVN=0x13 and SVN = 0x1.
This patch adds the GUTS driver support for eSDHC driver to match SoC.
And fix host version to avoid that incorrect version numbers break down
the ADMA
On 10/27/2016 08:24 PM, Kirti Wankhede wrote:
>
>
> On 10/27/2016 5:41 PM, Jike Song wrote:
>> On 10/27/2016 05:29 AM, Kirti Wankhede wrote:
>>> Update arguments of vaddr_get_pfn() to take struct mm_struct *mm as input
>>> argument.
>>>
>>> Signed-off-by: Kirti Wankhede
>>> Signed-off-by: Neo
Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/
since it's used by not only PowerPC but also ARM. And add a specification
for 'little-endian' property.
Signed-off-by: Yangbo Lu
Acked-by: Rob Herring
Acked-by: Scott Wood
---
Changes for v4:
- Added this patch
> -Original Message-
> From: Y.B. Lu
> Sent: Friday, October 28, 2016 2:00 PM
> To: 'Scott Wood'; linux-...@vger.kernel.org; ulf.hans...@linaro.org; Arnd
> Bergmann
> Cc: linuxppc-...@lists.ozlabs.org; devicet...@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org;
[...]
>
>> Moreover, I am still trying to understand what's the big deal to why
>> you say no to BFQ as a legacy scheduler. Ideally it shouldn't cause
>> you any maintenance burden and it doesn't make the removal of the
>> legacy blk layer any more difficult, right?
>
>
> Not sure I can state it
> Signed-off-by: Stephen Bates
FYI, that address has bounced throught the whole thread for me,
replacing it with a known good one for now.
> + * This driver is heavily based on drivers/block/pmem.c.
> + * Copyright (c) 2014, Intel Corporation.
> + * Copyright (C) 2007 Nick Piggin
> + *
I'd say please fold this into the previous patch.
Commit-ID: a01aa6c9f40fe03c82032e7f8b3bcf1e6c93ac0e
Gitweb: http://git.kernel.org/tip/a01aa6c9f40fe03c82032e7f8b3bcf1e6c93ac0e
Author: Dmitry Safonov
AuthorDate: Thu, 27 Oct 2016 17:15:15 +0300
Committer: Ingo Molnar
CommitDate: Fri, 28 Oct 2016 08:15:55 +0200
x86/prctl/uapi: Remove
Commit-ID: 24d86f59093b0bcb3756cdf47f2db10ff4e90dbb
Gitweb: http://git.kernel.org/tip/24d86f59093b0bcb3756cdf47f2db10ff4e90dbb
Author: Josh Poimboeuf
AuthorDate: Thu, 27 Oct 2016 08:10:58 -0500
Committer: Ingo Molnar
CommitDate: Fri, 28 Oct 2016 08:16:45 +0200
x86/unwind: Ensure stack
Commit-ID: 67dece7d4c5841e84a3c795e79bf0dcd5be54f55
Gitweb: http://git.kernel.org/tip/67dece7d4c5841e84a3c795e79bf0dcd5be54f55
Author: Dmitry Safonov
AuthorDate: Thu, 27 Oct 2016 17:15:16 +0300
Committer: Ingo Molnar
CommitDate: Fri, 28 Oct 2016 08:15:55 +0200
x86/vdso: Set vDSO
H3 has two SPI controllers. The size of the buffer is 64 * 8.
(8 bit transfer by 64 entry FIFO)
A31 has four controllers. The size of the buffer is 128 * 8.
(8 bit transfer by 128 entry FIFO)
Register maps are sharable, so sun6i SPI driver is reusable with
device configuration.
Use the variable,
H3 SPI has same architecture as A31 except FIFO capacity.
To configure the buffer size separately, compatible property should be
different. Optional DMA specifiers and example are added.
Acked-by: Maxime Ripard
Cc: Mark Brown
Cc: Rob Herring
Cc: Chen-Yu Tsai
Signed-off-by: Milo Kim
---
H3 supports two SPI controllers. Four pins (MOSI, MISO, SCLK, SS) are
configured through the pinctrl subsystem.
Cc: Maxime Ripard
Cc: Chen-Yu Tsai
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/sun8i-h3.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git
Allwinner H3 SPI controller has same architecture as A31.
So most configuration is identical except one thing - FIFO capacity.
A31H3
Number of controllers 4 2
Number of FIFO depth 12864
Transfer bits 8
H3 SPI subsystem is almost same as A31 SPI except buffer size, so those
DT properties are reusable.
Cc: Maxime Ripard
Cc: Chen-Yu Tsai
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/sun8i-h3.dtsi | 32
1 file changed, 32 insertions(+)
diff --git
NanoPi common dtsi supports all components of NEO SBC, so just include it.
Cc: James Pettigrew
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts | 79 +--
1 file changed, 1 insertion(+), 78 deletions(-)
diff --git
This patch provides a common file for NanoPi M1 and Neo SBC.
Those have common features below.
* UART0
* 2 LEDs
* USB host (EHCI3, OHCI3) and PHY
* MicroSD
* GPIO key switch
Cc: James Pettigrew
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/sun8i-h3-nanopi.dtsi | 144
601 - 700 of 1354 matches
Mail list logo