Add clock and reset property for gmac node.
Signed-off-by: Dongpo Li
---
arch/arm/boot/dts/hisi-x5hd2-dkb.dts | 2 ++
arch/arm/boot/dts/hisi-x5hd2.dtsi| 15 +++
2 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/hisi-x5hd2-dkb.dts
b/arch/arm/boot/
On 11 August 2016 at 16:44, Peter Chen wrote:
> On Thu, Aug 11, 2016 at 04:41:27PM +0800, Baolin Wang wrote:
>> >> >>
>> >> >> OK. But that is a real problem. It will pm_runtime_resume() falied
>> >> >> (issued in choose_wakeup()), cause usb controller has powered-off and
>> >> >> xHCI controller
On Thu, Aug 11, 2016 at 12:09 AM, Tejun Heo wrote:
> On Wed, Aug 10, 2016 at 09:55:39PM +0200, Roman Pen wrote:
>> percpu issues some RCU callbacks to synchronize its state, so before
>> freeing we have to wait all those callbacks to finish.
>>
>> E.g. the following simple sequence on stack causes
From: Li Dongpo
The "hix5hd2" is SoC name, add the generic ethernet driver name.
The "hisi-gemac-v1" is the basic version and "hisi-gemac-v2" adds
the SG/TXCSUM/TSO/UFO features.
This patch only adds the SG(scatter-gather) driver for transmitting,
the drivers of other features will be submitted l
Am Donnerstag, den 11.08.2016, 10:51 +0200 schrieb Daniel Vetter:
> On Thu, Aug 11, 2016 at 09:33:26AM +0200, Philipp Zabel wrote:
> > Am Donnerstag, den 04.08.2016, 10:59 +0800 schrieb Bibby Hsieh:
> > > These patches based on 4.7-rc1 to clean up unused function
> > > & variable and use drm core f
>From 2f3f4dda747c0619594d13996e65598ab675c60c Mon Sep 17 00:00:00 2001
From: Bibby Hsieh
Date: Thu, 28 Jul 2016 10:22:54 +0800
Subject: [PATCH] drm/mediatek: Add gamma correction.
Add gamma set function to correct brightness values.
It applies arbitrary mapping curve to compensate the
incorrect
* Aaron Lu wrote:
> This is found by LKP's cyclic performance regression tracking recently
> with the vm-scalability test suite. I have bisected to commit
> 0a7ce4b5a632 ("mm/rmap: share the i_mmap_rwsem"). This commit didn't do
> anything wrong but revealed the irq_call_count problem. IIUC, the
On 08/11/2016 05:13 PM, Ingo Molnar wrote:
>
> * Aaron Lu wrote:
>
>> This is found by LKP's cyclic performance regression tracking recently
>> with the vm-scalability test suite. I have bisected to commit
>> 0a7ce4b5a632 ("mm/rmap: share the i_mmap_rwsem"). This commit didn't do
>> anything wro
"Alex Ng (LIS)" writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Friday, August 5, 2016 3:49 AM
>> To: de...@linuxdriverproject.org
>> Cc: linux-kernel@vger.kernel.org; Haiyang Zhang ; KY
>> Srinivasan ; Alex Ng (LIS)
>> Subject: [PATCH 3/4] D
KY Srinivasan writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Tuesday, August 9, 2016 1:46 AM
>> To: de...@linuxdriverproject.org
>> Cc: linux-kernel@vger.kernel.org; Haiyang Zhang ;
>> KY Srinivasan
>> Subject: [PATCH 0/2] Drivers: hv: vmbus
On Wed, Jul 20, 2016 at 7:58 AM, Andrew Jeffery wrote:
> diff --git a/arch/arm/mach-aspeed/Kconfig b/arch/arm/mach-aspeed/Kconfig
> index 25a0ae01429e..a52de9d3adfb 100644
> --- a/arch/arm/mach-aspeed/Kconfig
> +++ b/arch/arm/mach-aspeed/Kconfig
> @@ -6,6 +6,10 @@ menuconfig ARCH_ASPEED
>
Op 10-08-16 om 16:27 schreef Lyude:
> Since the watermark calculations for Skylake are still broken, we're apt
> to hitting underruns very easily under multi-monitor configurations.
> While it would be lovely if this was fixed, it's not. Another problem
> that's been coming from this however, is th
On Mon, Aug 08, 2016 at 06:24:16PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Hi Greg,
>
> This is the last step in the Sync Framwork de-stage task. It de-stage
> the SW_SYNC validation framework and the sync_debug info debugfs file.
>
> The first 2 patches are clean up and impro
On Wed, Aug 10, 2016 at 12:59:40PM -0500, Reza Arbab wrote:
> On Thu, Aug 04, 2016 at 10:24:04AM +0100, Mel Gorman wrote:
> >[1.713998] Unable to handle kernel paging request for data at address
> >0xff7a1
> >[1.714164] Faulting instruction address: 0xc0270cd0
> >[1.714304]
Update documentation. This limit is unneccessary.
Signed-off-by: Zhen Lei
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/numa.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/numa.txt
b/Documentation/devicetree/bindings/numa.txt
index 21b350
Use the same tactic to cpu and numa-distance nodes.
Signed-off-by: Zhen Lei
---
drivers/of/of_numa.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
index 7b3fbdc..afaeb9c 100644
--- a/drivers/of/of_numa.c
+++ b/drivers/of/of_numa.c
@@ -75,6 +
At present, the distances must equal in both direction for each node
pairs. For example: the distance of node B->A must the same to A->B.
But we really don't have to do this.
End up fill default distances as below:
1. If both direction specified, keep no change.
2. If only one direction specified,
Some numa nodes may have no memory. For example:
1. cpu0 on node0
2. cpu1 on node1
3. device0 access the momory from node0 and node1 take the same time.
So, we can not simply classify device0 to node0 or node1, but we can
define a node2 which distances to node0 and node1 are the same.
Signed-off-
1. MAX_NUMNODES is base on CONFIG_NODES_SHIFT, the default value of the
latter is very small now.
2. Suppose the default value of MAX_NUMNODES is enlarged to 64, so the
size of numa_distance is 4K, it's still acceptable if run the Image
on other processors.
3. It will make function __node_
1. Currently only cpu0 set on cpu_possible_mask and percpu areas have not
been initialized.
2. No reason to limit cpu0 must belongs to node0.
Signed-off-by: Zhen Lei
---
arch/arm64/mm/numa.c | 8
1 file changed, 8 deletions(-)
diff --git a/arch/arm64/mm/numa.c b/arch/arm64/mm/numa.c
From: Kefeng Wang
Use pr_fmt to prefix kernel output, and remove duplicated msg
of NUMA turned off.
Signed-off-by: Kefeng Wang
---
arch/arm64/mm/numa.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/arch/arm64/mm/numa.c b/arch/arm
From: Kefeng Wang
Use of_get_next_parent() instead of open-code.
Signed-off-by: Kefeng Wang
Acked-by: Rob Herring
---
drivers/of/of_numa.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
index 8723f64..ed103e6 100644
--- a/d
If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with
vmalloc_node.
grsecurity has had a similar feature (called
GRKERNSEC_KSTACKOVERFLOW) for a long time.
Cc: Oleg Nesterov
Signed-off-by: Andy Lutomirski
---
arch/Kconfig| 34 +
arch/ia64/includ
Hi all-
Since the dawn of time, a kernel stack overflow has been a real PITA
to debug, has caused nondeterministic crashes some time after the
actual overflow, and has generally been easy to exploit for root.
With this series, arches can enable HAVE_ARCH_VMAP_STACK. Arches
that enable it (just x
If we're using CONFIG_VMAP_STACK and we manage to point an sg entry
at the stack, then either the sg page will be in highmem or sg_virt
will return the direct-map alias. In neither case will the existing
check_for_stack() implementation realize that it's a stack page.
Fix it by explicitly checkin
This allows x86_64 kernels to enable vmapped stacks. There are a
couple of interesting bits.
First, x86 lazily faults in top-level paging entries for the vmalloc
area. This won't work if we get a page fault while trying to access
the stack: the CPU will promote it to a double-fault and we'll die
This warning has been printed in of_numa_parse_cpu_nodes before.
Signed-off-by: Zhen Lei
Acked-by: Rob Herring
---
drivers/of/of_numa.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
index afaeb9c..8723f64 100644
--- a/dr
To make each percpu area allocated from its local numa node. Without this
patch, all percpu areas will be allocated from the node which cpu0 belongs
to.
Signed-off-by: Zhen Lei
---
arch/arm64/Kconfig | 8
arch/arm64/mm/numa.c | 56
This information will be printed in the subfunction numa_add_memblk.
They are not the same, but very similar.
Signed-off-by: Zhen Lei
Acked-by: Rob Herring
---
drivers/of/of_numa.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
index ed5a097..
Hi Fu,
Do you mind if I send IORT series where new drivers/acpi/arm64 directory
would be introduced in first place ? This means your GTDT set would
depend on IORT.
Thanks,
Tomasz
On 26.07.2016 14:19, fu@linaro.org wrote:
From: Fu Wei
This patchset:
(1)Preparation for adding GTDT s
For a normal memory@ devicetree node, its reg property can contains more
memory blocks.
Because we don't known how many memory blocks maybe contained, so we try
from index=0, increase 1 until error returned(the end).
Signed-off-by: Zhen Lei
Acked-by: Rob Herring
---
drivers/of/of_numa.c | 29 +
From: Kefeng Wang
Use pr_fmt to prefix kernel output.
Signed-off-by: Kefeng Wang
Acked-by: Rob Herring
---
drivers/of/of_numa.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
index ed103e6..1234b4a 100644
numa_init(of_numa_init) may returned error because of numa configuration
error. So "No NUMA configuration found" is inaccurate. In fact, specific
configuration error information should be immediately printed by the
testing branch.
Signed-off-by: Zhen Lei
---
arch/arm64/mm/numa.c | 6 +++---
1 fi
v5 -> v6:
Move memblk nid check from arch/arm64/mm/numa.c into drivers/of/of_numa.c,
because this check is arch independent.
This modification only related to patch 3, but impacted the contents of patch 7
and 8,
other patches have no change.
v4 -> v5:
This version has no code changes, just add "
Am Dienstag, den 09.08.2016, 18:41 +0200 schrieb Peter Senna Tschudin:
> Add support to attach a drm_bridge to imx-ldb in addition to
> existing support to attach a LVDS panel.
>
> This patch does a simple code refactoring by moving code
> from for_each_child_of_node iterator to a new function nam
On 08/10/2016 08:16 AM, js1...@gmail.com wrote:
From: Joonsoo Kim
We can make code clean by moving decision condition
for set_page_guard() into set_page_guard() itself. It will
help code readability. There is no functional change.
Signed-off-by: Joonsoo Kim
Acked-by: Vlastimil Babka
From: Akash Goel
relay essentially needs to maintain the per CPU array of channel buffer
pointers but it manually creates that array.
Instead its better to avail the per CPU constructs, provided by the
kernel, to allocate & access the array of pointer to channel buffers.
v2: Include in relay.h
On 08/10/2016 10:14 AM, Sergey Senozhatsky wrote:
@@ -1650,18 +1655,15 @@ static inline void expand(struct zone *zone, struct
page *page,
size >>= 1;
VM_BUG_ON_PAGE(bad_range(zone, &page[size]), &page[size]);
- if (IS_ENABLED(CONFIG_DEBUG_PAGEALLOC)
On Mon, Aug 08, 2016 at 06:24:19PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> The common behaviour for trace headers is to have them in the same folder
> they are used, instead of creating a special trace/ directory.
>
> Signed-off-by: Gustavo Padovan
Reviewed-by: Eric Engestrom
On Mon, Aug 08, 2016 at 06:24:20PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> remove file paths in the comments and add short description about each
> file.
>
> v2: remove file paths instead of just change them.
>
> Signed-off-by: Gustavo Padovan
> ---
> drivers/staging/android
On Mon, Aug 08, 2016 at 06:24:21PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> This interface is hidden from kernel headers and it is intended for use
> only for testing. So testers would have to add the ioctl information
> internally. This is to prevent misuse of this feature.
>
>
On Wed, Aug 10, 2016 at 05:44:55PM -0700, Tim Harvey wrote:
> On Wed, Aug 10, 2016 at 4:41 AM, Mark Brown wrote:
> >> +/* LDO1 always on fixed 0.8V-3.3V via scalar via R1/R2 feeback res */
> >> +static struct regulator_ops ltc3676_fixed_standby_regulator_ops = {
> >> +};
> > Remove this, it's po
Hi everyone:
arm64:
SECTION_SIZE_BITS 30 -1G
The memory hotplug(add_memory -->check_hotplug_memory_range)
must be aligned with section.So I can not add mem with 64M ...
Can I modify the SECTION_SIZE_BITS to 26?
Thanks,
Xishi Qiu
On 11/08/16 09:37, Marc Zyngier wrote:
> On 08/08/16 22:48, Linus Walleij wrote:
>> On Sat, Aug 6, 2016 at 1:45 AM, John Stultz wrote:
>>
>>> @@ -614,7 +615,11 @@ unsigned int irq_create_fwspec_mapping(struct
>>> irq_fwspec *fwspec)
>>> * it now and return the interrupt number.
>
From: Johannes Berg
After Peter's commit (see below) we get a lot of sparse warnings
(one for every rcu_dereference, and more) since the expression
here is assigning to the wrong address space.
Instead of validating that 'p' is a pointer this way, instead make
it fail compilation when it's not b
From: Johannes Berg
This reverts commit fa7d81bb3c269a2ee38b6e4d569d9eb8be1a78ad.
As Peter explained:
[...] lockless_dereference() is _stronger_ than READ_ONCE(), not weaker.
[...]
Also, clue is in the name: 'dereference', you don't actually dereference
the pointer here, only load it.
On 08/10/2016 08:16 AM, js1...@gmail.com wrote:
From: Joonsoo Kim
What debug_pagealloc does is just mapping/unmapping page table.
Basically, it doesn't need additional memory space to memorize something.
But, with guard page feature, it requires additional memory to distinguish
if the page is f
On Mon, Aug 08, 2016 at 06:24:22PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> SW_SYNC allows to run tests on the sync_file framework via debugfs on
>
> /sync/sw_sync
>
> Opening and closing the file triggers creation and release of a sync
> timeline. To create fences on this time
> We have netif_get_num_default_rss_queues() which does this.
Thanks for pointing out the generic API.
Will make changes and resubmit.
From: Jan Östlund
The BQ32K_SECONDS_MASK and BQ32K_MINUTES_MASK both has the same
value. This is no functional change.
Signed-off-by: Daniel Romell
---
drivers/rtc/rtc-bq32k.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-bq32k.c b/drivers/rtc/rtc-bq32k.c
From: Jan Östlund
While the oscillator failure flag is set, the RTC registers
should be considered invalid. bq32k_rtc_read_time() now
returns an error instead of an invalid time.
The failure flag is cleared the next time the clock is set.
Signed-off-by: Daniel Romell
---
drivers/rtc/rtc-bq32k
Hi all,
This is a couple of patches for the bq32000 RTC.
The first one is purely cosmetic, fixing a case where the wrong mask (but
correct value) was used when reading a register value.
The second patch adds a check for a failure flag in the read function. If the
register contents can't be trust
On 10/08/16 22:41, Salah Triki wrote:
> On Tue, Aug 09, 2016 at 11:01:23PM +0100, Luis de Bethencourt wrote:
>> befs_dump_super_block() wasn't giving the inode_size information when
>> dumping all elements of the superblock. Add this element to have complete
>> information of the superblock.
>>
>>
There is at least one Chelsio 10Gb card which uses VPD area to store
some custom blocks (example below). However pci_vpd_size() returns
the length of the first block only assuming that there can be only
one VPD "End Tag" and VFIO blocks access beyond that offset
(since 4e1a63555) which leads to the
On 01/07/16 17:27, Andrew F. Davis wrote:
> Found with scripts/coccinelle/misc/boolconv.cocci.
>
> Signed-off-by: Andrew F. Davis
> ---
> drivers/gpu/drm/omapdrm/dss/dispc.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c
> b/d
For ITS, MSI functionality consists on building domain stack and
during that process we need to reference to domain stack components
e.g. before we create new DOMAIN_BUS_PCI_MSI domain we need to specify
its DOMAIN_BUS_NEXUS parent domain. In order to manage that process
properly, maintain list whi
The series builds the PCI/MSI domain stack based on initial IORT driver
which is added in first place. As a reference please see IORT spec:
http://infocenter.arm.com/help/topic/com.arm.doc.den0049b/DEN0049B_IO_Remapping_Table.pdf
Tested on Cavium ThunderX server and Qualcomm Technologies server pl
There is no point to initialize ITS without having msi-controller
property in corresponding DT node. However, its_probe is checking
msi-controller presence at the end, so we can save our time and do that
check prior to its_probe call. Also, for the code clarity purpose,
we put domain initialization
Firmware agnostic code lands in common functions which do necessary
domain initialization based on unique domain handler. DT specific
code goes to DT specific init call.
Signed-off-by: Tomasz Nowicki
Acked-by: Marc Zyngier
---
drivers/irqchip/irq-gic-v3-its-pci-msi.c | 44 +-
In order to add ACPI support we need to isolate ACPI&DT common code and
move DT logic to corresponding functions. To achieve this we are using
firmware agnostic handle which can be unpacked to either DT or ACPI node.
No functional changes other than a very minor one:
1. Terminate its_init call wit
Let ACPI build ITS PCI MSI domain. ACPI code is responsible for retrieving
inner domain token and passing it on to its_pci_msi_init_one generic
init call.
IORT maintains list of registered domain tokens and allows to find
corresponding domain based on MADT ITS subtable ID info.
Signed-off-by: Tom
ITS is prepared for being initialized different than DT,
therefore we can initialize it in ACPI way. We collect register base
address from MADT table and pass mandatory info to firmware-agnostic
ITS init call.
Use here IORT lib to register ITS domain which then can be found and
used on to build an
On Thu, Aug 11, 2016 at 05:44:46PM +0800, Xishi Qiu wrote:
> arm64:
> SECTION_SIZE_BITS 30 -1G
>
> The memory hotplug(add_memory -->check_hotplug_memory_range)
> must be aligned with section.So I can not add mem with 64M ...
> Can I modify the SECTION_SIZE_BITS to 26?
There was a patch to re
It is possible to provide information about which MSI controller to
use on a per-device basis for DT. This patch supply this with ACPI support.
Currently, IORT is the only one ACPI table which can provide such mapping.
In order to plug IORT into MSI infrastructure we are adding ACPI
equivalents fo
IORT shows representation of IO topology for ARM based systems.
It describes how various components are connected together on
parent-child basis e.g. PCI RC -> SMMU -> ITS. Also see IORT spec.
http://infocenter.arm.com/help/topic/com.arm.doc.den0049b/DEN0049B_IO_Remapping_Table.pdf
Initial support
Hi Shawn,
On 08/09/2016 10:49 AM, Shawn Lin wrote:
> Hi,
>
> On 2016/8/8 18:24, Jaehoon Chung wrote:
>> Hi Shawn,
>>
>> On 08/07/2016 10:33 AM, Shawn Lin wrote:
>>> By default, dw_mmc outputs high level voltage to indicate powering
>>> up the card and outputs low level vcltage to indicate powerin
Hi,
Please consider this patch as Acked-by: Chaitra P B
Thanks,
Chaitra
-Original Message-
From: Greg Edwards [mailto:gedwa...@fireweed.org]
Sent: Saturday, July 30, 2016 9:36 PM
To: Sathya Prakash; Chaitra P B; Suganath Prabu Subramani; James E.J.
Bottomley; Martin K. Petersen
Cc: mpt
2016-08-11 0:52 GMT+08:00 Rik van Riel :
> On Wed, 10 Aug 2016 07:39:08 +0800
> Wanpeng Li wrote:
>
>> The regression is caused by your commit "sched,time: Count actually
>> elapsed irq & softirq time".
>
> Wanpeng, does this patch fix your issue?
I test this against kvm guest (nohz_full, four vC
On 11/08/2016 at 11:59:15 +0200, Daniel Romell wrote :
> From: Jan Östlund
>
> While the oscillator failure flag is set, the RTC registers
> should be considered invalid. bq32k_rtc_read_time() now
> returns an error instead of an invalid time.
>
> The failure flag is cleared the next time the cl
We've clean skb_array in macvtap_put_queue() but still try to pop from
it during macvtap_sock_destruct(). Fix this use after free by moving
the skb array cleanup to macvtap_sock_destruct() instead.
Fixes: 362899b8725b ("macvtap: switch to use skb array")
Reported-by: Cornelia Huck
Tested-by: Corn
Hi,
On 2016/8/11 17:37, Tomasz Nowicki wrote:
Hi Fu,
Do you mind if I send IORT series where new drivers/acpi/arm64 directory
would be introduced in first place ? This means your GTDT set would
depend on IORT.
I think it's reasonable as the IORT for ITS is the key device enablement
for PCI MS
Add runtime-pm and pinctrl support for Tegra I2C driver.
The first 4 patches are trivial clean-up/simplification changes.
Jon Hunter (6):
i2c: tegra: Add missing new line characters
i2c: tegra: Remove non device-tree support
i2c: tegra: Use device name for adapter name
i2c: tegra: Simplif
Add missing new line characters for the various error messages.
Signed-off-by: Jon Hunter
---
drivers/i2c/busses/i2c-tegra.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
index b126dbaa47e3..93b09396a10
Tegra has only supported device-tree for platform/board configuration
for quite some time now and so simplify the Tegra I2C driver by dropping
code for non device-tree platforms/boards.
Signed-off-by: Jon Hunter
---
drivers/i2c/busses/i2c-tegra.c | 10 +++---
1 file changed, 3 insertions(+),
Update the Tegra I2C driver to use runtime PM and move the code in the
tegra_i2c_clock_enable/disable() functions to the PM runtime resume and
suspend callbacks, respectively.
Note that given that CONFIG_PM is not mandatory for Tegra, if CONFIG_PM
is not enabled and so runtime PM is not enabled, e
All Tegra I2C devices have the name "Tegra I2C adapter" which is not
very useful when viewing the I2C adapter names via the sysfs. Therefore,
use the device name, which is unique for each I2C device, instead.
Signed-off-by: Jon Hunter
---
drivers/i2c/busses/i2c-tegra.c | 2 +-
1 file changed, 1
The I2C adapter is unlocked regardless of whether the tegra_i2c_init()
called during the resume is successful or not. However, if the
tegra_i2c_init() is not successful, then ->is_suspended is not set to
false. Simplify the resume code by only setting ->is_suspended to false
if tegra_i2c_init() is
On Tegra124/132 the pins for I2C6 are shared with the Display Port AUX
(DPAUX) channel and on Tegra210 the pins for I2C4 and I2C6 are shared
with DPAUX1 and DPAUX0, respectively. The multiplexing of the pins is
handled by a register in the DPAUX and so the Tegra DPAUX driver has
been updated to reg
Hi Hanjun, Tomasz,
On 11 August 2016 at 18:15, Hanjun Guo wrote:
> Hi,
>
> On 2016/8/11 17:37, Tomasz Nowicki wrote:
>>
>> Hi Fu,
>>
>> Do you mind if I send IORT series where new drivers/acpi/arm64 directory
>> would be introduced in first place ? This means your GTDT set would
>> depend on IORT
Hi Guodong,
On 08/11/2016 11:23 AM, Shawn Lin wrote:
> On 2016/8/10 16:03, Guodong Xu wrote:
>> Dwmmc host controller may in unknown state when entering kernel boot. One
>> example is when booting from eMMC, bootloader need initialize MMC host
>> controller into some state so it can read. In order
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 85e97be32c6242c98dbbc7a241b4a78c1b93327b
commit: 339b19e3c4ff728a5dcdbd388a5fbe83c1aabc37 drm/ast: make fbdev support
really optional
date: 3 weeks ago
config: x86_64-randconfig-b0-08111650 (attached as .c
On Thu, 11 Aug, at 10:52:25AM, Ingo Molnar wrote:
>
> Ok, fine enough to me!
>
> Matt, is patch #5:
>
>[PATCH v2 5/5] x86/efi: Allocate a trampoline if needed in
> efi_free_boot_services()
>
> looking good to you?
Yep, looks good.
Reviewed-by: Matt Fleming
Since gcc does this, it's apparently valid to write
switch (x) {
case __builtin_bswap16(12):
break;
}
but sparse will flag it as an error today.
The constant folding used to be done in the kernel's htons() and
friends, but due to gcc bugs that isn't done anymore since
commit 7322dd755e7d (
Hi Steve,
> From: Steve deRosier [mailto:deros...@gmail.com]
> Sent: Thursday, August 11, 2016 2:39 AM
> To: Amitkumar Karwar
> Cc: Brian Norris; linux-wirel...@vger.kernel.org; Cathy Luo; Nishant
> Sarmukadam; linux-kernel@vger.kernel.org; Wei-Ning Huang
> Subject: Re: mwifiex: PCIe8997 chip spec
On Thu, Aug 11, 2016 at 11:50:21AM +0200, Johannes Berg wrote:
> From: Johannes Berg
>
> This reverts commit fa7d81bb3c269a2ee38b6e4d569d9eb8be1a78ad.
>
> As Peter explained:
> [...] lockless_dereference() is _stronger_ than READ_ONCE(), not weaker.
>
> [...]
>
> Also, clue is in the nam
Debugfs support for PM domains is only enabled if both CONFIG_PM_DEBUG
and CONFIG_PM_ADVANCED_DEBUG are enabled. CONFIG_PM_ADVANCED_DEBUG is
described as "extra PM attributes in sysfs for low-level
debugging/testing" which does not seem related.
Given that the debugfs for PM domains only allows us
From: Austin Christ
According to UEFI 2.6 section 7.5.3, the capsule should be in contiguous
virtual memory and firmware may consume the capsule immediately. To
correctly implement this functionality, the kernel driver needs to vmap
the entire capsule at the time it is made available to firmware.
From: Alex Thorlton
This problem has actually been in the UV code for a while, but we didn't
catch it until recently, because we had been relying on EFI_OLD_MEMMAP
to allow our systems to boot for a period of time. We noticed the issue
when trying to kexec a recent community kernel, where we hit
The util-linux release v2.28.1 is available at
http://ftp.kernel.org/pub/linux/utils/util-linux/v2.28
Feedback and bug reports, as always, are welcomed.
Karel
util-linux 2.28.1 Release Notes
===
agetty:
- call uname() only when necessary [Karel Zak]
-
On Mon, Jul 04, 2016 at 03:46:04PM -0400, Julien Desfossez wrote:
> The effective priority of running threads can also be temporarily
> changed in the PI code, but a dedicated tracepoint is already in place
> to cover this case.
So while we have that tracepoint its not really all that useful.
I w
Please pull the following two patches that fix EFI issues in v4.7.
They're both tagged for stable.
The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linu
Convert dma-buf documentation over to sphinx; also cleanup to
address sphinx warnings.
While at that, convert dma-buf-sharing.txt as well, and make it the
dma-buf API guide.
There is no content change yet; only format conversion and creation of
some hyperlinks.
Sumit Semwal (4):
dma-buf/fence:
Commit 0431b9065f28ecf6c320fefebe0241620049984f ("staging/android: bring
struct sync_pt back") removed child_list and active_list from struct fence,
but left it in kernel doc. Delete them.
Fixes: 0431b9065f28 ("staging/android: bring struct sync_pt back")
Signed-off-by: Sumit Semwal
---
include
Commit e941759c74a44d6ac2eed21bb0a38b21fe4559e2 ("fence: dma-buf
cross-device synchronization (v18)") had a spurious kerneldoc section
header that caused Sphinx to complain. Fix it.
Fixes: e941759c74a4 ("fence: dma-buf cross-device synchronization (v18)")
Signed-off-by: Sumit Semwal
---
include
Convert dma-buf documentation over to sphinx; also cleanup to
address sphinx warnings.
While at that, convert dma-buf-sharing.txt as well, and make it the
dma-buf API guide.
There is no content change yet; only format conversion and creation of
some hyperlinks.
Sumit Semwal (4):
dma-buf/fence:
Branch out dma-buf related documentation into its own rst file to allow
adding it to the sphinx documentation generated.
While at it, move dma-buf-sharing.txt into rst as the dma-buf guide too.
Signed-off-by: Sumit Semwal
---
Documentation/DocBook/device-drivers.tmpl | 37 ---
Documentation/dm
Include dma-buf sphinx documentation into top level index.
Signed-off-by: Sumit Semwal
---
Documentation/index.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/index.rst b/Documentation/index.rst
index 43c722f15292..2fe8e82d7d8c 100644
--- a/Documentation/index.rst
+++ b/D
On 10/08/16 23:12, Salah Triki wrote:
> Check that the allocation group number is not greater or equal to the
> number of allocations group in the file system and return BEF_ERR in the
> case of error.
>
> Signed-off-by: Salah Triki
> ---
> fs/befs/befs.h | 5 +
> 1 file changed, 5 insertion
struct netvsc_device is not suitable for storing VF information as this
structure is being destroyed on MTU change / set channel operation (see
rndis_filter_device_remove()). Move all VF related stuff to struct
net_device_context which is persistent.
Signed-off-by: Vitaly Kuznetsov
---
drivers/n
On Thu, Aug 11, 2016 at 06:22:03PM +0800, Fu Wei wrote:
> Hi Hanjun, Tomasz,
>
> On 11 August 2016 at 18:15, Hanjun Guo wrote:
> > Hi,
> >
> > On 2016/8/11 17:37, Tomasz Nowicki wrote:
> >>
> >> Hi Fu,
> >>
> >> Do you mind if I send IORT series where new drivers/acpi/arm64 directory
> >> would b
101 - 200 of 803 matches
Mail list logo
