Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
init/main.c
between commit:
caba4cbbd27d ("debugobjects: Make kmemleak ignore debug objects")
from the tip tree and commit:
50a7dc046b58 ("mm, page_ext: move page_ext_init() after
page_alloc_init_late()")
On 08/17/2017 09:16 AM, Wenyou Yang wrote:
> Add the configuration of formats: GREY, ARGB444, ARGB555 and ARGB32.
>
> Signed-off-by: Wenyou Yang
> ---
>
> drivers/media/platform/atmel/atmel-isc.c | 22 --
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/d
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/parisc/include/uapi/asm/mman.h
between commit:
1c190151447d ("parisc: Add MADV_HWPOISON and MADV_SOFT_OFFLINE")
from the parisc-hd tree and commit:
115d20ededaf ("mm,fork: introduce MADV_WIPEONFORK")
f
On Mon, Aug 21, 2017 at 05:14:00PM -0500, Brian King wrote:
> Save / restore the retry counter in scsi_cmd in scsi_init_command.
> This allows us to go back through scsi_init_command for retries
> and not forget we are doing a retry.
So where will we initialize it to zero now?
On Mon, Aug 21, 2017 at 05:13:20PM -0500, Brian King wrote:
> Move the initialization of scsi_cmd->jiffies_at_alloc to allocation
> time rather than prep time. Also ensure that jiffies_at_alloc
> is preserved when we go through prep. This lets us send retries
> through prep again and not break the
Hi all,
After merging the spi tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
drivers/spi/spi-imx.c: In function 'spi_imx_buf_rx_swap_u32':
drivers/spi/spi-imx.c:284:15: warning: unused variable 'bytes_per_word'
[-Wunused-variable]
unsigned int bytes_per_word;
Hi, Imran,
Seems the alternatively approach is better than former.
But sorry, I still think, like this kind of "monitoring", its better/easy to
mark some "privileged task" not be monitored, but not list the one should be
monitored.
Because It's easy to know which task should NOT be monitored (f
On 08/22/2017 05:01 AM, Yong wrote:
> Hi Hans,
>
> On Mon, 21 Aug 2017 16:37:41 +0200
> Hans Verkuil wrote:
>
>> Hi Yong,
>>
>> First two high-level comments before I start the review:
>>
>> 1) Can you provide the v4l2-compliance output? I can't merge this unless I
>>see that it passes the c
On Mon, 2017-08-21 at 17:11 -0500, Brian King wrote:
> The following two patches address the hang issue being observed
> with Bart's patch on powerpc. The first patch moves the initialization
> of jiffies_at_alloc from scsi_init_command to scsi_init_rq, and ensures
> we don't zero jiffies_at_alloc
From: Rui Feng
Signed-off-by: Rui Feng
---
drivers/mfd/rts5249.c| 195
drivers/mfd/rtsx_pcr.c | 205 +--
drivers/mfd/rtsx_pcr.h | 11 +++
include/linux/mfd/rtsx_pci.h | 60 +
4 fil
netif_napi_del() should be paired with netif_napi_add(), however no
such call takes place in ftgmac100_probe(). This triggers a NULL
pointer dereference if e.g. no PHY is found by the MDIO probe:
[ 2.77] libphy: Fixed MDIO Bus: probed
[ 2.77] ftgmac100 1e66.ethernet:
The JIT compiler emits ARM 32 bit instructions. Currently, It supports
eBPF only. Classic BPF is supported because of the conversion by BPF core.
This patch is essentially changing the current implementation of JIT compiler
of Berkeley Packet Filter from classic to internal with almost all
instruc
On Tue, Aug 22, 2017 at 11:57 AM, Richard Cochran
wrote:
> On Mon, Aug 21, 2017 at 11:01:12PM +0530, Bhumika Goyal wrote:
>> File ptp_ixp46x.c is not tested as I could not find any architecture
>> to cross compile it.
>
> No problem. Thanks for test compiling the other drivers.
>
By testing I me
On 2017-08-02 11:32, Peter Rosin wrote:
> It simplifies some tests.
>
> Signed-off-by: Peter Rosin
Applied to i2c-mux/for-next
Cheers,
peda
On 2017-08-02 11:50, Peter Rosin wrote:
> Specifically mention what drivers are mux-locked and parent-locked.
>
> Signed-off-by: Peter Rosin
Applied to i2c-mux/for-next
Cheers,
peda
On Mon, Aug 21, 2017 at 04:37:32PM +0530, Arvind Yadav wrote:
> drm_fb_helper_funcs are not supposed to change at runtime.
> All functions working with drm_fb_helper_funcs provided
> by work with const drm_fb_helper_funcs.
> So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
On Mon, Aug 21, 2017 at 01:35:49PM -0700, David Miller wrote:
> I ask because the commit log message indicates that this failure is
> not expected to ever happen on SMP.
I fear my commit message (but not the code) might be wrong.
irq_create_affinity_masks can return NULL any time we don't have any
The JIT compiler emits ARM 32 bit instructions. Currently, It supports
eBPF only. Classic BPF is supported because of the conversion by BPF core.
This patch is essentially changing the current implementation of JIT compiler
of Berkeley Packet Filter from classic to internal with almost all
instruc
The JIT compiler emits ARM 32 bit instructions. Currently, It supports
eBPF only. Classic BPF is supported because of the conversion by BPF core.
This patch is essentially changing the current implementation of JIT compiler
of Berkeley Packet Filter from classic to internal with almost all
instruc
On 2017-08-22 01:45, Boris Brezillon wrote:
Le Thu, 17 Aug 2017 17:37:38 +0530,
Abhishek Sahu a écrit :
* v5:
1. Removed the patches already applied to linux-next and rebased the
remaining patches on [3]
2. Addressed the review comments in v4 and Added Archit Reviewed
by tag.
[3] http:
On Sat, Aug 19, 2017 at 11:58:17PM +0530, Arvind Yadav wrote:
> i2c_device_id are not supposed to change at runtime. All functions
> working with i2c_device_id provided by work with
> const i2c_device_id. So mark the non-const structs as const.
All applied.
btw I think this isn't your first seri
The JIT compiler emits ARM 32 bit instructions. Currently, It supports
eBPF only. Classic BPF is supported because of the conversion by BPF core.
This patch is essentially changing the current implementation of JIT compiler
of Berkeley Packet Filter from classic to internal with almost all
instruc
Wouldn't it make sense to backport the changes to set the virt_boundary
(which probably still is the SG_GAPS flag in such an old kernel)?
On Mon, Aug 21, 2017 at 11:01:12PM +0530, Bhumika Goyal wrote:
> File ptp_ixp46x.c is not tested as I could not find any architecture
> to cross compile it.
No problem. Thanks for test compiling the other drivers.
Acked-by: Richard Cochran
Preserve the module names with Makefile additions.
Signed-off-by: Peter Rosin
---
drivers/mux/Makefile | 5 +
drivers/mux/{mux-adg792a.c => adg792a.c} | 0
drivers/mux/{mux-core.c => core.c} | 0
drivers/mux/{mux-gpio.c => gpio.c} | 0
drivers/mux/{mux-mmio.c
From: Ulrich Hecht
Required for __must_check.
Signed-off-by: Ulrich Hecht
Signed-off-by: Peter Rosin
---
include/linux/mux/consumer.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/mux/consumer.h b/include/linux/mux/consumer.h
index 5577e1b773c4..ea96d4c82be7 100644
--- a
Hi Greg!
I sent these individually a couple of weeks ago, and do not
know if you forgot about them or simply haven't gotten to
them yet. I know that by now it's close to the merge window,
but this is trivial stuff. I'm resending as a series, because
I think that might be easier for you?
Cheers,
P
From: Rob Herring
Now that we have a custom printf format specifier, convert users of
full_name to use %pOF instead. This is preparation to remove storing
of the full path string for each node.
Signed-off-by: Rob Herring
Signed-off-by: Peter Rosin
---
drivers/mux/mux-core.c | 12 ++--
From: Abhisit Sangjan
TI LMP92001 Analog System Monitor and Controller
8-bit GPIOs.
12 DACs with 12-bit resolution.
The GPIOs and DACs are shared port function with Cy function pin to
take control the pin suddenly from external hardware.
DAC's referance voltage selectable for Internal/External.
Make these const as they are only passed to a const argument of the function
omapfb_set_lcd_config.
Also, replace __initdata with __initconst to avoid section conflict error.
Done using Coccinelle.
@match disable optional_qualifier@
identifier s;
@@
static struct omap_lcd_config s = {...};
@ref@
On Mon, Aug 21, 2017 at 10:36:50PM +0530, Bhumika Goyal wrote:
> Make these const as they are only used in a copy operation.
> Done using Coccinelle.
Acked-by: Richard Cochran
On Mon, Aug 21, 2017 at 06:22:10PM +, Vallish Vaidyeshwara wrote:
> AWS Lambda is affected by this change in behavior in
> system call. Following links has more information:
> https://en.wikipedia.org/wiki/AWS_Lambda
Quote:
Unlike Amazon EC2, which is priced by the hour, AWS Lambda is
On Mon, Aug 21, 2017 at 10:42:36AM +0200, Peter Zijlstra wrote:
> On Fri, Aug 18, 2017 at 09:39:16PM -0700, Mathieu Desnoyers wrote:
> > @@ -3295,6 +3301,9 @@ static void __sched notrace __schedule(bool preempt)
> > * Make sure that signal_pending_state()->signal_pending() below
> > * can
The Banana Pi M2 Ultra is an SBC based on the Allwinner V40 SoC (same as
the R40 SoC). The form factor is similar to the Raspberry Pi series.
It features:
- X-Powers AXP221s PMIC connected to i2c0
- 1GiB DDR3 DRAM
- microSD slot
- MicroUSB Type-B port for power and connected to usb0
- HDMI output
From: Chen-Yu Tsai
The Allwinner R40 SoC is marketed as the successor to the A20 SoC.
The R40 is a smaller chip than the A20, but features the same set
of programmable pins, with a couple extra pins and some new pin
functions. The chip features 4 Cortex-A7 cores and a Mali-400 MP2
GPU. It retains
From: Chen-Yu Tsai
The Banana Pi M2 Ultra is an SBC based on the Allwinner R40 SoC. The
form factor and position of various connectors, leds and buttons is
similar to the Banana Pi M1+, Banana Pi M3, and is exactly the same
as the latest Banana Pi M64.
It features:
- X-Powers AXP221s PMIC con
>From: Vineet Gupta [mailto:vineet.gup...@synopsys.com]
>Sent: Monday, August 21, 2017 20:04 PM
>> +
>> +/* Handle an out of bounds mtm hs counter value */ static void __init
>> +handle_mtm_hs_ctr_out_of_bounds_error(uint8_t val) {
>> +pr_err("** The value must be in range [%d,%d] (inclu
On 8/22/2017 7:24 AM, Zhang, Shile (NSB - CN/Hangzhou) wrote:
> Hi, Imran,
>
Hi Shile,
Thanks for getting back on this.
> I think a "unmonitored list" is better than "monitor list", because we want
> khungtaskd can find out the "unexpected" hung task, but not few in a list.
> Then, for the fg ta
This is used to force PHY with USB OTG function to enter a specific
mode, and override OTG VBUS and ID signals.
Signed-off-by: Chunfeng Yun
---
drivers/phy/mediatek/phy-mtk-tphy.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/drivers/phy/mediatek/phy-
Chip bank of version-1 is initialized as NULL, but it's used
by pcie_phy_instance_power_on/off(), so assign it a right
address.
Signed-off-by: Chunfeng Yun
---
drivers/phy/mediatek/phy-mtk-tphy.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/phy/mediatek/phy-mt
Meelis Roos writes:
>> Meelis Roos writes:
>>
>> > I was trying 4.13.0-rc5-00075-gac9a40905a61 on my PowerMac G4 with 1G
>> > RAM and after some time of sddm respawning and X trying to restart,
>> > dmesg is full of messages about vmap allocation failures.
>>
>> Did it just start happening?
On 8/16/2017 10:48 PM, Sricharan R wrote:
+
+struct glink_msg {
+ __le16 cmd;
+ __le16 param1;
+ __le32 param2;
+ u8 data[];
+} __packed;
why we are using extra u8 data[] member here ?
+
+/**
+ * struct glink_defer_cmd - deferred incoming control message
+ * @node:
This patch adds the MFD driver for Dollar Cove TI PMIC (ACPI INT33F5)
that is found on some Intel Cherry Trail devices.
The driver is based on the original work by Intel, found at:
https://github.com/01org/ProductionKernelQuilts
This is a minimal version for adding the basic resources. Currentl
This provides a new input driver for supporting the power button on
Dollar Cove TI PMIC, found on Cherrytrail-based devices.
The patch is based on the original work by Intel, found at:
https://github.com/01org/ProductionKernelQuilts
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=193891
Si
Hi,
this is a patch set to add the support for Dollar Cove TI PMIC found
on some Intel Cherry Trail laptops / tablets. All drivers are based
on the original code from Intel downstream patches, with lots of
rewrites and cleanups. MFD driver is implemented as a stand-alone
like a few other variant
Hi Stephen,
On 08/22/17 at 01:50pm, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got conflicts in:
>
> drivers/iommu/amd_iommu.c
> drivers/iommu/amd_iommu_init.c
> drivers/iommu/amd_iommu_proto.h
> drivers/iommu/amd_iommu_types.h
>
> between commits:
>
This patch adds the opregion driver for Dollar Cove TI PMIC on Intel
Cherry Trail devices. The patch is based on the original work by
Intel, found at:
https://github.com/01org/ProductionKernelQuilts
with many cleanups and rewrites.
The driver is currently provided only as built-in to follow
On Mon, Aug 21, 2017 at 03:07:57PM +0100, Juri Lelli wrote:
> > Consider a 4 core, SMT2 system:
> >
> > LLC [0 - 7]
> >
> > SMT [0,1] [2,3] [4,5] [6,7]
> >
> > If we do a wake-up on CPU0, we'll find CPU1, mark that as fallback,
> > continue up the domain tree, exclude 0,1 from 0-
On Mon, Aug 21, 2017 at 02:44:58PM +0100, Juri Lelli wrote:
> Hi,
> On 18/08/17 17:21, Byungchul Park wrote:
> > It would be better to try to check other siblings first if
> > SD_PREFER_SIBLING is flaged when pushing tasks - migration.
> >
> > Signed-off-by: Byungchul Park
>
> Mmm, this looks li
On Mon, Aug 21, 2017 at 05:46:00PM +0200, Peter Zijlstra wrote:
>
>
> Booting the very latest -tip on my test machine gets me the below splat.
>
> Dave, TJ, FYI, lockdep grew annotations for completions; it remembers
> which locks were taken before we complete() and checks none of those are
> he
Hi Boris,
2017-08-22 14:37 GMT+09:00 Boris Brezillon :
> Le Tue, 22 Aug 2017 11:56:14 +1000,
> Stephen Rothwell a écrit :
>
>> Hi Brian,
>>
>> Today's linux-next merge of the l2-mtd tree got a conflict in:
>>
>> include/asm-generic/vmlinux.lds.h
>>
>> between commit:
>>
>> cb87481ee89d ("kbu
On Sun, 2017-08-13 at 16:54 +0200, Julia Lawall wrote:
> Hello,
Hello, sorry for the delayed response.
>
> At the suggestion of Christoph Hellwig, I am working on inlining the
> functions stored in the err_handler field of a pci_driver structure into
> the pci_driver structure itself. A number
Le Tue, 22 Aug 2017 11:56:14 +1000,
Stephen Rothwell a écrit :
> Hi Brian,
>
> Today's linux-next merge of the l2-mtd tree got a conflict in:
>
> include/asm-generic/vmlinux.lds.h
>
> between commit:
>
> cb87481ee89d ("kbuild: linker script do not match C names unless
> LD_DEAD_CODE_DATA
Hi Vinod,
After merging the slave-dma tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/dma/dmaengine.h:9:0,
from drivers/dma/altera-msgdma.c:27:
drivers/dma/altera-msgdma.c: In function 'msgdma_probe':
drivers/dma/altera-msgdma.
From: Long Li
This patch is for linux-stable 4.1 branch only.
storvsc checks the SG list for gaps before passing them to Hyper-v device.
If there are gaps, data is copied to a bounce buffer and a continuous data
buffer is passed to Hyper-V.
The check on gaps assumes SG list is continuous, and n
Allwinner R40 is a new SoC, with Quad Core Cortex-A7 and peripherals
like A20.
Add support for it.
Signed-off-by: Icenowy Zheng
---
Changes in v2:
- Fix alphabetical orders.
Documentation/arm/sunxi/README | 6 ++
Documentation/devicetree/bindings/arm/sunxi.txt | 1 +
arch/
The Allwinner V3s SoC is not quad-core, but single-core.
Fix this in the README file.
Fixes: b074fede01c0 ("arm: sunxi: add support for V3s SoC")
Signed-off-by: Icenowy Zheng
---
Documentation/arm/sunxi/README | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/Document
On Tuesday 22 August 2017 06:47 AM, Franklin S Cooper Jr wrote:
>
>
> On 08/21/2017 04:05 AM, Sekhar Nori wrote:
>> On Thursday 17 August 2017 03:47 AM, Franklin S Cooper Jr wrote:
>>
>>> @@ -802,7 +821,6 @@ static int davinci_i2c_probe(struct platform_device
>>> *pdev)
>>> dev->clk = devm_c
The compatible string for Allwinner V3s SoC used to be missing.
Add it to the binding document.
Fixes: b074fede01c0 ("arm: sunxi: add support for V3s SoC")
Signed-off-by: Icenowy Zheng
---
Documentation/devicetree/bindings/arm/sunxi.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Docume
Hi
On Tuesday 22 August 2017 01:50 AM, Dan Carpenter wrote:
Don't say "[PATCH 4/4]". It's not a patchset or a part of an email
thread.
Yes, It's part of these patchset.
[PATCH 1/4] misc: apds9802als: constify i2c_device_id
[PATCH 2/4] misc: hmc6352: constify i2c_device_id
[PATCH 3/4] mi
On Mon, Aug 21, 2017 at 05:46:00PM +0200, Peter Zijlstra wrote:
> Now given the above observance rule and the fact that the below report
> is from the complete, the thing that happened appears to be:
>
>
> lockdep_map_acquire(&work->lockdep_map)
> down_write(&A)
>
>
在 2017-08-21 17:34，Maxime Ripard 写道：
Hi,
On Sun, Aug 20, 2017 at 01:29:57PM +0800, Icenowy Zheng wrote:
Allwinner R40 is a new SoC, with Quad Core Cortex-A7 and peripherals
like A20.
Add support for it.
Signed-off-by: Icenowy Zheng
---
Documentation/arm/sunxi/README | 6 +++
Rob Herring writes:
> In preparation to remove the full path from device_node.full_name, use
> of_find_node_by_path instead of open coding with strcmp.
>
> Signed-off-by: Rob Herring
> Cc: Benjamin Herrenschmidt
> Cc: Paul Mackerras
> Cc: Michael Ellerman
> Cc: linuxppc-...@lists.ozlabs.org
>
Hi Andy,
On 08/18/2017 05:38 AM, Andy Shevchenko wrote:
On Tue, Aug 1, 2017 at 9:13 PM,
wrote:
From: Kuppuswamy Sathyanarayanan
Currently intel_scu_ipc.c, intel_pmc_ipc.c and intel_punit_ipc.c
redundantly implements the same IPC features and has lot of code
duplication between them. This dr
Hi Kishon,
After merging the phy-next tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/phy/ralink/phy-ralink-usb.c: In function 'ralink_usb_phy_probe':
drivers/phy/ralink/phy-ralink-usb.c:195:13: warning: cast from pointer to
integer of different size [-Wpointe
Hi,
On 08/18/2017 05:24 AM, Andy Shevchenko wrote:
On Tue, Aug 1, 2017 at 9:13 PM,
wrote:
From: Kuppuswamy Sathyanarayanan
This patch cleans up unnecessary free/alloc calls in this driver
by using devm_* calls.
static int ipc_plat_remove(struct platform_device *pdev)
{
- struct re
Hi Greg,
On Monday 21 August 2017 06:15 PM, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the phy pull request for 4.14 merge window below.
>
> It adds a new USB phy driver for Ralink SoC, add support for PCIe and
> SATA PHY in phy-mt65xx-usb3 driver, add support for allwinner A83T
>
Hi Andy,
On 08/18/2017 05:29 AM, Andy Shevchenko wrote:
On Tue, Aug 1, 2017 at 9:13 PM,
wrote:
Currently, we have lot of repetitive code in dependent device resource
allocation and device creation handling code. This logic can be improved if
we use MFD framework for dependent device creation
>
> >> I think with this patch from -rc6 the symptoms should be cured:
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c005390374957baacbc38eef96ea360559510aa7
> >>
> >> if that theory is right.
> >
> > The result with 4.13-rc6 is positive but mixed: the
Hi Andy,
On 08/18/2017 05:22 AM, Andy Shevchenko wrote:
On Tue, Aug 1, 2017 at 9:13 PM,
wrote:
From: Kuppuswamy Sathyanarayanan
This patch adds proper error handling for failure cases in
ipc_pci_probe() function.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
drivers/platform/x86/intel_
Hi Greg,
Stephen Rothwell reported a issue with my previous pull request
w.r.t missing Signed-off-by committer. I've fixed that in this pull
request.
It adds a new USB phy driver for Ralink SoC, add support for PCIe and
SATA PHY in phy-mt65xx-usb3 driver, add support for allwinner A83T
USB PHY an
Hi Peter,
On Mon, Aug 21, 2017 at 2:14 PM, Peter Zijlstra wrote:
> On Mon, Aug 21, 2017 at 04:21:28PM +0100, Brendan Jackman wrote:
>> The current use of returning NULL from find_idlest_group is broken in
>> two cases:
>>
>> a1) The local group is not allowed.
>>
>>In this case, we currently
Hi Mark,
thanks for your reply.
On 08/22/2017 01:31 AM, Mark Brown wrote:
On Fri, Aug 18, 2017 at 11:03:46PM +0800, jeffy wrote:
when using legacy dai naming, the dai->name for rt5514-spi would be the dev
name, which is spi2.0 with my local 4.4 kernel, and would be spi32765.0 with
upstream ke
Hi Arnaldo, Will,
are there any comments on this series?
On Wed, Aug 16, 2017 at 12:40 PM, Ganapatrao Kulkarni
wrote:
> Extending json/jevent framework for parsing arm64 event files.
> Adding jevents for ThunderX2 implementation defined PMU events.
>
> v5:
>- Addressed comments from Arnaldo
Hi all,
Today's linux-next merge of the rcu tree got a conflict in:
arch/x86/mm/tlb.c
between commit:
94b1b03b519b ("x86/mm: Rework lazy TLB mode and TLB freshness tracking")
from the tip tree and commit:
3ed668659e95 ("membarrier: Document scheduler barrier requirements")
from the rcu
From: Icenowy Zheng
Some RTL8211E chips have broken GbE function, which needs a hack to
fix. It's said that this fix will affect the performance on not-buggy
PHYs, so it should only be enabled on boards with the broken PHY.
Currently only some Pine64+ boards are known to have this issue.
This ha
From: Icenowy Zheng
The page select register also exists on RTL8211E PHY (although it
behaves slightly differently).
Change the register macro name to remove the F.
Signed-off-by: Icenowy Zheng
---
drivers/net/phy/realtek.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
d
Some Pine64+ boards have a broken RTL8211E PHY, which cannot work
reliably in 1000Base-T mode with default configuration.
A solution is passed to Pine64, which is said to be disabling the
internal RX delay of the PHY.
Enable the hack by set the PHY mode to RGMII-TXID.
Signed-off-by: Icenowy Zhen
Some boards uses a PHY with internal delay with an Allwinner SoC.
Support these PHY modes in the driver.
As the driver has no configuration registers for these modes, just treat
them as ordinary RGMII.
Signed-off-by: Icenowy Zheng
---
drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c | 3 +++
Some Pine64+ boards come with bad RTL8211E PHYs, which cannot work reliably
unless do some hack. According to Pine64 people, Realtek describes the hack
as totally disabling RX delay, and it's not documented at all.
This patchset introduces the workaround on Pine64+.
The first patch adds RGMII var
Hi all,
Today's linux-next merge of the tip tree got conflicts in:
drivers/iommu/amd_iommu.c
drivers/iommu/amd_iommu_init.c
drivers/iommu/amd_iommu_proto.h
drivers/iommu/amd_iommu_types.h
between commits:
4c232a708be1 ("iommu/amd: Detect pre enabled translation")
9494ea90a56d ("Reve
Do you need a personal/business L0AN, if yes contact Softlink Int'L for more
info
Add a common device tree for all Nuvoton NPCM750 BMCs and a board
specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by: Brendan Higgins
---
.../devicetree/bindings/arm/npcm/npcm.txt | 6 +
arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 63 ++
arch/ar
Hello Lee,
Gentle ping. Do you see any issues with the following change?
Thanks,
Furquan
On Sun, Jul 23, 2017 at 11:02 PM, Furquan Shaikh wrote:
>
> Commit 274e43edcda6f ("mfd: intel-lpss: Do not put device in reset
> state on suspend") changed the behavior on suspend by not putting LPSS
> cont
Add maintainers and reviewers for the Nuvoton NPCM architecture.
Signed-off-by: Brendan Higgins
---
MAINTAINERS | 13 +
1 file changed, 13 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 44cb004c765d..67064bf11904 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1598,6 +159
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/firmware/efi/libstub/arm64-stub.c
between commit:
170976bcab07 ("efi/arm64: add EFI_KIMG_ALIGN")
from the arm64 tree and commit:
0426a4e68f18 ("efi/libstub/arm64: Force 'hidden' visibility for section
markers")
Adds basic support for the Nuvoton NPCM750 BMC.
Signed-off-by: Brendan Higgins
---
arch/arm/Kconfig | 2 +
arch/arm/Makefile| 1 +
arch/arm/mach-npcm/Kconfig | 60 +++
arch/arm/mach-npcm/Makefile | 3 +
arch/arm/mach-npcm/headsmp.S | 120
This patch set adds support for the Nuvoton NPCM Baseboard Management Controller
(BMC) SoC architecture as well as the NPCM750 variant. NPCM is an ARM based SoC
with external DDR RAM and supports a large set of peripherals.
The NPCM750 is based on Cortex A9 and comes in single core and dual core
f
On 2017年08月15日 17:58, Mel Gorman wrote:
> On Tue, Aug 15, 2017 at 04:45:36PM +0800, Kemi Wang wrote:
>> Threshold CPU cyclesThroughput(88 threads)
>> 32 799 241760478
>> 64 640 301628829
>> 125 537 358906028 <==> system by de
Currently we are handling pcie wake irq in mrvl wifi driver.
Move it to rockchip pcie driver for Gru boards.
Signed-off-by: Jeffy Chen
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 15 +--
1 file changed, 9 insertions
Add an optional interrupt for PCIE_WAKE pin.
Signed-off-by: Jeffy Chen
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
.../devicetree/bindings/pci/rockchip-pcie.txt| 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/Documentation/de
Fix error handlings in probe & resume.
Signed-off-by: Jeffy Chen
---
Changes in v4:
Rebase on newest for-next branch, also fix error handling by:
1e7f570a1b86 PCI: rockchip: Idle inactive PHY(s)
Changes in v3: None
Changes in v2: None
drivers/pci/host/pcie-rockchip.c | 160 +++
Currently we are handling pcie wake in mrvl wifi driver. But Brian
suggests to move it into rockchip pcie driver.
Tested on my chromebook bob(with cros 4.4 kernel and mrvl wifi).
Changes in v4:
Rebase on newest for-next branch, also fix error handling by:
1e7f570a1b86 PCI: rockchip: Idle inacti
Add support for PCIE_WAKE pin in rockchip pcie driver.
Signed-off-by: Jeffy Chen
---
Changes in v4: None
Changes in v3:
Fix error handling
Changes in v2:
Use dev_pm_set_dedicated_wake_irq
-- Suggested by Brian Norris
drivers/pci/host/pcie-rockchip.c | 21 +++--
1 file
There is a problem that when counting the pages for creating
the hibernation snapshot will take significant amount of
time, especially on system with large memory. Since the counting
job is performed with irq disabled, this might lead to NMI lockup.
The following warning were found on a system with
Hi Hans,
On Mon, 21 Aug 2017 16:37:41 +0200
Hans Verkuil wrote:
> Hi Yong,
>
> First two high-level comments before I start the review:
>
> 1) Can you provide the v4l2-compliance output? I can't merge this unless I
>see that it passes the compliance tests. Make sure you compile from the gi
> -Original Message-
> From: Waiman Long [mailto:long...@redhat.com]
> Sent: Monday, August 21, 2017 9:35 PM
> To: Wangkai (Kevin,C); Alexander Viro; Jonathan Corbet
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> linux-fsde...@vger.kernel.org; Paul E. McKenney; Andrew Mo
Hi Andrew,
On Mon, Aug 21, 2017 at 01:26:00PM -0700, Andrew Morton wrote:
> On Mon, 21 Aug 2017 23:08:18 +0800 Chen Yu wrote:
>
> > There is a problem that when counting the pages for creating
> > the hibernation snapshot will take significant amount of
> > time, especially on system with large m
On Fri, Aug 18, 2017 at 04:09:49PM +0800, Sandy Huang wrote:
> This patch add Document for Rockchip Soc RK3288 LVDS,
> This based on the patches from Mark yao and Heiko Stuebner.
>
> Signed-off-by: Sandy Huang
> Signed-off-by: Mark yao
> Signed-off-by: Heiko Stuebner
> ---
> Changes:
> - us
On Fri, Aug 18, 2017 at 08:20:45AM +0200, Mylène Josserand wrote:
> Add the Cypress TrueTouch Generation 5 touchscreen device tree bindings
> documentation. It can use I2C or SPI bus.
> This touchscreen can handle some defined zone that are designed and
> sent as button. To be able to customize the
1 - 100 of 988 matches
Mail list logo
