> From: Lorenzo Pieralisi
> Sent: Wednesday, March 14, 2018 04:50
> On Tue, Mar 13, 2018 at 06:23:39PM +, Dexuan Cui wrote:
>
> [...]
>
> > Hi Lorenzo, Bjorn, and all,
> > Do you need more ACKs? Currently Michael and Haiyang reviewed and ack'd
> > the patchset.
> >
> > Should I send a v4 tha
From: Madalin Bucur
Date: Wed, 14 Mar 2018 08:37:27 -0500
> This patch set is addressing several issues in the DPAA Ethernet
> driver suite:
>
> - module unload crash caused by wrong reference to device being left
>in the cleanup code after the DSA related changes
> - scheduling wile atomi
Sorry
I just noticed that the commit header is corrupted
I will resend this patch
Patrice
On 03/14/2018 03:52 PM, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> As serial interface is already specified into stdout-path property,
> "console=ttyASN,115200" from bootargs can be remove
Hi Ulf,
On Wed, Mar 14, 2018 at 05:58:10PM +0100, Ulf Hansson wrote:
> For ARM, the PSCI firmware interface may be managing the power to the CPUs.
> Depending on the SoC, CPUs may also be arranged in hierarchical manner, which
> could add another level of complexity from a CPU idle management poin
On Wed, Mar 14, 2018 at 05:58:16PM +0100, Ulf Hansson wrote:
> @@ -132,6 +133,15 @@ static inline ktime_t tick_nohz_get_sleep_length(void)
> {
> return NSEC_PER_SEC / HZ;
> }
> +
> +static inline ktime_t tick_nohz_get_next_wakeup(int cpu)
> +{
> + ktime_t len = NSEC_PER_SEC/HZ;
> +
> +
Radim Krčmář writes:
> 2018-03-12 15:19+0100, Vitaly Kuznetsov:
>>
>> That said I'd like to defer the question to KVM maintainers: Paolo,
>> Radim, what would you like me to do? Use STATIC_JUMP_IF_TRUE/FALSE as
>> they are, try to make them work for !HAVE_JUMP_LABEL and use them or
>> maybe we c
Hi Zong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc5 next-20180314]
[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-ci/linux
On Wed, Mar 14, 2018 at 04:49:39PM +0100, Frederic Weisbecker wrote:
> On Mon, Mar 12, 2018 at 10:47:41AM +0100, Rafael J. Wysocki wrote:
> > @@ -136,6 +138,13 @@ static inline u64 get_cpu_idle_time_us(i
> > static inline u64 get_cpu_iowait_time_us(int cpu, u64 *unused) { return
> > -1; }
> > #
Hi Peter,
On 03/14/2018 09:51 AM, Peter Seiderer wrote:
Enables gstreamer v4l2src lost frame detection, e.g:
0:00:08.685185668 348 0x54f520 WARN v4l2src
gstv4l2src.c:970:gst_v4l2src_create: lost frames detected: count =
141 - ts: 0:00:08.330177332
Signed-off-by: Peter Seiderer
---
Ch
From: Jason Wang
Date: Wed, 14 Mar 2018 11:23:40 +0800
> Now we have ndo_xdp_xmit, switch to use it instead of the slow generic
> XDP TX routine. XDP_TX on TAP gets ~20% improvements from ~1.5Mpps to
> ~1.8Mpps on 2.60GHz Core(TM) i7-5600U.
>
> Signed-off-by: Jason Wang
Applied, thanks Jason.
Thomas Gleixner writes:
> On Mon, 12 Mar 2018, Vitaly Kuznetsov wrote:
>> Thomas Gleixner writes:
>> > On Fri, 9 Mar 2018, Vitaly Kuznetsov wrote:
>> >> Static key is being used to avoid performance penalty for non-Hyper-V
>> >> deployments. Tests show we add around 3 (three) CPU cycles on each
On Wed, Mar 14, 2018 at 9:36 AM, Jonathan Toppins wrote:
> The problem was introduced in commit
> 506b0a395f26 ("[netdrv] tg3: APE heartbeat changes"). The bug occurs
> because tp->lock spinlock is held which is obtained in tg3_start
> by way of tg3_full_lock(), line 11571. The documentation for u
From: Patrice Chotard
As serial interface is already specified into stdout-path property,
"console=ttyASN,115200" from bootargs can be removed.
Signed-off-by: Patrice Chotard
---
arch/arm/boot/dts/stih407-b2120.dts | 2 +-
arch/arm/boot/dts/stih410-b2120.dts | 2 +-
arch/arm/boot/dts/stih410-b
On Tue, Mar 13, 2018 at 8:34 PM, Darren Hart wrote:
>
> At RC5, we're certainly further into the RC cycle than I want to see
> these changes. So if you just want to call it now, I understand and I'll
> send you the revert pull request. If you can give me another day, I
> think we may finally have
On Wed, Mar 14, 2018 at 12:28 PM, Dou Liyang wrote:
> +static void __init acpi_update_possible_map(void)
> +{
> + unsigned int cpu, nr = 0;
> +
> + if (nr_cpu_ids <= nr_unique_ids)
> + return;
> +
> + for_each_possible_cpu(cpu) {
> + if (nr >= nr_uni
On Wed, 2018-03-14 at 13:08 -0400, Mimi Zohar wrote:
> On Wed, 2018-03-14 at 07:41 -0700, James Bottomley wrote:
[...]
> > What about a compromise: we
> > already get the boot loader to do measurements and PCR extensions
> > using the BIOS TPM driver, there's no reason why we can't do the
> > same
On Wed, Mar 14, 2018 at 05:58:25PM +0100, Ulf Hansson wrote:
> Instead of having each psci init function taking care of the of_node_put(),
> let's deal with that from psci_dt_init(), as this enables a bit simpler
> error path for each psci init function.
>
> Cc: Lina Iyer
> Co-developed-by: Lina
This will allow usage of vsock from 32-bit binaries on a 64-bit
kernel.
Signed-off-by: Sonny Rao
---
drivers/vhost/vsock.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c
index 0d14e2ff19f16..d0e65e92110e5 100644
--- a/drivers/vhost/vsock.c
+++ b
On Thu, 15 Mar 2018, Masahiro Yamada wrote:
> From the comment, I expect this code creates autoksyms.h in case it
> is missing, but it actually touches it when it does exists.
Oops, indeed.
> Signed-off-by: Masahiro Yamada
> ---
>
> I do not know when this code is useful...
>
> If autoksyms.h
On 03/14/2018 01:22 PM, Michael Chan wrote:
> On Wed, Mar 14, 2018 at 9:36 AM, Jonathan Toppins wrote:
>> The problem was introduced in commit
>> 506b0a395f26 ("[netdrv] tg3: APE heartbeat changes"). The bug occurs
>> because tp->lock spinlock is held which is obtained in tg3_start
>> by way of tg
On Wed, 14 Mar 2018 10:07:35 PDT (-0700), t...@linutronix.de wrote:
On Wed, 7 Mar 2018, Palmer Dabbelt wrote:
This converts the ARM port to use the recently added
GENERIC_IRQ_MULTI_HANDLER, which is essentially just a copy of ARM's
existhing MULTI_IRQ_HANDLER. The only changes are:
* handle_a
On Tue, Mar 13, 2018 at 07:24:20PM -0400, Lyude Paul wrote:
> On Mon, 2018-03-12 at 23:01 +0200, Ville Syrjälä wrote:
> > On Fri, Mar 09, 2018 at 04:32:27PM -0500, Lyude Paul wrote:
> > > While having the modeset_retry_work in intel_connector makes sense with
> > > SST, this paradigm doesn't make a
On Wed, 14 Mar 2018 10:11:49 PDT (-0700), s...@shealevy.com wrote:
Palmer Dabbelt writes:
On Wed, 14 Mar 2018 05:07:09 PDT (-0700), s...@shealevy.com wrote:
Palmer Dabbelt writes:
On Tue, 13 Mar 2018 14:30:53 PDT (-0700), s...@shealevy.com wrote:
Hi Palmer,
Palmer Dabbelt writes:
On T
On Wed, Mar 14, 2018 at 05:58:28PM +0100, Ulf Hansson wrote:
> Following changes needs to be able to call psci_get|set_domain_state() and
> psci_dt_parse_state_node(), but from a separate file. Let's make that
> possible by sharing them via a new internal PSCI header file.
>
> Cc: Lina Iyer
> Sig
On Wed, Mar 14, 2018 at 7:12 PM, Aaron Durbin wrote:
> On Wed, Mar 14, 2018 at 10:38 AM, Andy Shevchenko
> wrote:
>> On Wed, Mar 14, 2018 at 6:29 PM, Daniel Kurtz wrote:
>>> On Wed, Mar 14, 2018 at 4:54 AM Ricardo Ribalda Delgado <
>>> ricardo.riba...@gmail.com> wrote:
On Wed, Mar 14, 2018
> Displaying these different types for s390 is important from my point of
> view. Of course, I could create a mapping of TX_NC_TABORT/TX_NC_TEND
> to tx-commit/tx-abort. The remaining events would still appear to be specific
> to the cpum_cf.
If you want more generic metrics you can just use the
From: Colin Ian King
Currently when cnt is 100 an array bounds overflow occurs on the assignment
of fd[cnt]. Fix this by performing the bounds check on cnt before writing
to fd.
Detected by cppcheck:
tools/perf/tests/bp_account.c:115: (warning) Either the condition
'cnt==100' is redundant or the
On Wed, Mar 14, 2018 at 06:11:22PM +0200, Igor Stoppa wrote:
> On 14/03/18 15:04, Matthew Wilcox wrote:
> > but the principle it uses
> > seems like a better match to me than the rather complex genalloc.
>
> It uses meta data in a different way than genalloc.
> There is probably a tipping point wh
Hi Zong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc5 next-20180314]
[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-ci/linux
On 14 March 2018 at 16:41, Ard Biesheuvel wrote:
> On 14 March 2018 at 15:54, Ard Biesheuvel wrote:
>> On 14 March 2018 at 14:54, Michal Hocko wrote:
>>> On Wed 14-03-18 14:35:12, Ard Biesheuvel wrote:
On 14 March 2018 at 14:13, Michal Hocko wrote:
> Does http://lkml.kernel.org/r/2018
On Wed, Mar 14, 2018 at 05:58:30PM +0100, Ulf Hansson wrote:
> In case the hierarchical layout is used in DT, we want to initialize the
> corresponding PM domain topology for the CPUs, by using the generic PM
> domain (aka genpd) infrastructure.
>
> At first glance, it may seem feasible to hook in
On Wed, Mar 14, 2018 at 05:58:33PM +0100, Ulf Hansson wrote:
> Some new files have been for the PSCI firmware driver, let's make the
> expression more generic to cover them all.
>
> Signed-off-by: Ulf Hansson
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -
+struct pmalloc_data {
+ struct gen_pool *pool; /* Link back to the associated pool. */
+ bool protected; /* Status of the pool: RO or RW. */
+ struct kobj_attribute attr_protected; /* Sysfs attribute. */
+ struct kobj_attribute attr_avail; /* Sysfs attribute. *
On Wed, Mar 14, 2018 at 6:34 PM, Desnes A. Nunes do Rosario
wrote:
> Add PCI_DEV_FLAGS_QUIET_PCI_REALIGN to pci_dev_flags and use it to
> silent PCI realignment messages if the flag is turned on by a driver.
It doesn't explain "Why?"
Why the driver needs that?
Another approach is to increase lev
On Sat, Mar 10, 2018 at 12:33:35AM +, Prakhya, Sai Praneeth wrote:
> Although the discussions were off my understanding, the present issue
> I see is, (and also the motivation for me to do the patch is) when a
> thread tries to execute any efi_runtime_service() we switch to efi_pgd
> (which doe
Hi Palmer,
On Wed, Mar 14, 2018 at 09:41:43AM -0700, Palmer Dabbelt wrote:
> The device tree code looks for CONFIG_CMDLINE_FORCE, but we were using
> CONFIG_CMDLINE_OVERRIDE. It looks like this was just a hold over from
> before our device tree conversion -- in fact, we'd already removed the
> su
On 14/03/18 17:11, Thomas Gleixner wrote:
> On Wed, 14 Mar 2018, Mark Rutland wrote:
>> On Tue, Mar 13, 2018 at 06:35:07PM +, Marc Zyngier wrote:
>>> On 13/03/18 17:51, Mark Rutland wrote:
On Tue, Mar 13, 2018 at 05:21:00PM +, Marc Zyngier wrote:
> As kexec and kdump are getting us
On Wed, Mar 14, 2018 at 03:37:37PM +0100, Arnd Bergmann wrote:
> Hardwall is a tile specific feature, and with the removal of the
> tile architecture, this has become dead code, so let's remove it.
>
> Signed-off-by: Arnd Bergmann
ACK
Although it should go via tile tree for "atomicity".
Hi Tejun,
Thanks, I see I missed the RCU part.
I'll try the force atomic thing.
Though so far I haven't been able to reproduce it yet.
Thanks,
David
2018-03-14 8:43 GMT-07:00 Tejun Heo :
> Hello, David.
>
> On Tue, Mar 13, 2018 at 03:50:47PM -0700, David Chen wrote:
>>
>> CPU A
On Wed, Mar 14, 2018 at 7:41 PM, Andy Shevchenko
wrote:
> I would rather name it _NO_PCI_REALIGN_MSG
I meant _NO_REALIGN_MSG of course (PCI is already at the beginning).
--
With Best Regards,
Andy Shevchenko
John Garry [john.ga...@huawei.com] wrote:
> In the recently introduced support for vendor subdirectory,
> the checking for directory entries under xfs (or any other fs
> which does not support dirent.d_type) is missing the check
> for links for current and parent directory. This can result
> in a b
On 3/13/18 3:00 PM, Matthew Wilcox wrote:
On Tue, Mar 13, 2018 at 11:45:50PM +0200, Igor Stoppa wrote:
When a page is used for virtual memory, it is often necessary to obtain
a handler to the corresponding vm_struct, which refers to the virtually
continuous area generated when invoking vmalloc
From: Michael Chan
Date: Wed, 14 Mar 2018 10:22:51 -0700
> On Wed, Mar 14, 2018 at 9:36 AM, Jonathan Toppins wrote:
>> The problem was introduced in commit
>> 506b0a395f26 ("[netdrv] tg3: APE heartbeat changes"). The bug occurs
>> because tp->lock spinlock is held which is obtained in tg3_start
On Sat, Mar 10, 2018 at 09:16:36AM -0800, Kees Cook wrote:
> On Sat, Mar 10, 2018 at 6:14 AM, Luis R. Rodriguez wrote:
> > Greg,
> >
> > Here's a respin of what I have queued up for v4.17 for the firmware API. It
> > combines the cleanup I've been working on and the addition of the new API
> > ca
On Wed, Mar 14, 2018 at 04:45:20PM +0100, Andrey Konovalov wrote:
> On Fri, Mar 9, 2018 at 6:42 PM, Evgenii Stepanov wrote:
> > On Fri, Mar 9, 2018 at 9:31 AM, Andrey Konovalov
> > wrote:
> >> On Fri, Mar 9, 2018 at 4:53 PM, Catalin Marinas
> >> wrote:
> >>> I'm not yet convinced these functio
On 13/03/18 08:55, Vivek Gautam wrote:
From: Sricharan R
The smmu device probe/remove and add/remove master device callbacks
gets called when the smmu is not linked to its master, that is without
the context of the master device. So calling runtime apis in those places
separately.
Signed-off-b
Hi Colin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.16-rc4]
[cannot apply to next-20180314]
[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-ci/linux/commits/Colin-King/ASoC
On Wed, Mar 14, 2018 at 06:31:38PM +0200, Andy Shevchenko wrote:
> On Tue, Mar 13, 2018 at 11:45 PM, Bjorn Helgaas wrote:
> > From: Bjorn Helgaas
>
> Agree with Christoph's comment.
>
> > If a device already has MSI or MSI-X enabled, there's no need to set up its
> > legacy INTx interrupt.
>
>
On 13/03/18 08:55, Vivek Gautam wrote:
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which gets
called once when the master is added to the smm
On 03/14/2018 10:14 AM, Ram Pai wrote:
> I look at key-0 as 'the key'. It has special status.
> (a) It always exist.
Do you mean "is always allocated"?
> (b) it cannot be freed.
This is the one I'm questioning.
> (c) it is assigned by default.
I agree on this totally. :)
> (d) its permission
Hi all,
this series switches the x86 code the the dma-direct implementation
for direct (non-iommu) dma and the generic swiotlb ops. This includes
getting rid of the special ops for the AMD memory encryption case and
the STA2x11 SOC. The generic implementations are based on the x86
code, so they
On Thu, 15 Mar 2018, Masahiro Yamada wrote:
> Commit d3fc425e819b ("kbuild: make sure autoksyms.h exists early")
> moved the code that touches autoksyms.h to scripts/kconfig/Makefile
> with obscure reason.
>
> From Nicolas' comment [1], he did not seem to be sure about the root
> cause.
>
> I gu
There were only a few Pentium Pro multiprocessors systems where this
errata applied. They are more than 20 years old now, and we've slowly
dropped places where put the workarounds in and discouraged anyone
from enabling the workaround.
Get rid of it for good.
Signed-off-by: Christoph Hellwig
Rev
Hi all,
this series switches the x86 code the the dma-direct implementation
for direct (non-iommu) dma and the generic swiotlb ops. This includes
getting rid of the special ops for the AMD memory encryption case and
the STA2x11 SOC. The generic implementations are based on the x86
code, so they
Signed-off-by: Christoph Hellwig
---
include/linux/set_memory.h | 12
1 file changed, 12 insertions(+)
diff --git a/include/linux/set_memory.h b/include/linux/set_memory.h
index e5140648f638..da5178216da5 100644
--- a/include/linux/set_memory.h
+++ b/include/linux/set_memory.h
@@ -1
All dma_ops implementations used on x86 now take care of setting their own
required GFP_ masks for the allocation. And given that the common code
now clears harmful flags itself that means we can stop the flags in all
the iommu implementations as well.
Signed-off-by: Christoph Hellwig
---
arch/
We want to phase out looking at the magic GFP_DMA flag in the dma mapping
routines, so switch the gart driver to use the coherent_dma_mask instead,
which is used to select the GFP_DMA flag in the caller.
Signed-off-by: Christoph Hellwig
---
arch/x86/kernel/amd_gart_64.c | 2 +-
1 file changed, 1
Now that set_memory_decrypted is always available we can just call it
directly.
Signed-off-by: Christoph Hellwig
---
arch/x86/include/asm/mem_encrypt.h | 2 --
arch/x86/mm/mem_encrypt.c | 9 -
lib/swiotlb.c | 12 ++--
3 files changed, 6 insertions(
Unused now that everyone uses swiotlb_{alloc,free}.
Signed-off-by: Christoph Hellwig
---
include/linux/swiotlb.h | 8
lib/swiotlb.c | 38 --
2 files changed, 46 deletions(-)
diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h
in
Give the basic phys_to_dma and dma_to_phys helpers a __-prefix and add
the memory encryption mask to the non-prefixed versions. Use the
__-prefixed versions directly instead of clearing the mask again in
various places.
Signed-off-by: Christoph Hellwig
---
arch/arm/include/asm/dma-direct.h
With that in place the generic dma-direct routines can be used to
allocate non-encrypted bounce buffers, and the x86 SEV case can use
the generic swiotlb ops including nice features such as using CMA
allocations.
Note that I'm not too happy about using sev_active() in dma-direct, but
I couldn't co
On Wed, Mar 14, 2018 at 09:58:19AM -0700, Vineet Gupta wrote:
> Well it is broken wrt the semantics the syscall is supposed to provide.
> Preemption disabling is what prevents a concurrent thread from coming in and
> modifying the same location (Imagine a variable which is being cmpxchg
> concurre
Use the dma_direct_* helpers and cleanup the code flow.
Signed-off-by: Christoph Hellwig
---
drivers/iommu/Kconfig | 1 +
drivers/iommu/intel-iommu.c | 62 -
2 files changed, 17 insertions(+), 46 deletions(-)
diff --git a/drivers/iommu/Kconfig
The generic swiotlb dma ops were based on the x86 ones and provide
equivalent functionality, so use them.
Also fix the sta2x11 case. For that SOC the dma map ops need an
additional physical to dma address translations. For swiotlb buffers
that is done throught the phys_to_dma helper, but the sta
This gains support for CMA allocations for the force_iommu case, and
cleans up the code a bit.
Signed-off-by: Christoph Hellwig
---
arch/x86/kernel/amd_gart_64.c | 36 ++--
1 file changed, 14 insertions(+), 22 deletions(-)
diff --git a/arch/x86/kernel/amd_gart_64
This cleans up the code a lot by removing duplicate logic.
Signed-off-by: Christoph Hellwig
---
drivers/iommu/Kconfig | 1 +
drivers/iommu/amd_iommu.c | 68 +++
2 files changed, 22 insertions(+), 47 deletions(-)
diff --git a/drivers/iommu/Kconfig
The generic dma-direct implementation is now functionally equivalent to
the x86 nommu dma_map implementation, so switch over to using it.
Note that the various iommu drivers are switched from x86_dma_supported
to dma_direct_supported to provide identical functionality, although the
checks looks fa
These days all devices (including the ISA fallback device) have a coherent
DMA mask set, so remove the workaround.
Signed-off-by: Christoph Hellwig
Reviewed-by: Konrad Rzeszutek Wilk
---
arch/x86/include/asm/dma-mapping.h | 18 ++
arch/x86/kernel/pci-dma.c | 10
On Wed, Mar 14, 2018 at 05:44:03PM +, Luis R. Rodriguez wrote:
> On Sat, Mar 10, 2018 at 09:16:36AM -0800, Kees Cook wrote:
> > On Sat, Mar 10, 2018 at 6:14 AM, Luis R. Rodriguez
> > wrote:
> > > Greg,
> > >
> > > Here's a respin of what I have queued up for v4.17 for the firmware API.
> > >
On Tue, Mar 13, 2018 at 10:06:34PM +0100, Maciej S. Szmigiero wrote:
> The maximum possible value returned by install_equiv_cpu_table() is
> UINT_MAX + CONTAINER_HDR_SZ (on a 64-bit kernel).
> This is more than (signed) int type currently returned by this function can
> hold so this function will n
On Tue, Mar 13, 2018 at 10:06:48PM +0100, Maciej S. Szmigiero wrote:
> +/* Maximum of all the above families */
> +#define PATCH_MAX_SIZE SIMPLE_MAX3(F1XH_MPB_MAX_SIZE, F14H_MPB_MAX_SIZE, \
Nope, it should be
#define PATCH_MAX_SIZE (max_t(unsigned int, FXXH...
--
Regards/Gruss,
Boris.
Good
On Tue, Mar 13, 2018 at 08:44:49AM -0500, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wvla, remove VLA and replace it
> with a fixed-length array instead.
>
> Fixed as part of the directive to remove all VLAs from
> the kernel: https://lkml.org/lkml/2018/3/7/621
>
> Reviewed-by: Maur
On Wed, Mar 14, 2018 at 9:16 AM, Benjamin Tissoires
wrote:
>
> Hi Nicolas,
>
> On Wed, Mar 14, 2018 at 6:22 AM, Nicolas Boichat
> wrote:
> > From: Wei-Ning Huang
> >
> > Add Google hammer HID driver. This driver allow us to control hammer
> > keyboard backlight and support future features.
> >
Whenever PCI bus is added, HyperV guarantees the BUS id is unique. Even with
that when a first device is added to the bus, it overrides bus domain ID with
the device serial number. Sometime this can result in BUS ID not being unique.
In this case, when PCI_BUS and a device added to the bus, even be
On Wed, Mar 14, 2018 at 01:34:54PM -0300, Desnes A. Nunes do Rosario wrote:
> Add PCI_DEV_FLAGS_QUIET_PCI_REALIGN to pci_dev_flags and use it to
> silent PCI realignment messages if the flag is turned on by a driver.
>
> Signed-off-by: Desnes A. Nunes do Rosario
> ---
> drivers/pci/pci.c |
Whenever PCI bus is added, HyperV guarantees the BUS id is unique. Even with
that when a first device is added to the bus, it overrides bus domain ID
with
the device serial number. Sometime this can result in BUS ID not being
unique.
In this case, when PCI_BUS and a device added t
On Wed, Jan 24, 2018 at 07:41:15PM -0600, Samuel Holland wrote:
> On many systems, coreboot[1] firmware can initialize graphics hardware
> and set up a high-resolution linear framebuffer. It exports information
> about this framebuffer, along with various other information, in a table
> discoverabl
Hi Colin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.16-rc4]
[cannot apply to next-20180314]
[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-ci/linux/commits/Colin-King/ASoC
Hello Andy,
On 03/14/2018 02:41 PM, Andy Shevchenko wrote:
On Wed, Mar 14, 2018 at 6:34 PM, Desnes A. Nunes do Rosario
wrote:
Add PCI_DEV_FLAGS_QUIET_PCI_REALIGN to pci_dev_flags and use it to
silent PCI realignment messages if the flag is turned on by a driver.
It doesn't explain "Why?"
Why
This patchset reworks the I2C/SPI code from meter module. The set of
patches try to reduce the code duplication and make the communication
reliable. The current version of the module had many code duplications,
which make the code more error-prone and hard to read. Jonh Syne
identified some wrong e
Hi Sergei,
thanks for review
On Wed, Mar 14, 2018 at 08:09:52PM +0300, Sergei Shtylyov wrote:
> On 03/13/2018 05:30 PM, Jacopo Mondi wrote:
>
> > Add DRM bridge driver for Thine THC63LVD1024 LVDS to digital parallel
> > output decoder.
> >
> > Signed-off-by: Jacopo Mondi
> [...]
> > diff --git
The write operation using I2C has many code duplications and four
different interfaces per data size. This patch introduces a single
function that centralizes the main tasks.
The central function inserted by this patch can easily replace all the
four functions related to the data size. However, th
The write operation using SPI has a many code duplications (similar to
I2C) and four different interfaces per data size. This patch introduces
a single function that centralizes the main task related to SPI.
Signed-off-by: Rodrigo Siqueira
---
drivers/staging/iio/meter/ade7854-spi.c | 100 ++
This patch removes code duplications related to the write_reg_*
functions and centralizes them in a single function. Also, it eliminates
the legacy functions and replaces them by a unique signature that is
used by SPI and I2C.
Signed-off-by: Rodrigo Siqueira
---
drivers/staging/iio/meter/ade7854
The read operation for the I2C function has many duplications that can
be generalized into a single function. This patch reworks the read
operation for I2C to centralizes all similar code in a single function.
Part of the rework includes a proper error handling and a fix on the
i2c_master_recv for
On architectures with CONFIG_HAVE_ARCH_HUGE_VMAP set, ioremap()
may create pud/pmd mappings. Kernel panic was observed on arm64
systems with Cortex-A75 in the following steps as described by
Hanjun Guo. [1]
1. ioremap a 4K size, valid page table will build,
2. iounmap it, pte0 will set to 0;
3
On architectures with CONFIG_HAVE_ARCH_HUGE_VMAP set, ioremap()
may create pud/pmd mappings. Kernel panic was observed on arm64
systems with Cortex-A75 in the following steps as described by
Hanjun Guo.
1. ioremap a 4K size, valid page table will build,
2. iounmap it, pte0 will set to 0;
3. io
The original code had a read function per data size; after updates, all
read functions tasks were centralized in a single function, but the old
signature was kept to maintain the module working without problems. This
patch removes a set of duplications associated with read_reg_*, and
update the are
Implement pud_free_pmd_page() and pmd_free_pte_page() on x86, which
clear a given pud/pmd entry and free up lower level page table(s).
Address range associated with the pud/pmd entry must have been purged
by INVLPG.
fixes: e61ce6ade404e ("mm: change ioremap to set up huge I/O mappings")
Signed-off
Hi Shameer,
On 05/03/18 11:44, Shameerali Kolothum Thodi wrote:
Hi Robin,
-Original Message-
From: Robin Murphy [mailto:robin.mur...@arm.com]
Sent: Friday, March 02, 2018 5:17 PM
To: Alex Williamson ; Shameerali Kolothum
Thodi
Cc: Auger Eric ; pmo...@linux.vnet.ibm.com;
k...@vger.kern
There is some improper error handling for IRQ and device register. This
patch adds a proper verification. The IRQ correction was extracted from
John Syne patches.
Signed-off-by: Rodrigo Siqueira
Signed-off-by: John Syne
---
drivers/staging/iio/meter/ade7854.c | 4 ++--
1 file changed, 2 insert
Rework read SPI function to reduce the code duplication and centralizes
all the task in a single function.
Signed-off-by: Rodrigo Siqueira
---
drivers/staging/iio/meter/ade7854-spi.c | 132 ++--
1 file changed, 41 insertions(+), 91 deletions(-)
diff --git a/drivers/s
On 14/03/2018 at 16:35:21 +0100, Arnd Bergmann wrote:
> The tile architecture is getting removed, so this driver is
> no longer needed.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Alexandre Belloni
> ---
> drivers/rtc/Kconfig| 7 ---
> drivers/rtc/Makefile | 1 -
> drivers/rtc/rtc-til
On 14/03/2018 at 16:35:22 +0100, Arnd Bergmann wrote:
> The blackfin architecture is getting removed, so this one is
> now obsolete.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Alexandre Belloni
> ---
> drivers/rtc/Kconfig| 10 --
> drivers/rtc/Makefile | 1 -
> drivers/rtc/rtc-bfin.c
Based on the previous patches, this patch supports the
LPC host on hip06/hip07 for ACPI FW.
It is the responsibility of the LPC host driver to
enumerate the child devices, as the ACPI scan code will
not enumerate children of "indirect IO" hosts.
The ACPI table for the LPC host controller and the
On 03/14/2018 09:04 PM, jacopo mondi wrote:
>>> Add DRM bridge driver for Thine THC63LVD1024 LVDS to digital parallel
>>> output decoder.
>>>
>>> Signed-off-by: Jacopo Mondi
>> [...]
>>> diff --git a/drivers/gpu/drm/bridge/thc63lvd1024.c
>>> b/drivers/gpu/drm/bridge/thc63lvd1024.c
>>> new file m
From: Zhichang Yuan
The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in
I/O port addresses. This patch implements the LPC host controller driver
which perform the I/O operations on the underlying hardware.
We don't want to touch those existing peripherals' driver, such as
Added maintainer for drivers/bus/hisi_lpc.c
Signed-off-by: John Garry
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c187bc8..cd4f9dc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6403,6 +6403,13 @@ W: http://www.hisilicon.com
S
From: Gabriele Paoloni
In preparation for having the PCI MMIO helpers to use the new generic
I/O space management(logical PIO) we need to add the fwnode handler as
extra input parameter.
This patch changes the signature of pci_register_io_range() and of
its callers as needed.
Signed-off-by: Gabr
On Wed, Mar 14, 2018 at 7:49 PM, Bjorn Helgaas wrote:
> On Wed, Mar 14, 2018 at 06:31:38PM +0200, Andy Shevchenko wrote:
>> On Tue, Mar 13, 2018 at 11:45 PM, Bjorn Helgaas wrote:
>> > If a device already has MSI or MSI-X enabled, there's no need to set up its
>> > legacy INTx interrupt.
>>
>> Ju
701 - 800 of 1242 matches
Mail list logo
