On Mon, 2019-06-24 at 08:16 +0200, Christoph Hellwig wrote:
> On Thu, Jun 20, 2019 at 04:11:26PM +0800, Daniel Drake wrote:
> > On Thu, Jun 20, 2019 at 2:11 PM Christoph Hellwig wrote:
> > > The Linux NVMe driver will deal with NVMe as specified plus whatever
> > > minor tweaks we'll need for smal
Because as a matter of policy the driver has no business knowing the
actual bridge. Even if we'd agree that a driver workaround would be
the right thing it has to be discoverable by an actual interface and
not a system type or root port PCI ID.
On Mon, 24 Jun 2019 at 01:36, Chanwoo Choi wrote:
>
> On 19. 6. 24. 오전 4:16, Krzysztof Kozlowski wrote:
> > On Sun, 23 Jun 2019 at 06:31, Chanwoo Choi wrote:
> >>
> >> Hi Krzysztof,
> >>
> >> 2019년 6월 23일 (일) 오전 4:20, Krzysztof Kozlowski 님이 작성:
> >>>
> >>> Enable support for Mali GPU with Panfros
On Mon, Jun 17, 2019 at 11:35 AM Oded Gabbay wrote:
>
> On Mon, Jun 17, 2019 at 11:19 AM Christoph Hellwig wrote:
> >
> > On Sun, Jun 16, 2019 at 02:24:08PM +0300, Oded Gabbay wrote:
> > > So the alternative is that my device won't work on POWER9.
> >
> > The alternative is that we fix the powerp
Hi Andrew,
>> +enum {
>> +MACB_SERDES_RATE_5_PT_15625Gbps = 5,
>> +MACB_SERDES_RATE_10_PT_3125Gbps = 10,
>> +};
>What do the units mean here? Why would you clock the SERDES at 15Tbps,
>or 3Tbps? 3.125Mbps would give you 2.5Gbps when using 8b/10b encoding.
>
MACB_SERDES_RATE_5_PT_15625Gbps
On 12-06-19, 19:52, jassisinghb...@gmail.com wrote:
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
Do we need both, IIRC of_dma.h does include of.h!
> +/* mc->vc.lock must be held by caller */
> +static void milbe
>Which Clause 45 PHY are you using?
I am using emulated PHY in our CSP environment.
This is using 10G generic PHY driver, with PHY having compatible =
"ethernet-phy-ieee802.3-c45"
Hi Andrew,
Can I add your "Reviewed-by" tag for this patch. You added it to this patch in
last series.
Regards,
Pa
On Thu, Jun 20, 2019 at 11:37:52PM +0530, Puranjay Mohan wrote:
> Rename the PCI_REV_ID define to PCI_REVISION_ID in skfbi.h
> and drvfbi.c to make it compatible with the pci_regs.h
> which defines it as PCI_REVISION_ID.
We already cache the revision in struct pci_dev. In doubt you should
use tha
On Mon, Jun 24, 2019 at 07:33:51AM +0200, Christophe JAILLET wrote:
> Do not allocate memory with GFP_KERNEL when holding a spin_lock, it may
> sleep. Use GFP_NOWAIT instead.
>
checking for this in the rest of the kernel with a cocci spatch
virtual report
@nonatomic@
position p;
identifier var;
Can you send me the patch formally so that I can queue it up for the
dma-mapping tree?
>> +if (change_interface) {
>> +if (bp->phy_interface == PHY_INTERFACE_MODE_SGMII) {
>> +gem_writel(bp, NCFGR, ~GEM_BIT(SGMIIEN) &
>> + ~GEM_BIT(PCSSEL) &
>> + gem_readl(bp, NCFGR));
>> +
On 20-06-19, 15:59, Sameer Pujar wrote:
> > > > So can you explain me what is the difference here that the peripheral
> > > > cannot configure and use burst size with passing fifo depth?
> > > Say for example FIFO_THRESHOLD is programmed as 16 WORDS, BURST_SIZE as 8
> > > WORDS.
> > > ADMAIF does
On Tue, Jun 18, 2019 at 12:08:45AM +0200, Rafael J. Wysocki wrote:
> On Fri, Jun 14, 2019 at 7:54 PM Suzuki K Poulose
> wrote:
> >
> > The prototype of bus_find_device() will be unified with that of
> > class_find_device() subsequently, but for this purpose the callback
> > functions passed to it
A buffer(kexec boot command line arguments) measured into IMA
measuremnt list cannot be appraised, without already being
aware of the buffer contents. Since hashes are non-reversible,
raw buffer is needed for validation or regenerating hash for
appraisal/attestation.
Add support to store/read the
The kexec boot command line arguments are not currently being
measured.
Currently during soft reboot(kexec)
- the PCRS are not reset
- the command line arguments used for the next kernel are not measured.
This gives the impression to the secure boot attestation that a cold boot took
place.
Fo
During soft reboot(kexec_file_load) boot command line
arguments are not measured.
Call ima hook ima_kexec_cmdline to measure the boot command line
arguments into IMA measurement list.
- call ima_kexec_cmdline from kexec_file_load.
- move the call ima_add_kexec_buffer after the cmdline
args have b
Currently during soft reboot(kexec_file_load) boot command line
arguments are not measured. Define hooks needed to measure kexec
command line arguments during soft reboot(kexec_file_load).
- A new ima hook ima_kexec_cmdline is defined to be called by the
kexec code.
- A new function process_buffer
Realtek RTL8822BE BT chip on ASUS X420FA cannot be turned on correctly
after on-off several times. Bluetooth daemon sets BT mode failed when
this issue happens.
bluetoothd[1576]: Failed to set mode: Failed (0x03)
If BT is tunred off, then turned on again, it works correctly again.
According to t
>From: Russell King - ARM Linux admin
>On Sun, Jun 23, 2019 at 10:17:37AM +0100, Parshuram Thombare wrote:
>> +switch (state->interface) {
>> +case PHY_INTERFACE_MODE_GMII:
>> +case PHY_INTERFACE_MODE_RGMII:
>> +if (bp->caps & MACB_CAPS_GIGABIT_MODE_AVAILABLE) {
>> +
Our patch to add support for the FU540-C000 broke compilation on at
least powerpc allyesconfig, which was found as part of the linux-next
build regression tests. This must have somehow slipped through the
cracks, as the patch has been reverted in linux-next for a while now. This
patch applies on
The patch to add support for the FU540-C000 added a dependency on
COMMON_CLK, but didn't express that via Kconfig. This fixes the build
failure by adding CONFIG_MACB_FU540, which depends on COMMON_CLK and
conditionally enables the FU540-C000 support.
I've built this with a powerpc allyesconfig (w
When touching the Kconfig for this driver I noticed that both the
Kconfig help text and a comment referred to this being an Atmel driver.
As far as I know, this is a Cadence driver. The fix is just
s/Atmel/Cadence/, but I did go and re-wrap the Kconfig help text as that
change caused it to go over
On Thu, Jun 20, 2019 at 04:11:26PM +0800, Daniel Drake wrote:
> On Thu, Jun 20, 2019 at 2:11 PM Christoph Hellwig wrote:
> > The Linux NVMe driver will deal with NVMe as specified plus whatever
> > minor tweaks we'll need for small bugs. Hiding it behind an AHCI
> > device is completely out of sc
Allow multiple firmware file versions in table and load them in
increasing order as we find them in the file system.
Tested-by: Christian Lamparter
Signed-off-by: Vinod Koul
Cc: Yoshihiro Shimoda
Cc: Christian Lamparter
---
drivers/usb/host/xhci-pci.c | 47 +++-
uPD720201 supports ROM and allows software to program the ROM and boot
from it. Add support for detecting if ROM is present, if so load the ROM
if not programmed earlier.
Tested-by: Christian Lamparter
Signed-off-by: Vinod Koul
Cc: Yoshihiro Shimoda
Cc: Christian Lamparter
---
drivers/usb/hos
Instead of using register values and fields lets define them and
use in the driver.
Tested-by: Christian Lamparter
Signed-off-by: Vinod Koul
Cc: Yoshihiro Shimoda
Cc: Christian Lamparter
---
drivers/usb/host/xhci-pci.c | 60 ++---
1 file changed, 43 insertions(
From: Christian Lamparter
This patch adds a firmware loader for the uPD720201K8-711-BAC-A
and uPD720202K8-711-BAA-A variant. Both of these chips are listed
in Renesas' R19UH0078EJ0500 Rev.5.00 "User's Manual: Hardware" as
devices which need the firmware loader on page 2 in order to
work as they "
This series add support for Renesas USB controllers uPD720201 and uPD720202.
These require firmware to be loaded and in case devices have ROM those can
also be programmed if empty. If ROM is programmed, it runs from ROM as well.
This includes two patches from Christian which supported these contro
On Mon, Jun 24, 2019 at 1:16 PM Anshuman Khandual
wrote:
>
>
>
> On 06/24/2019 09:51 AM, Pingfan Liu wrote:
> > The current pfn_range_valid_gigantic() rejects the pud huge page allocation
> > if there is a pmd huge page inside the candidate range.
> >
> > But pud huge resource is more rare, which
On 21-06-19, 15:23, Daniel Lezcano wrote:
> The cpufreq_cooling_unregister() function uses now the policy to
> unregister itself. The only purpose of the cooling device pointer is
> to unregister the cpu cooling device.
>
> As there is no more need of this pointer, remove it.
>
> Signed-off-by: D
On 21-06-19, 15:23, Daniel Lezcano wrote:
> The cpufreq_cooling_unregister() function uses now the policy to
> unregister itself. The only purpose of the cooling device pointer is
> to unregister the cpu cooling device.
>
> As there is no more need of this pointer, remove it.
>
> Signed-off-by: D
On 21-06-19, 15:23, Daniel Lezcano wrote:
> The cpufreq_cooling_unregister() function uses now the policy to
> unregister itself. The only purpose of the cooling device pointer is
> to unregister the cpu cooling device.
>
> As there is no more need of this pointer, remove it.
>
> Signed-off-by: D
On Mon, Jun 24, 2019 at 07:40:33AM +0200, Enrico Weigelt, metux IT consult
wrote:
> From: Enrico Weigelt
>
> Add more helper macros for trivial driver init cases, similar to the
> already existing module_platform_driver() or module_i2c_driver().
>
> This helps to reduce driver init boilerplate.
On 21-06-19, 15:22, Daniel Lezcano wrote:
> The cpufreq_cooling_unregister() function uses now the policy to
> unregister itself. The only purpose of the cooling device pointer is
> to unregister the cpu cooling device.
>
> As there is no more need of this pointer, remove it.
>
> Signed-off-by: D
On 21-06-19, 15:22, Daniel Lezcano wrote:
> Currently the function cpufreq_cooling_register() returns a cooling
> device pointer which is used back as a pointer to call the function
> cpufreq_cooling_unregister(). Even if it is correct, it would make
> sense to not leak the structure inside a cpufr
Hi,
Ran Wang writes:
>> >> > >> >> > /* Global Debug Queue/FIFO Space Available Register */
>> >> > >> >> > #define DWC3_GDBGFIFOSPACE_NUM(n) ((n) & 0x1f)
>> >> > >> >> > #define DWC3_GDBGFIFOSPACE_TYPE(n) (((n) << 5) & 0x1e0)
>> >> > >> >> > @@ -859,6 +867,7 @@ struct dwc3_scratchp
Hi Leo,
Applied the patch 10-11/11 to my tree, thanks!
Chunyan
Chunyan
On Wed, 8 May 2019 at 10:21, Leo Yan wrote:
>
> CoreSight DT bindings have been updated, thus the old compatible strings
> are obsolete and the drivers will report warning if DTS uses these
> obsolete strings.
>
> This pa
On Mon, Jun 24, 2019 at 1:03 PM Ira Weiny wrote:
>
> On Mon, Jun 24, 2019 at 12:21:08PM +0800, Pingfan Liu wrote:
> > The current pfn_range_valid_gigantic() rejects the pud huge page allocation
> > if there is a pmd huge page inside the candidate range.
> >
> > But pud huge resource is more rare,
We have historically decided that we want to preallocate the xfs_trans
structure at writeback time so that we don't have to allocate on in
the I/O completion handler. But we treat unwrittent extent and COW
fork conversions different already, which proves that the transaction
allocations in the end
Takes the xfs writeback code and move it to iomap.c. A new structure
with three methods is added as the abstraction from the generic
writeback code to the file system. These methods are used to map
blocks, submit an ioend, and cancel a page that encountered an error
before it was added to an ioen
Hello Richard,
Nice to see you upstreaming this! Thumbs up!
Just few remarks to pmic node from me:
On Thu, Jun 20, 2019 at 04:32:52PM +0300, Andra Danciu wrote:
> From: Richard Hu
>
> The current level of support yields a working console and is able to boot
> userspace from an initial ramdisk
The fail argument is long gone, update the comment.
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
index 9cceb90e77c5..dc60aec0c5a7 100644
--- a/fs/xfs/xfs_aops.c
+++ b/fs/xfs/xfs_ao
Instead of a magic flag for xfs_trans_alloc, just ensure all callers
that can't relclaim through the file system use memalloc_nofs_save to
set the per-task nofs flag.
Signed-off-by: Christoph Hellwig
---
fs/xfs/libxfs/xfs_shared.h | 1 -
fs/xfs/xfs_aops.c | 12 +---
fs/xfs/xfs_
In preparation for moving the XFS writeback code to fs/iomap.c, switch
it to use struct iomap instead of the XFS-specific struct xfs_bmbt_irec.
Signed-off-by: Christoph Hellwig
---
fs/xfs/libxfs/xfs_bmap.c | 14 +--
fs/xfs/libxfs/xfs_bmap.h | 3 +-
fs/xfs/xfs_aops.c| 80
Currently we don't overwrite the flags field in the iomap in
xfs_bmbt_to_iomap. This works fine with 0-initialized iomaps on stack,
but is harmful once we want to be able to reuse an iomap in the
writeback code. Replace the shared paramter with a set of initial
flags an thus ensures the flags fie
Lift the xfs code for tracing address space operations to the iomap
layer.
Signed-off-by: Christoph Hellwig
---
fs/iomap.c | 13 +-
fs/xfs/xfs_aops.c| 27 ++--
fs/xfs/xfs_trace.h | 65
include/trace/events/iomap.h |
Compare the block layer status directly instead of converting it to
an errno first.
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
index 017b87b7765f..acbd73976067 10
Introduce two nicely abstracted helper, which can be moved to the
iomap code later. Also use list_pop and list_first_entry_or_null
to simplify the code a bit.
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.c | 66 ++-
1 file changed, 36 insertio
In preparation for moving the writeback code to iomap.c, replace the
XFS-specific COW fork concept with the iomap IOMAP_F_SHARED flag.
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.c | 40 +---
fs/xfs/xfs_aops.h | 2 +-
2 files changed, 22 insertions(+
Move setting up operation and write hint to xfs_alloc_ioend, and
then just copy over all needed information from the previous bio
in xfs_chain_bio and stop passing various parameters to it.
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.c | 35 +--
1 file ch
We have a very common pattern where we want to delete the first entry
from a list and return it as the properly typed container structure.
Add a list_pop helper to implement this behavior.
Signed-off-by: Christoph Hellwig
---
include/linux/list.h | 22 ++
1 file changed, 22
Hi all,
this series cleans up the xfs writepage code and then lifts it to
fs/iomap.c so that it could be use by other file system. I've been
wanting to this for a while so that I could eventually convert gfs2
over to it, but I never got to it. Now Damien has a new zonefs
file system for semi-raw
Hi all,
Today's linux-next merge of the devicetree tree got conflicts in:
scripts/dtc/Makefile.dtc
scripts/dtc/libfdt/Makefile.libfdt
between commit:
ec8f24b7faaf ("treewide: Add SPDX license identifier - Makefile/Kconfig")
from Linus' tree and commit:
12869ecd5eef ("scripts/dtc: Upda
Hi,
>
>
> From: Bean Huo
>
> This series patch is to fix several typos and fix one issue of twice
> completing ufs-bsg job in case of UPIU/DME command failed.
>
> Changed since v1:
> - split v1 patch
> - add fixes tag
> - delete needless blank line
>
> Bean Huo (3):
> scsi: ufs
Doing the indirection through macros for the regs accessors just
makes them harder to read, so implement the helpers directly.
Note that only the helpers actually used are implemented now.
Signed-off-by: Christoph Hellwig
Acked-by: Catalin Marinas
---
arch/arm64/include/asm/ptrace.h | 31 +
Doing the indirection through macros for the regs accessors just
makes them harder to read, so implement the helpers directly.
Note that only the helpers actually used are implemented now.
Signed-off-by: Christoph Hellwig
---
arch/sh/include/asm/ptrace.h | 29 +
1 fi
Hi all,
asm-generic/ptrace.h is a little weird in that it doesn't actually
implement any functionality, but it provided multiple layers of macros
that just implement trivial inline functions. We implement those
directly in the few architectures and be off with a much simpler
design.
I'm not sure
Doing the indirection through macros for the regs accessors just
makes them harder to read, so implement the helpers directly.
Note that only the helpers actually used are implemented now.
Signed-off-by: Christoph Hellwig
Acked-by: Ingo Molnar
Acked-by: Oleg Nesterov
---
arch/x86/include/asm/
No one is using this header anymore.
Signed-off-by: Christoph Hellwig
Acked-by: Arnd Bergmann
Acked-by: Oleg Nesterov
---
MAINTAINERS| 1 -
arch/mips/include/asm/ptrace.h | 5 ---
include/asm-generic/ptrace.h | 73 --
3 files changed, 79
Doing the indirection through macros for the regs accessors just
makes them harder to read, so implement the helpers directly.
Note that only the helpers actually used are implemented now.
Signed-off-by: Christoph Hellwig
---
arch/powerpc/include/asm/ptrace.h | 29 ++---
On 6/21/19 4:07 PM, Bharath Vedartham wrote:
> Do you think this could cause a race condition between
> __setup_per_zone_wmarks and pgdat_watermark_boosted which checks whether
> the watermark_boost of each zone is non-zero? pgdat_watermark_boosted is
> not called with a zone lock.
> Here is a prob
Signed-off-by: Christoph Hellwig
Reviewed-by: Vladimir Murzin
---
include/linux/mm.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index dd0b5f4e1e45..69843ee0c5f8 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -2756,7 +2756,13 @@
From: Damien Le Moal
When in M-Mode, we can use the mhartid CSR to get the ID of the running
HART. Doing so, direct M-Mode boot without firmware is possible.
Signed-off-by: Damien Le Moal
Signed-off-by: Christoph Hellwig
---
arch/riscv/kernel/head.S | 8
1 file changed, 8 insertions(
RISC-V has the concept of a cpu level interrupt controller. Part of it
is expose as bits in the status registers, and 2 new CSRs per privilege
level in the instruction set, but the machanisms to trigger IPIs and
timer events, as well as reading the actual timer value are not
specified in the RISC-
The numerical levels for External/Timer/Software interrupts differ
between S-mode and M-mode.
Signed-off-by: Christoph Hellwig
---
arch/riscv/kernel/irq.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/riscv/kernel/irq.c b/arch/riscv/kernel/irq.c
index 804f
On 21.06.19 23:17, Wolfram Sang wrote:
> On Mon, Jun 17, 2019 at 08:39:37PM +0200, Enrico Weigelt, metux IT consult
> wrote:
>> From: Enrico Weigelt
>>
>> Add more helper macros for trivial driver init cases, similar to the
>> already existing module_i2c_driver()+friends - now for those which
>>
We can't expose UAPI symbols differently based on CONFIG_ symbols, as
userspace won't have them available. Instead always define the flag,
but only respect it based on the config option.
Signed-off-by: Christoph Hellwig
Reviewed-by: Vladimir Murzin
---
arch/xtensa/include/uapi/asm/mman.h|
For TPM2-based systems, retrieve the TCG log from the TPM2 ACPI table.
Signed-off-by: Jordan Hand
---
v2:
- Apologies, v1 had a silly compile error
drivers/char/tpm/eventlog/acpi.c | 67 +++-
1 file changed, 48 insertions(+), 19 deletions(-)
diff --git a/drivers/cha
The kernel runs in M-mode without using page tables, and thus can't run
bare metal without help from additional firmware.
Most of the patch is just stubbing out code not needed without page
tables, but there is an interesting detail in the signals implementation:
- The normal RISC-V syscall ABI
Switch to our own constant for the satp register instead of using
the old name from a legacy version of the privileged spec.
Signed-off-by: Christoph Hellwig
---
arch/riscv/mm/context.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/arch/riscv/mm/context.c b/arch/riscv
From: Damien Le Moal
Do not allow selecting SBI related options with MMU option not set.
Signed-off-by: Damien Le Moal
Signed-off-by: Christoph Hellwig
---
drivers/tty/hvc/Kconfig| 2 +-
drivers/tty/serial/Kconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/driv
When we get booted we want a clear slate without any leaks from previous
supervisors or the firmware. Flush the instruction cache and then clear
all registers to known good values. This is really important for the
upcoming nommu support that runs on M-mode, but can't really harm when
running in S
Only call the SBI code if we are not running in M mode, and if we didn't
do the SBI call, or it didn't succeed call wfi in a loop to at least
save some power.
Signed-off-by: Christoph Hellwig
---
arch/riscv/kernel/reset.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/ar
The RISC-V ISA only supports flushing the instruction cache for the local
CPU core. For normal S-mode Linux remote flushing is offloaded to
machine mode using ecalls, but for M-mode Linux we'll have to do it
ourselves. Use the same implementation as all the existing open source
SBI implementation
Many of the privileged CSRs exist in a supervisor and machine version
that are used very similarly. Provide a new X-naming layer so that
we don't have to ifdef everywhere for M-mode Linux support.
Contains contributions from Damien Le Moal .
Signed-off-by: Christoph Hellwig
---
arch/riscv/Kcon
There is no SBI when we run in M-mode, so fail the compile for any code
trying to use SBI calls.
Signed-off-by: Christoph Hellwig
---
arch/riscv/include/asm/sbi.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/riscv/include/asm/sbi.h b/arch/riscv/include/asm/sbi.h
in
This allows just loading the kernel at a pre-set address without
qemu going bonkers trying to map the ELF file.
Signed-off-by: Christoph Hellwig
---
arch/riscv/Makefile| 13 +
arch/riscv/boot/Makefile | 7 ++-
arch/riscv/boot/loader.S | 8
arch/riscv/boot/l
This prepare for adding native non-SBI IPI code.
Signed-off-by: Christoph Hellwig
---
arch/riscv/kernel/smp.c | 55 +++--
1 file changed, 31 insertions(+), 24 deletions(-)
diff --git a/arch/riscv/kernel/smp.c b/arch/riscv/kernel/smp.c
index 5a9834503a2f..8cd7
When running in M-mode we still the S-mode plic handlers in the DT.
Ignore them by setting the maximum threshold.
Signed-off-by: Christoph Hellwig
---
drivers/irqchip/irq-sifive-plic.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/irqchip/irq-sifive-pl
The whole header file deals with swap entries and PTEs, none of which
can exist for nommu builds.
Signed-off-by: Christoph Hellwig
---
include/linux/swapops.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/linux/swapops.h b/include/linux/swapops.h
index 4d961668
Hi all,
below is a series to support nommu mode on RISC-V. For now this series
just works under qemu with the qemu-virt platform, but Damien has also
been able to get kernel based on this tree with additional driver hacks
to work on the Kendryte KD210, but that will take a while to cleanup
an ups
On 6/20/2019 9:51 PM, Martin Blumenstingl wrote:
Use a 1us AHB idle timeout in dwc2_core_reset() and make it
consistent with the other "wait for AHB master IDLE state" ocurrences.
This fixes a problem for me where dwc2 would not want to initialize when
updating to 4.19 on a MIPS Lantiq VRX20
Hi folks,
this is v3 of my siox/gpio series from last week.
v3: fixed subject and formatting pointed out by Uwe,
second patch (gpio-siox.c) already acked by him
v2: fixed the typos pointed out by Uwe.
--mtx
From: Enrico Weigelt
Add more helper macros for trivial driver init cases, similar to the
already existing module_platform_driver() or module_i2c_driver().
This helps to reduce driver init boilerplate.
Signed-off-by: Enrico Weigelt
---
include/linux/siox.h | 10 ++
1 file changed, 10
From: Enrico Weigelt
Reduce driver init boilerplate by using the new
module_siox_driver() macro.
Signed-off-by: Enrico Weigelt
---
drivers/gpio/gpio-siox.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/gpio/gpio-siox.c b/drivers/gpio/gpio-siox.c
inde
Sekhar, Bartosz,
if the sparse warning is not fixed, the driver won't hit this kernel
version. Please fix it before the two next days otherwise it won't make
it for v5.4.
Thanks
-- Daniel
On 14/06/2019 12:39, Sekhar Nori wrote:
> Hi Daniel,
>
> On 05/06/19 2:03 PM, Bartosz Golaszewski wro
On Mon, Jun 24, 2019 at 1:32 PM Pingfan Liu wrote:
>
> On Mon, Jun 24, 2019 at 12:43 PM Ira Weiny wrote:
> >
> > On Mon, Jun 24, 2019 at 12:12:41PM +0800, Pingfan Liu wrote:
> > > Both hugetlb and thp locate on the same migration type of pageblock, since
> > > they are allocated from a free_list[
Do not allocate memory with GFP_KERNEL when holding a spin_lock, it may
sleep. Use GFP_NOWAIT instead.
Fixes: 950fd867c635 ("staging: bcm2835-camera: Replace open-coded idr with a
struct idr.")
Signed-off-by: Christophe JAILLET
---
drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c | 2 +
On 18.06.19 18:17, Uwe Kleine-König wrote:
Hi,
> I like the change. Just noticed that the Subject line is a bit strange>
> though. if "more for" is proper English then it's news to me. I'd
write:> > siox: add helper macro to simplify driver registration
Good point, seems I've must have bee
On Mon, Jun 24, 2019 at 12:43 PM Ira Weiny wrote:
>
> On Mon, Jun 24, 2019 at 12:12:41PM +0800, Pingfan Liu wrote:
> > Both hugetlb and thp locate on the same migration type of pageblock, since
> > they are allocated from a free_list[]. Based on this fact, it is enough to
> > check on a single sub
Cleanup DBI read and write APIs by removing "__" (underscore) from their
names as there are no no-underscore versions and the underscore versions
are already doing what no-underscore versions typically do. It also removes
passing dbi/dbi2 base address as one of the arguments as the same can be
deri
Add an API to group all the tasks to be done to de-initialize host which
can then be called by any DesignWare core based driver implementations
while adding .remove() support in their respective drivers.
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pimentel
---
Changes from v7:
* None
Changes f
Export all configuration space access APIs and also other APIs to
support host controller drivers of DesignWare core based implementations
while adding support for .remove() hook to build their respective drivers
as modules
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pimentel
---
Changes from v
From: Björn Töpel
Jonathan Lemon has volunteered as an official AF_XDP reviewer. Thank
you, Jonathan!
Signed-off-by: Björn Töpel
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0cfe98a6761a..dd875578d53c 100644
--- a/MAINTAINERS
+++ b/MAINTAI
[This email was generated by a script. Let me know if you have any suggestions
to make it better.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 25 of them as possibly being bugs in the kvm subsystem. I've listed
these reports below, sorted by an algorith
On 06/24/2019 09:51 AM, Pingfan Liu wrote:
> The current pfn_range_valid_gigantic() rejects the pud huge page allocation
> if there is a pmd huge page inside the candidate range.
>
> But pud huge resource is more rare, which should align on 1GB on x86. It is
> worth to allow migrating away pmd
Commit bfe59032bd6127ee190edb30be9381a01765b958 ("net: ethernet:
ti: cpsw: use cpsw as drv data")changes
the driver data to struct cpsw_common *cpsw. This is done
only in probe/remove but the suspend/resume functions are
still left with struct net_device *ndev. Hence fix both
suspend & resume also
[This email was generated by a script. Let me know if you have any suggestions
to make it better.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 27 of them as possibly being bugs in the bluetooth subsystem. I've
listed these reports below, sorted by an al
mm/vmalloc.c: In function ‘pcpu_get_vm_areas’:
mm/vmalloc.c:976:4: warning: ‘lva’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
insert_vmap_area_augment(lva, &va->rb_node,
Signed-off-by: Weitao Hou
---
mm/vmalloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
[This email was generated by a script. Let me know if you have any suggestions
to make it better.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 9 of them as possibly being bugs in the sound subsystem. I've listed
these reports below, sorted by an algorit
1 - 100 of 436 matches
Mail list logo
