On Mon, Feb 04, 2019 at 06:21:39PM +, Christopher Lameter wrote:
> On Mon, 4 Feb 2019, Jason Gunthorpe wrote:
>
> > On Mon, Feb 04, 2019 at 05:14:19PM +, Christopher Lameter wrote:
> > > Frankly I still think this does not solve anything.
> > >
> > > Concurrent write access from two
From: Qingmin Liu
When PIPEMIX=1, change the operation from 2x8 EP to 1x8 EP + 1x8 RC.
Signed-off-by: Qingmin Liu
Signed-off-by: Ray Jui
---
drivers/phy/broadcom/phy-bcm-sr-pcie.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/phy/broadcom/phy-bcm-sr-pcie.c
On 2/4/19 9:49 AM, Thomas Gleixner wrote:
> On Fri, 1 Feb 2019, Fenghua Yu wrote:
>> This option behaves like existing kernel option clearcpuid.
>
> No it does NOT. clearcpuid allows to disable things.
>
> This allows to enable random CPUID bits without any sanity checking. Not
> going to
The ingenic-nand driver uses an API provided by the jz4780-bch driver.
This makes it difficult to support other SoCs in the jz4780-bch driver.
To work around this, we separate the API functions from the SoC-specific
code, so that these API functions are SoC-agnostic.
Signed-off-by: Paul Cercueil
Before adding support for more SoCs and seeing the number of files for
these drivers grow, we move them to their own subfolder to keep it tidy.
Signed-off-by: Paul Cercueil
---
Changes:
v2: New patch
v3: No change
drivers/mtd/nand/raw/Kconfig | 14 +-
Use SPDX license notifiers instead of GPLv2 license text in the headers.
Signed-off-by: Paul Cercueil
Reviewed-by: Boris Brezillon
---
Changes:
v2: No changes
v3: No changes
drivers/mtd/nand/raw/ingenic/jz4780_bch.c | 5 +
drivers/mtd/nand/raw/ingenic/jz4780_bch.h | 5 +
The Ben Nanonote from Qi Hardware expects a specific OOB layout on its
NAND.
Signed-off-by: Paul Cercueil
---
Changes:
v2: New patch
v3: Use the qi,lb60 layout unconditionally if we detect that we're
running on that board.
drivers/mtd/nand/raw/ingenic/ingenic_nand.c | 41
The boot ROM of the JZ4725B SoC expects a specific OOB layout on the
NAND, so we use it unconditionally in the ingenic-nand driver.
Also add the jz4725b-bch driver to support the JZ4725B-specific BCH
hardware.
Signed-off-by: Paul Cercueil
---
Changes:
v2: Instead of forcing the OOB layout,
The JZ4740 ECC hardware is not BCH but Reed-Solomon, so it makes more
sense to use the more generic ECC term.
Signed-off-by: Paul Cercueil
---
Changes:
v3: New patch
.../devicetree/bindings/mtd/ingenic,jz4780-nand.txt| 18 +-
1 file changed, 9 insertions(+), 9
The jz4780_nand driver will be modified to handle all the Ingenic
JZ47xx SoCs that the upstream Linux kernel supports (JZ4740, JZ4725B,
JZ4770, JZ4780), so it makes sense to rename it.
Signed-off-by: Paul Cercueil
---
Changes:
v3: New patch
drivers/mtd/nand/raw/ingenic/Makefile
Add support for probing the ingenic-nand driver on the JZ4740 SoC from
Ingenic, and the jz4740-ecc driver to support the JZ4740-specific
ECC hardware.
Signed-off-by: Paul Cercueil
---
Changes:
v2: New patch
v3: Also add support for the hardware ECC of the JZ4740 in this patch
Add compatible strings to probe the jz4780-nand and jz4780-bch drivers
from devicetree on the JZ4725B and JZ4740 SoCs from Ingenic.
Signed-off-by: Paul Cercueil
---
Changes:
v2: - Change 'ingenic,jz4725b-nand' compatible string to
'ingenic,jz4740-nand' to reflect driver change
- Add
From: Colin Ian King
Variable count is never zero inside the loop so the check if count is
zero is redundant and can be removed. Fix this.
Detected by CoverityScan, CID#1466880 ("Logically dead code")
Signed-off-by: Colin Ian King
---
drivers/bluetooth/h4_recv.h | 3 ---
1 file changed, 3
On 2/4/19 10:45 AM, Fenghua Yu wrote:
> On Mon, Feb 04, 2019 at 10:41:40AM -0800, Dave Hansen wrote:
>> On 2/1/19 9:14 PM, Fenghua Yu wrote:
>>> --- a/arch/x86/include/asm/cpufeatures.h
>>> +++ b/arch/x86/include/asm/cpufeatures.h
>>> @@ -221,6 +221,7 @@
>>> #define X86_FEATURE_ZEN
On 2/4/2019 1:15 PM, Borislav Petkov wrote:
On Mon, Feb 04, 2019 at 11:55:27AM -0500, Liang, Kan wrote:
We cannot apply X86_STEPPING_ANY to ignore the stepping. There will be
problems for 0-8 stepping for KABYLAKE_MOBILE.
So why are we even doing this new "interface"
On Mon, Feb 4, 2019 at 3:41 AM Jiri Olsa wrote:
>
> On Mon, Feb 04, 2019 at 02:29:56PM +0300, Alexey Budankov wrote:
> > On 04.02.2019 13:36, Jiri Olsa wrote:
> > > On Mon, Feb 04, 2019 at 01:12:11PM +0300, Alexey Budankov wrote:
> > >>
> > >> Hi,
> > >>
> > >> On 03.02.2019 18:30, Jiri Olsa
Hi Daniel
On Mon, Feb 04, 2019 at 11:31:14AM +0100, Daniel Vetter wrote:
> Noticed why wonder what vboxvideo is using the ->master_set/drop hooks
> for.
Can you improve the gammar a little, I find it hard to read.
>
> Signed-off-by: Daniel Vetter
> Cc: Greg Kroah-Hartman
> Cc: Fabio Rafael da
On Mon, Feb 4, 2019 at 9:49 AM Stanislav Fomichev wrote:
>
> On 02/01, Dmitry Vyukov wrote:
> > Hello,
> >
> > The following program leads to an unkillable process that eats CPU in
> > an infinite loop in BPF_PROG_TEST_RUN syscall. But kernel does not
> > self-detect cpu/rcu/task stalls either.
Need to retouch your photos? Deep etching or masking for your photos?
We are the studio who can do those service for your photos.
Please send photos to start
Thanks,
Stacy
Wedmar
Leddmgo
On Mon, Feb 04, 2019 at 10:41:40AM -0800, Dave Hansen wrote:
> On 2/1/19 9:14 PM, Fenghua Yu wrote:
> > --- a/arch/x86/include/asm/cpufeatures.h
> > +++ b/arch/x86/include/asm/cpufeatures.h
> > @@ -221,6 +221,7 @@
> > #define X86_FEATURE_ZEN( 7*32+28) /* "" CPU is AMD
> >
From: Alice Ferrazzi
As a result of an unsupported operation is better to use EOPNOTSUPP
as error code.
ENOSYS is only used for 'invalid syscall nr' and nothing else.
Signed-off-by: Alice Ferrazzi
---
Changes v1->v2:
- Use EOPNOTSUPP instead of ENOTSUPP (Petr)
kernel/livepatch/core.c | 2 +-
Hi Daniel
On Mon, Feb 04, 2019 at 11:31:13AM +0100, Daniel Vetter wrote:
> The compiler already clears this for us.
>
> More important, someone might look what this is actually used for,
> and freak out about the dragon staring back at them.
>
> Signed-off-by: Daniel Vetter
> Cc: Greg
04.02.2019 19:17, Thierry Reding пишет:
> On Mon, Feb 04, 2019 at 05:28:23PM +0300, Dmitry Osipenko wrote:
>> 04.02.2019 17:00, Thierry Reding пишет:
>>> On Mon, Feb 04, 2019 at 03:03:49PM +0300, Dmitry Osipenko wrote:
04.02.2019 14:05, Thierry Reding пишет:
> On Mon, Feb 04, 2019 at
On 02/04/2019 07:18 AM, Peter Zijlstra wrote:
> On Mon, Feb 04, 2019 at 10:02:11AM +0100, Juri Lelli wrote:
>> On 18/01/19 17:46, Juri Lelli wrote:
>>> On 18/01/19 08:17, Tejun Heo wrote:
On Thu, Jan 17, 2019 at 09:47:34AM +0100, Juri Lelli wrote:
> Hi,
>
> v6 of a series of
Hi Ronald,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on input/next]
[also build test ERROR on v5.0-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 2/3/19 10:39 PM, Marcel Holtmann wrote:
Hi Shuah,
tty_set_termios() has the following WARN_ON which can be triggered with a
syscall to invoke TIOCSETD __NR_ioctl.
WARN_ON(tty->driver->type == TTY_DRIVER_TYPE_PTY &&
tty->driver->subtype == PTY_TYPE_MASTER);
Reference:
On 04.02.2019 17:42, Thierry Reding wrote:
> From: Thierry Reding
>
> Read MAC address 32-bit at a time and manually extract the individual
> bytes. This avoids pointer aliasing and gives the compiler a better
> chance of optimizing the operation.
>
> Suggested-by: Andrew Lunn
> Signed-off-by:
* Andreas Kemnade [190204 18:33]:
> On Mon, 4 Feb 2019 07:56:04 -0800
> Tony Lindgren wrote:
>
> > * Andreas Kemnade [190202 06:01]:
> > > Enabling off mode was only reachable deeply hidden
> > > in the debugfs. As powersaving is an important feature,
> > > move the option out of its shady
Hi Joe.
> My preference would also convert all the
> DRM_DEV_ uses to drm_dev_ eventually.
>
> Also, the macros themselves could change to use a
> more consistent mechanism.
>
> This would make the drm logging mechanisms more like
> other logging mechanisms used in the kernel.
>
> Something
On Tue, 29 Jan 2019 at 05:29, Leo Yan wrote:
>
> This patch seris adds support for sample flags so can facilitate perf
> to print sample flags for branch instruction.
>
> Patch 0001 is used to save last branch information in packet structure,
> this includes instruction type, subtype and
On 2/1/19 9:14 PM, Fenghua Yu wrote:
> --- a/arch/x86/include/asm/cpufeatures.h
> +++ b/arch/x86/include/asm/cpufeatures.h
> @@ -221,6 +221,7 @@
> #define X86_FEATURE_ZEN ( 7*32+28) /* "" CPU is AMD
> family 0x17 (Zen) */
> #define X86_FEATURE_L1TF_PTEINV (
Fix reversed logic while actionpoints configuration (full/min)
detection.
Fixies: 7dd380c338f1e ("ARC: boot log: print Action point details")
Signed-off-by: Eugeniy Paltsev
---
arch/arc/kernel/setup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arc/kernel/setup.c
ttm_fbdev_mmap() just doesn't work. It appears to work fine, mmap()
returns success, but any attempt to actually access the mapping causes a
SIGBUS.
We can just use drm_gem_prime_mmap() instead. Almost. We have to copy
over the start offset from the ttm_buffer_object vm_node to the
On Mon, 4 Feb 2019 07:56:04 -0800
Tony Lindgren wrote:
> * Andreas Kemnade [190202 06:01]:
> > Enabling off mode was only reachable deeply hidden
> > in the debugfs. As powersaving is an important feature,
> > move the option out of its shady place.
>
> How about let's enable always if we
Need to retouch your photos? Deep etching or masking for your photos?
We are the studio who can do those service for your photos.
Please send photos to start
Thanks,
Stacy
Wesdl
Saarloduis
Hi Ronald,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on input/next]
[also build test ERROR on v5.0-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Mon, Feb 04, 2019 at 08:03:37AM -0800, Bjorn Andersson wrote:
> We have a regulator that is described as 1.05V in the schematics for the
> board we're working on and we have the USB block wanting 1.05V on one of
> its pins. But the particular regulator works in steps of 8mV, and the
>
On Monday 04 Feb 2019 at 10:03:03 (-0800), Matthias Kaehlcke wrote:
> There is the option to remove the OPP check from the cpufreq drivers
> and instead return an error from dev_pm_opp_of_register_em(), but with
> the more complex error handling it might be more hassle than it's
> worth.
Agreed.
On Mon, 4 Feb 2019, Jason Gunthorpe wrote:
> On Mon, Feb 04, 2019 at 05:14:19PM +, Christopher Lameter wrote:
> > Frankly I still think this does not solve anything.
> >
> > Concurrent write access from two sources to a single page is simply wrong.
> > You cannot make this right by allowing
From: Alexander Duyck
This patch adds the flag named kvm-pv-unused-page-hint. This functionality
is enabled by kvm for x86 and provides a mechanism by which the guest can
indicate to the host which pages it is no longer using. By providing these
hints the guest can help to reduce the memory
On Sun, Feb 03, 2019 at 09:21:33PM -0800, john.hubb...@gmail.com wrote:
> +/*
> + * GUP_PIN_COUNTING_BIAS, and the associated functions that use it, overload
> + * the page's refcount so that two separate items are tracked: the original
> page
> + * reference count, and also a new count of how
Christoph Hellwig writes:
> On Tue, Jan 29, 2019 at 09:36:08PM -0500, Michael S. Tsirkin wrote:
>> This has been discussed ad nauseum. virtio is all about compatibility.
>> Losing a couple of lines of code isn't worth breaking working setups.
>> People that want "just use DMA API no tricks"
From: Alexander Duyck
Add guest support for providing free memory hints to the KVM hypervisor for
freed pages huge TLB size or larger. I am restricting the size to
huge TLB order and larger because the hypercalls are too expensive to be
performing one per 4K page. Using the huge TLB order became
From: Alexander Duyck
Because the implementation was limiting itself to only providing hints on
pages huge TLB order sized or larger we introduced the possibility for free
pages to slip past us because they are freed as something less then
huge TLB in size and aggregated with buddies later.
To
This patch set provides a mechanism by which guests can notify the host of
pages that are not currently in use. Using this data a KVM host can more
easily balance memory workloads between guests and improve overall system
performance by avoiding unnecessary writing of unused pages to swap.
In
* Roger Quadros [190204 14:23]:
> From: "Andrew F. Davis"
>
> The Programmable Real-Time Unit Subsystem (PRUSS) contains an
> interrupt controller (INTC) that can handle various system input
> events and post interrupts back to the device-level initiators.
> The INTC can support upto 64 input
From: Alexander Duyck
In order to enable a KVM hypervisor to notify the host that a guest has
freed its pages we will need to have a mechanism to update the virtual
memory associated with the guest. In order to expose this functionality I
am adding a new function do_madvise_dontneed that can be
From: Alexander Duyck
Add the host side of the KVM memory hinting support. With this we expose a
feature bit indicating that the host will pass the messages along to the
new madvise function.
This functionality is mutually exclusive with device assignment. If a
device is assigned we will
On Mon, Feb 04, 2019 at 11:55:27AM -0500, Liang, Kan wrote:
> We cannot apply X86_STEPPING_ANY to ignore the stepping. There will be
> problems for 0-8 stepping for KABYLAKE_MOBILE.
So why are we even doing this new "interface"
x86_cpu_has_min_microcode_rev() if even at the conversion stage it
Hello Michael,
Michael S. Tsirkin writes:
> On Tue, Jan 29, 2019 at 03:42:44PM -0200, Thiago Jung Bauermann wrote:
>>
>> Fixing address of powerpc mailing list.
>>
>> Thiago Jung Bauermann writes:
>>
>> > Hello,
>> >
>> > With Christoph's rework of the DMA API that recently landed, the patch
On 2/4/2019 10:42 AM, Marc Gonzalez wrote:
This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490.
Calling ufshcd_set_vccq_rail_unused hangs my system.
It seems vccq is not *not* needed.
Signed-off-by: Marc Gonzalez
---
Reviewed-by: Jeffrey Hugo
drivers/scsi/ufs/ufs.h| 1 -
On 2/4/2019 10:39 AM, Marc Gonzalez wrote:
Use same init sequence as sdm845.
Signed-off-by: Marc Gonzalez
---
Reviewed-by: Jeffrey Hugo
drivers/phy/qualcomm/phy-qcom-qmp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c
On 2/4/2019 10:38 AM, Marc Gonzalez wrote:
Add compatible string for QMP UFS phy on msm8998.
Signed-off-by: Marc Gonzalez
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
On 2/4/2019 10:37 AM, Marc Gonzalez wrote:
The UFS host controller driver needs to set the load on 3 power rails
(l20, l26, s4) but the operation fails silently unless we specify the
regulator-allow-set-load property in the corresponding DT nodes.
Signed-off-by: Marc Gonzalez
---
Hello, Matthew.
On Mon, Feb 04, 2019 at 05:33:00AM -0800, Matthew Wilcox wrote:
> On Mon, Feb 04, 2019 at 11:49:56AM +0100, Uladzislau Rezki wrote:
> > On Fri, Feb 01, 2019 at 01:45:28PM +0100, Michal Hocko wrote:
> > > On Thu 31-01-19 17:24:52, Uladzislau Rezki (Sony) wrote:
> > > > vmap_lazy_nr
On 2/4/2019 10:36 AM, Marc Gonzalez wrote:
Add host controller and PHY DT nodes.
Signed-off-by: Marc Gonzalez
---
vddp-ref-clk-max-microamp = <100>; sounds tiny and fishy.
Jeffrey, Bjorn, can you check?
The PHY driver doesn't seem to try to set any load...
Yes, 0.1mA matches the hardware
* Roger Quadros [190204 15:54]:
> --- a/arch/arm/boot/dts/dra7.dtsi
> +++ b/arch/arm/boot/dts/dra7.dtsi
> @@ -167,6 +167,200 @@
> l4_per3: interconnect@4880 {
> };
>
> + pru_icss1: target-module@4b20 {
I suggest you add these into dra7-pruss.dtsi
Hi Emil,
> Hi,
>
> Den mån 4 feb. 2019 kl 12:18 skrev Shivamurthy Shastri (sshivamurthy)
> :
> >
> > Driver is redesigned using parameter page to support all the Micron
> > SPI NAND flashes.
> >
> > Parameter page of Micron flashes is similar to ONFI parameter table
> > and functionality is
On Mon, Feb 04, 2019 at 11:09:48AM +, Quentin Perret wrote:
> The Energy Model (EM) framework provides an API to let drivers register
> the active power of CPUs. The drivers are expected to provide a callback
> method which estimates the power consumed by a CPU at each available
> performance
Need to retouch your photos? Deep etching or masking for your photos?
We are the studio who can do those service for your photos.
Please send photos to start
Thanks,
Stacy
Aaledn
Bdautzen
Hi Shivamurthy,
On Mon, 4 Feb 2019 11:17:51 +
"Shivamurthy Shastri (sshivamurthy)" wrote:
> Driver is redesigned using parameter page to support all the Micron
> SPI NAND flashes.
Do all Micron SPI NANDs really expose a valid ONFI param page? If
that's not the case, then relying on ONFi
On 02/02/2019 01:17, Matthias Kaehlcke wrote:
> Hi Pi-Hsun,
>
> a few comments inline.
>
> It's the first time I dabble into remoteproc, I don't claim to have a
> complete understanding of the driver at this point ;-)
>
> On Thu, Jan 31, 2019 at 05:31:27PM +0800, Pi-Hsun Shih wrote:
>> From:
* Roger Quadros [190204 15:54]:
> +static int sysc_enable_pruss(struct sysc *sysc)
> +{
> + int i;
> + u32 reg;
> + bool ready;
> +
> + /* configure for Smart Idle & Smart Standby */
> + reg = sysc_read(sysc, sysc->offsets[SYSC_SYSCONFIG]);
> + reg &=
On 31/01/2019 10:31, Pi-Hsun Shih wrote:
> From: Erin Lo
[...]
> +struct platform_device *scp_get_plat_device(struct platform_device *pdev)
> +{
> + struct device *dev = >dev;
> + struct device_node *scp_node;
> + struct platform_device *scp_pdev;
> +
> + scp_node =
Hi Randy,
On Mon, Feb 4, 2019 at 6:57 PM Randy Dunlap wrote:
> On 2/4/19 9:46 AM, Randy Dunlap wrote:
> > On 2/4/19 5:42 AM, Geert Uytterhoeven wrote:
> >> Below is the list of build error/warning regressions/improvements in
> >> v5.0-rc5[1] compared to v4.20[2].
> >>
> >> Summarized:
> >> -
Hi Jonas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on block/for-next]
[also build test WARNING on v5.0-rc4 next-20190204]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
On 2/4/19 9:46 AM, Randy Dunlap wrote:
> On 2/4/19 5:42 AM, Geert Uytterhoeven wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v5.0-rc5[1] compared to v4.20[2].
>>
>> Summarized:
>> - build errors: +2/-4
>> - build warnings: +113/-14843
>>
>> JFYI, when
On Mon, Feb 04, 2019 at 05:14:19PM +, Christopher Lameter wrote:
> Frankly I still think this does not solve anything.
>
> Concurrent write access from two sources to a single page is simply wrong.
> You cannot make this right by allowing long term RDMA pins in a filesystem
> and thus the
On Fri, 1 Feb 2019, Fenghua Yu wrote:
> On some platforms, a feature (e.g. #AC for split lock) may not be
> enumerated by CPUID or non architectural way in IA32_CORE_CAPABILITY.
> To enable the feature on the platforms, a new kernel option setcpuid
> is added.
>
> The feature is defined in
On 02/01, Dmitry Vyukov wrote:
> Hello,
>
> The following program leads to an unkillable process that eats CPU in
> an infinite loop in BPF_PROG_TEST_RUN syscall. But kernel does not
> self-detect cpu/rcu/task stalls either. The program contains max
> number of repetitions, but as far as I see
On 2/4/19 5:42 AM, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.0-rc5[1] compared to v4.20[2].
>
> Summarized:
> - build errors: +2/-4
> - build warnings: +113/-14843
>
> JFYI, when comparing v5.0-rc5[1] to v5.0-rc4[3], the summaries
This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490.
Calling ufshcd_set_vccq_rail_unused hangs my system.
It seems vccq is not *not* needed.
Signed-off-by: Marc Gonzalez
---
drivers/scsi/ufs/ufs.h| 1 -
drivers/scsi/ufs/ufshcd.c | 59 +++
2
Use same init sequence as sdm845.
Signed-off-by: Marc Gonzalez
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c
b/drivers/phy/qualcomm/phy-qcom-qmp.c
index b4006818e1b6..39b9c31b67d0 100644
---
Add compatible string for QMP UFS phy on msm8998.
Signed-off-by: Marc Gonzalez
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
The UFS host controller driver needs to set the load on 3 power rails
(l20, l26, s4) but the operation fails silently unless we specify the
regulator-allow-set-load property in the corresponding DT nodes.
Signed-off-by: Marc Gonzalez
---
arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 3 +++
1 file
Hi Sakari,
[snip]
> > > > > fail_stop_pipeline:
> > > > > @@ -543,6 +546,8 @@ static void ipu3_vb2_stop_streaming(struct
> > > > vb2_queue *vq)
> > > > > dev_err(>pci_dev->dev,
> > > > > "failed to stop subdev streaming\n");
> > > > >
> > > > > +
Add host controller and PHY DT nodes.
Signed-off-by: Marc Gonzalez
---
vddp-ref-clk-max-microamp = <100>; sounds tiny and fishy.
Jeffrey, Bjorn, can you check?
The PHY driver doesn't seem to try to set any load...
---
arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 19 +++
Hello,
This series is now good enough for the limelight, IMO.
Difference between, v2 and v3:
- Add qcom,msm8998-qmp-ufs-phy compat string and match it in the PHY driver
- Drop vdd-hba-fixed-regulator
- Write the reg addresses with full 32-bit width
- Set regulator-allow-set-load only on the 3
When efi=noruntime or efi=oldmap is used, EFI services won't be available
in the second kernel, therefore the second kernel will not be able to get
the ACPI RSDP address from firmware by calling EFI services so it won't
boot. Previously we are expecting the user to set the acpi_rsdp=
on kernel
On Mon, 4 Feb 2019, Dmitry Vyukov wrote:
> On Mon, Feb 4, 2019 at 10:27 AM Thomas Gleixner wrote:
> >
> > On Fri, 1 Feb 2019, Dmitry Vyukov wrote:
> >
> > > On Fri, Feb 1, 2019 at 5:48 PM Dmitry Vyukov wrote:
> > > >
> > > > Hello,
> > > >
> > > > The following program creates an unkillable
On Tue, Jan 29, 2019 at 06:05:47PM +, Mark Brown wrote:
> On Tue, Jan 29, 2019 at 09:54:38AM +, Charles Keepax wrote:
>
> > Hmm... I think this might need a little more investigation, it
> > does indeed fail at present (amazing that it works upto exactly 1.2V
> > which is common the
On Fri, 1 Feb 2019, Rajneesh Bhardwaj wrote:
> Add CPUID of Icelake (ICL) mobile processors to Intel family list. The
> Information related to ICL CPUID is referenced from below Coreboot
> project link.
>
>
On 01/02/2019 08:38, michael@mediatek.com wrote:
> From: Michael Kao
>
> Add calibration item in thermal_data to support
> the project with different calibration coefficient.
>
> Signed-off-by: Michael Kao
> ---
> drivers/thermal/mtk_thermal.c | 19 ++-
> 1 file
On Mon, Feb 04, 2019 at 08:36:43PM +0530, Balakrishna Godavarthi wrote:
> During hci down we observed IBS sleep commands are queued in the Tx
> buffer and hci_uart_write_work is sending data to the chip which is
> not required as the chip is powered off. This patch will disable IBS
> and flush the
From: Moritz Fischer
Update device-tree binding with fixed-link support.
With fixed-link support the formerly required property 'phy-handle'
is now optional if 'fixed-link' child is present.
Signed-off-by: Moritz Fischer
---
.../devicetree/bindings/net/nixge.txt | 33
From: Moritz Fischer
This series adds fixed-link support to nixge.
The first patch corrects the binding to correctly reflect
hardware that does not come with MDIO cores instantiated.
The second patch adds fixed link support to the driver.
The third patch updates the binding document with the
From: Moritz Fischer
Make MDIO child optional and only instantiate the
MDIO bus if the child is actually present.
There are currently no (in-tree) users of this
binding; all (out-of-tree) users use overlays that
get shipped together with the FPGA images that contain
the IP.
This will
From: Moritz Fischer
Add support for fixed-link configurations to nixge driver.
Signed-off-by: Moritz Fischer
---
drivers/net/ethernet/ni/nixge.c | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git a/drivers/net/ethernet/ni/nixge.c
On Sat, 2 Feb 2019, Alan Mackenzie wrote:
> Hello, Thomas.
>
> Thanks for such a rapid reply!
>
> On Fri, Feb 01, 2019 at 23:04:48 +0100, Thomas Gleixner wrote:
> > Hello Alan,
>
> > On Fri, 1 Feb 2019, Alan Mackenzie wrote:
> > > 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94
> > > posix-timers: Fix
On 01/02/2019 08:38, michael@mediatek.com wrote:
> From: Michael Kao
>
> The index of msr and adcpnp should match the sensor
> which belongs to the selected bank in the for loop.
>
If I get that right, this fixes
b7cf0053738c ("thermal: Add Mediatek thermal driver for mt2701.")
So
On Sun, Feb 03, 2019 at 01:46:50AM +0800, Kai Heng Feng wrote:
> > On Jan 28, 2019, at 3:51 PM, Kai Heng Feng
> > wrote:
>
> >> If I understand correctly, the bugzilla lspci
> >> (https://bugzilla.kernel.org/attachment.cgi?id=280691) was collected
> >> at point 8, and it shows PME_Status=1 when
From: Bartosz Golaszewski
The timer interrupts specified in commit 3652e2741f42 ("ARM: dts:
da850: Add clocks") are wrong but since the current timer code
hard-codes them, the bug was never spotted.
This patch must go into stable since, once we introduce a proper
clocksource driver, devices
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da850.c | 56 ++-
1 file changed, 22 insertions(+), 34 deletions(-)
diff --git
From: Bartosz Golaszewski
Currently the timer code checks if the clock pointer passed to it is
good (!IS_ERR(clk)). The new clocksource driver expects the clock to
be functional and doesn't perform any checks so emit a warning if
clk_get() fails. Apply this to all davinci platforms.
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm644x.c | 36 ++
1 file changed, 23 insertions(+), 13 deletions(-)
diff --git
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm355.c | 36 ++-
1 file changed, 23 insertions(+), 13 deletions(-)
diff --git
From: Bartosz Golaszewski
Currently the clocksource and clockevent support for davinci platforms
lives in mach-davinci. It hard-codes many things, used global variables,
implements functionalities unused by any platform and has code fragments
scattered across many (often unrelated) files.
From: Bartosz Golaszewski
Boards from the dm* family rely on register offset definitions from
arch/arm/mach-davinci/include/mach/time.h. We'll be removing this file
soon, so move the required defines to davinci.h where the rest of such
constants live.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da830.c | 49 ---
1 file changed, 22 insertions(+), 27 deletions(-)
diff --git
From: Bartosz Golaszewski
We now have a proper clocksource driver for davinci. Switch the platform
to using it.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm646x.c | 36 ++
1 file changed, 23 insertions(+), 13 deletions(-)
diff --git
401 - 500 of 1302 matches
Mail list logo
