Em Fri, Feb 08, 2019 at 03:35:43PM -0700, Mathieu Poirier escreveu:
> After 'commit e22c1c751140 ("perf thread: Don't include symbol.h,
> symbol_conf.h is enough")'
>
> Compilation of the perf tools is broken when using the functionality
> provided by the openCSD library:
>
> [...]
>
> ...
On Thu, 2019-01-10 at 18:58 +0100, Lubomir Rintel wrote:
> Hello!
>
> This is a fifth spin of the patch set that adds support for the Embedded
> Controller on an OLPC XO 1.75 machine.
>
> It notably removes the patches that adjust the battery driver -- those were
> submitted to linux-pm
Em Mon, Feb 11, 2019 at 11:06:27AM +0100, Thomas Richter escreveu:
> On IBM z13 machine types 2964 and 2965 the descriptor
> sizes for sampling and diagnostic sampling entries
> might be missing in the trailer entry and are set to zero.
>
> This leads to a perf report failure when processing
On Mon, Feb 11, 2019 at 1:46 PM Lubomir Rintel wrote:
> Hello Andy & Darren,
>
> I'm wondering if there's anything more I need to do in order for the
> patches 01-07 to be queued for 5.1? I believe I addressed the issues
> that were pointed out and I believe the patch set is already in a good
>
On 10-02-19, 22:26, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix markup warning: insert a blank line before the hint.
>
> Documentation/driver-api/dmaengine/dmatest.rst:63: WARNING: Unexpected
> indentation.
Applied after adding dmaengine subsystem tag, thanks
>
> Signed-off-by: Randy
On 11/02/2019 10:47, Cornelia Huck wrote:
On Mon, 11 Feb 2019 10:20:49 +0100
Pierre Morel wrote:
When facility.76 MSAX3 is present for the guest we must issue a validity
interception if the CRYCBD is not valid.
The bit CRYCBD.31 is an effective field and tested at each guest
level and has
On Mon, Feb 11, 2019 at 10:39 AM Heikki Krogerus
wrote:
> On Thu, Jan 31, 2019 at 03:35:37PM +0200, Heikki Krogerus wrote:
> > On Wed, Jan 30, 2019 at 06:51:56PM +0200, Andy Shevchenko wrote:
> > > On Wed, Jan 30, 2019 at 6:03 PM Heikki Krogerus
> > > wrote:
> > > >
> > > > When the connections
On 11/02/2019 10:57, Will Deacon wrote:
> On Sat, Feb 09, 2019 at 07:34:53PM +0100, AngeloGioacchino Del Regno wrote:
>> From 33fb6d036de273bb71ac1c67d7a91b7a5148e659 Mon Sep 17 00:00:00 2001
>> From: "Angelo G. Del Regno"
>> Date: Sat, 9 Feb 2019 18:56:46 +0100
>> Subject: [PATCH] arm64/io:
On Fri, Feb 08, 2019 at 04:10:07PM +0100, Torsten Duwe wrote:
> In preparation for arm64 supporting ftrace built on other compiler
> options, let's have the arm64 makefiles remove the $(CC_FLAGS_FTRACE)
> flags, whatever these may be, rather than assuming '-pg'.
>
> There should be no
On 08-02-19, 16:30, Federico Vaga wrote:
> It clarifies that the DMA description pointer returned by
> `dmaengine_prep_*` function should not be used after submission.
>
> Signed-off-by: Federico Vaga
> ---
> Documentation/driver-api/dmaengine/client.rst | 7 +++
> 1 file changed, 7
On Mon, 11 Feb 2019 at 12:04, Borislav Petkov wrote:
>
> On Mon, Feb 11, 2019 at 10:46:18AM +, Ard Biesheuvel wrote:
> > As I pointed out in my previous reply, systab will be the wrong type
> > on 32-bit firmware, it needs to be efi_system_table_32_t
>
> Yeah, that seems to work. It boots now
On Fri, Feb 08, 2019 at 04:10:14PM +0100, Torsten Duwe wrote:
> In preparation for arm64 supporting ftrace built on other compiler
> options, let's have makefiles remove the $(CC_FLAGS_FTRACE)
> flags, whatever these may be, rather than assuming '-pg'.
>
> There should be no functional
+ Jason, Marc
Thomas, Jason, Marc,
On 08/02/19 11:04 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> This series ports the davinci platform to using SPARSE_IRQ, cleans up
> the irqchip drivers and moves them over to drivers/irqchip.
>
> The series can be logically split into
On Fri, Feb 08, 2019 at 04:10:14PM +0100, Torsten Duwe wrote:
> In preparation for arm64 supporting ftrace built on other compiler
> options, let's have makefiles remove the $(CC_FLAGS_FTRACE)
> flags, whatever these may be, rather than assuming '-pg'.
>
> There should be no functional
On Sun, Feb 10, 2019 at 09:00:50PM -0500, Waiman Long wrote:
> +static inline int __down_read_trylock(struct rw_semaphore *sem)
> +{
> + long tmp;
> +
> + while ((tmp = atomic_long_read(>count)) >= 0) {
> + if (tmp == atomic_long_cmpxchg_acquire(>count, tmp,
> +
On 05-02-19, 12:03, Nicolas Ferre wrote:
> Complement the identification of errors with stoping the channel and
> dumping the descriptor that led to the error case.
>
> Signed-off-by: Nicolas Ferre
> ---
> drivers/dma/at_xdmac.c | 43 --
> 1 file changed,
On Sun, Feb 10, 2019 at 01:12:12AM +0300, Yauhen Kharuzhy wrote:
> This patch series introduces new driver for controlling LEDs connected
> to Intel Cherry Trail Whiskey Cove PMIC (general-purpose LED and charger
> status led). Only simple 'always on' and blinking modes are supported
> for now, no
On Fri, Feb 08, 2019 at 04:10:11PM +0100, Torsten Duwe wrote:
> In preparation for arm64 supporting ftrace built on other compiler
> options, let's have makefiles remove the $(CC_FLAGS_FTRACE)
> flags, whatever these may be, rather than assuming '-pg'.
> While at it, fix arm32 as well.
>
trivial rule to print out the kernel arch and localversion, so
external tools, like distro packagers, can easily get it.
Signed-off-by: Enrico Weigelt, metux IT consult
---
Makefile | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Makefile b/Makefile
index 86cf35d..68c3e08 100644
---
Add new environment variable KDEB_RULES for controlling where the
generated debian rules are written to. By defaults, it's debian/rules,
but packagers might override it for providing their own rules file.
Signed-off-by: Enrico Weigelt, metux IT consult
---
scripts/package/mkdebian | 5 -
1
We missed some build dependencies in the generated debian/control file.
Signed-off-by: Enrico Weigelt, metux IT consult
---
scripts/package/mkdebian | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
index ff226be..1caaf0b
Hi folks,
here're some small patches for making mkdebian a bit more flexible, so it
can be used eg. with an given debian/rules file.
I'm using this along w/ local (adding debian/rules and .config) in order
to build the kernel via usual debian toolchains (git-buildpackage,
git-buildpackage, ...)
On Mon, Feb 11, 2019 at 8:38 AM Amir Goldstein wrote:
>
> On Sun, Feb 10, 2019 at 8:23 PM syzbot
> wrote:
> > -> #1 (_i_mutex_key[depth]){+.+.}:
> > down_write+0x38/0x90 kernel/locking/rwsem.c:70
> > inode_lock include/linux/fs.h:757 [inline]
> >
* Juergen Gross wrote:
> When limiting memory size via kernel parameter "mem=" this should be
> respected even in case of memory made accessible via a PCI card.
>
> Today this kind of memory won't be made usable in initial memory
> setup as the memory won't be visible in E820 map, but it
On Tuesday, February 5, 2019 1:23:23 PM CET Borislav Petkov wrote:
> On Tue, Feb 05, 2019 at 12:08:00PM +0100, Rafael J. Wysocki wrote:
> > OK, but care to resend and CC linux-acpi too?
>
> Here you go:
>
> ---
> From: Borislav Petkov
>
> Add James to the list of reviewers of the
On Monday, February 11, 2019 12:54:11 PM CET Vinod Koul wrote:
> On 08-02-19, 16:30, Federico Vaga wrote:
> > It clarifies that the DMA description pointer returned by
> > `dmaengine_prep_*` function should not be used after submission.
> >
> > Signed-off-by: Federico Vaga
> > ---
> >
> >
pon., 11 lut 2019 o 12:54 Sekhar Nori napisał(a):
>
> + Jason, Marc
>
> Thomas, Jason, Marc,
>
> On 08/02/19 11:04 PM, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > This series ports the davinci platform to using SPARSE_IRQ, cleans up
> > the irqchip drivers and moves them
Tony,
On 04/02/19 20:00, Tony Lindgren wrote:
> * 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,
On 11.02.2019 10:20, Pierre Morel wrote:
> When facility.76 MSAX3 is present for the guest we must issue a validity
> interception if the CRYCBD is not valid.
>
> The bit CRYCBD.31 is an effective field and tested at each guest
> level and has for effect to mask the facility.76
>
> It follows
On 11/02/2019 13:06, Ingo Molnar wrote:
>
> * Juergen Gross wrote:
>
>> When limiting memory size via kernel parameter "mem=" this should be
>> respected even in case of memory made accessible via a PCI card.
>>
>> Today this kind of memory won't be made usable in initial memory
>> setup as the
Hi Brendan,
On 09/02/2019 00:56, Brendan Higgins wrote:
> On Thu, Dec 6, 2018 at 4:16 AM Kieran Bingham
> wrote:
>>
>> Hi Brendan,
>>
>> On 03/12/2018 23:53, Brendan Higgins wrote:
>>> On Thu, Nov 29, 2018 at 7:45 PM Luis Chamberlain wrote:
On Thu, Nov 29, 2018 at 01:56:37PM +,
On Mon, Feb 11, 2019 at 11:55:27AM +, Ard Biesheuvel wrote:
> It you have CONFIG_EFI_MIXED enabled, you can in fact use 32-bit UEFI
> runtime services from 64-bit Linux, so just using the tables should be
> fine as well, and I don't think we should hide that behind a Kconfig
> option. (Note
From: Rafael J. Wysocki
Devices using the direct-complete optimization are not present it
debug messages printed by the core device suspend and resume code,
which sometimes makes it difficult to diagnose problems related to
them, so add debug messages for those devices.
Signed-off-by: Rafael J.
On Sun, Feb 10, 2019 at 09:28:43AM +, Peng Fan wrote:
> arm64_memory_present is doing same thing as memblocks_present, so
> let's use common code memblocks_present instead of platform
> specific arm64_memory_present.
>
> Signed-off-by: Peng Fan
I already merged a similar one (see commit
On Feb 8, 2019, Tom Li wrote:
> found Alexandre Oliva has stopped maintaining his tree
?!?
I still merge and tag every one of Torvalds' and Greg KH's releases into
the loongson-community tree, resolving trivial conflicts and trying to
verify that it at least builds and passes a smoke test on
>On Thu, Jan 31, 2019 at 11:52:31AM +, Pawel Laszczak wrote:
>> Patch moves switch responsible for decoding descriptor type
>> outside snprintf. It's little improves code readability.
>
>Should that last sentence read: "It improves code readability a little"?
>
Yes, it should.
Thanks
Pawel
Hi Adrian,
On 24/01/19 5:10 PM, Adrian Hunter wrote:
> On 11/01/19 1:08 PM, Faiz Abbas wrote:
>> From: Chunyan Zhang
>>
>> Some standard SD host controllers can support both external dma
>> controllers as well as ADMA/SDMA in which the SD host controller
>> acts as DMA master. TI's omap
Hi Viresh,
On 2019-02-11 10:55, Viresh Kumar wrote:
> On 11-02-19, 10:52, Marek Szyprowski wrote:
>> On 2019-02-11 09:44, Viresh Kumar wrote:
>>> On 07-02-19, 13:22, Marek Szyprowski wrote:
Dear All,
Recent commit 9ac6cb5fbb17 ("i2c: add suspended flag and accessors for
i2c
* Juergen Gross wrote:
> > If PCI devices had physical mmio memory areas above this range, we'd
> > still expect them to work - the option was really only meant to limit
> > RAM.
>
> No, in this case it seems to be real RAM added via PCI. The RAM is
> initially present in the E820 map, but
Hi Jens,
Would you please pick up the following patches for 5.1?
It is a bunch of misc patches this time. A couple of fixes and cleanups.
Andy Shevchenko (2):
lightnvm: Use u64 instead of __le64 for CPU visible side
lightnvm: pblk: Switch to use new generic UUID API
Hans Holmberg (3):
From: Hans Holmberg
pblk_line_meta_free might sleep (it can end up calling vfree, depending
on how we allocate lba lists), and this can lead to a BUG()
if we wake up on a different cpu and release the lock.
As there is no point of grabbing the free lock when pblk has shut down,
remove the lock.
From: Andy Shevchenko
Sparse complains about using strict data types:
drivers/lightnvm/pblk-read.c:254:43: warning: incorrect type in assignment
(different base types)
drivers/lightnvm/pblk-read.c:254:43:expected restricted __le64
drivers/lightnvm/pblk-read.c:254:43:got unsigned long
From: Andy Shevchenko
There are new types and helpers that are supposed to be used in new code.
As a preparation to get rid of legacy types and API functions do
the conversion here.
Signed-off-by: Andy Shevchenko
Reviewed-by: Javier González
Signed-off-by: Matias Bjørling
---
From: Hans Holmberg
pblk stripes writes of minimal write size across all non-offline chunks
in a line, which means that the maximum write pointer delta should not
exceed the minimal write size.
Extend the line write pointer balance check to cover this case, and
ignore the offline chunk wps.
From: Heiner Litz
This patch fixes a race condition where a write is mapped to the last
sectors of a line. The write is synced to the device but the L2P is not
updated yet. When the line is garbage collected before the L2P update
is performed, the sectors are ignored by the GC logic and the line
On Sat, Feb 9, 2019 at 12:55 PM christophe leroy
wrote:
>
> Hi Andrey,
>
> Le 08/02/2019 à 18:40, Andrey Konovalov a écrit :
> > On Fri, Feb 8, 2019 at 6:17 PM Christophe Leroy
> > wrote:
> >>
> >> Hi Daniel,
> >>
> >> Le 08/02/2019 à 17:18, Daniel Axtens a écrit :
> >>> Hi Christophe,
> >>>
>
From: Masahiro Yamada
As the comment block in include/trace/define_trace.h says,
TRACE_INCLUDE_PATH should be a relative path to the define_trace.h
../../drivers/lightnvm is the correct relative path.
../../../drivers/lightnvm is working by coincidence because the top
Makefile adds
From: Javier González
In order to respect mw_cuinits, pblk's write buffer maintains a
backpointer to protect data not yet persisted; when writing to the write
buffer, this backpointer defines a threshold that pblk's rate-limiter
enforces.
On small PU configurations, the following scenarios
From: Hans Holmberg
As chunk metadata is allocated using vmalloc, we need to free it
using vfree.
Fixes: 090ee26fd512 ("lightnvm: use internal allocation for chunk log page")
Signed-off-by: Hans Holmberg
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/pblk-core.c | 2 +-
1 file changed,
From: Bartosz Golaszewski
davinci_intc_base is defined globally in common.c. Define separate
local variables for the aintc and cp-intc drivers and remove the
global one.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/common.c | 2 --
From: Bartosz Golaszewski
Everything is in place now for SPARSE_IRQ. Select it and set
DAVINCI_INTC_START to NR_IRQS.
We now need to include mach/irqs.h in a couple places as it is no
longer indirectly included after selecting SPARSE_IRQ.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David
From: Bartosz Golaszewski
The intc_host_map field in struct davinci_soc_info is not used by any
board. Remove it as part of the interrupt support cleanup.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/cp_intc.c | 5 -
From: Bartosz Golaszewski
Since no offset goes past 0xff - let's drop the 00 prefix for better
readability. While we're at it: convert all hex numbers to lower-case.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/irq.c | 22 +++---
1
From: Bartosz Golaszewski
In preparation for moving the driver to drivers/irqchip do some
cleanup: use a common prefix for all symbols.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/cp_intc.c | 144 ++--
From: Bartosz Golaszewski
We don't need comments explaining what functions with obvious names do.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/cp_intc.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm/mach-davinci/cp_intc.c
From: Bartosz Golaszewski
Add a config structure that will be used by cp-intc-based platforms.
It contains the register range resource and the number of interrupts.
Signed-off-by: Bartosz Golaszewski
---
include/linux/irqchip/irq-davinci-cp-intc.h | 23 +
1 file changed,
From: Bartosz Golaszewski
Use WARN_ON() on eny error in cp-intc initialization and drop all
custom error messages.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/cp_intc.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git
From: Bartosz Golaszewski
Use lowercase letters in hexadecimal numbers in the cp-intc driver as
is done in most of the kernel code base.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/cp_intc.c | 8
1 file changed, 4 insertions(+), 4
From: Bartosz Golaszewski
The fields related to the two davinci interrupt controllers are no
longer used. Remove them.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da830.c | 98 --
arch/arm/mach-davinci/da850.c | 108
From: Bartosz Golaszewski
Add the new-style config structures for da8xx SoCs. They will be used
once we make the cp-intc driver stop using davinci_soc_info.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/da830.c | 10 ++
arch/arm/mach-davinci/da850.c | 10 ++
2
From: Bartosz Golaszewski
Drop tabs from variable initialization. Arrange variables in reverse
christmas-tree order. Add a newline before a return.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/cp_intc.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff
From: Bartosz Golaszewski
The cp-intc driver has now been cleaned up. Move it to drivers/irqchip
where it belongs.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/Kconfig | 8 ++--
arch/arm/mach-davinci/Makefile
From: Bartosz Golaszewski
Raplace all calls to __raw_readl() & __raw_writel() with readl_relaxed()
and writel_relaxed() respectively. It's safe to do as there's no
endianness conversion being done in the code.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/cp_intc.c | 4 ++--
1
From: Bartosz Golaszewski
These includes are no longer required. Remove them.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/irq.c | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/mach-davinci/irq.c b/arch/arm/mach-davinci/irq.c
index
From: Bartosz Golaszewski
Modify the cp-intc driver to take all its configuration from the new
config structure. Stop referencing davinci_soc_info in any way.
Move the declaration for davinci_cp_intc_init() to
irq-davinci-cp-intc.h and make it take the new config structure as
parameter. Convert
From: Bartosz Golaszewski
Replace the GPLv2 license boilerplate with an SPDX identifier and add
myself as a second author.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/cp_intc.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git
The Bosch Guardian is a TI am335x based device.
It's hardware specifications are as follows:
* 256 MB DDR3 memory
* 512 MB NAND Flash
* USB OTG
* RS232
* MicroSD external storage
* LCD Display interface
Signed-off-by: Martyn Welch
---
arch/arm/boot/dts/Makefile| 1 +
From: Bartosz Golaszewski
We're going to extend the cp_intc_init() function with a config
structure so we can drop the intc-related fields from davinci_soc_info.
Once we do it, we won't be able to use this routine directly as the
init_irq callback. Wrap the calls in additional helpers that
From: Bartosz Golaszewski
Once we select SPARSE_IRQ, the interrupt numbers defined in mach/irqs.h
will only signify the hardware interrupt offsets, not the interrupt
numbers seen by linux. Introduce a wrapper macro that translates the
hwirq number to virtual numbers. For now it's just a dummy.
From: Bartosz Golaszewski
In preparation for moving the driver to drivers/irqchip do some
cleanup: use a common prefix for all symbols.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/dm355.c | 2 +-
arch/arm/mach-davinci/dm365.c
From: Bartosz Golaszewski
I've been unable to figure out exactly why, but it seems that the
IRQ_TINT1_TINT34 interrupt for timer 1 needs to be handled as a
level irq, not edge like all others.
Let's move the handler setup out of the aintc driver where it's lived
since the beginning and into the
From: Bartosz Golaszewski
Add the new-style config structures for dm* SoCs. They will be used
once we make the aintc driver stop using davinci_soc_info.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/dm355.c | 11 +++
arch/arm/mach-davinci/dm365.c | 11 +++
> -Original Message-
> From: Catalin Marinas [mailto:catalin.mari...@arm.com]
> Sent: 2019年2月11日 20:21
> To: Peng Fan
> Cc: will.dea...@arm.com; a...@linux-foundation.org;
> r...@linux.vnet.ibm.com; ard.biesheu...@linaro.org; f.faine...@gmail.com;
> robin.mur...@arm.com;
From: Bartosz Golaszewski
Add a config structure that will be used by aintc-based platforms.
It contains the register range resource, number of interrupts and
a list of priorities.
Signed-off-by: Bartosz Golaszewski
---
include/linux/irqchip/irq-davinci-aintc.h | 25 +++
1
From: Bartosz Golaszewski
We're going to extend the davinci_irq_init() function with a config
structure so we can drop the intc-related fields from davinci_soc_info.
Once we do it, we won't be able to use this routine directly as the
init_irq callback. Wrap the calls in additional helpers that
From: Bartosz Golaszewski
Raplace all calls to __raw_readl() & __raw_writel() with readl_relaxed()
and writel_relaxed() respectively. It's safe to do as there's no
endianness conversion being done in the code.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/irq.c | 4 ++--
1 file
From: Bartosz Golaszewski
The aintc driver has now been cleaned up. Move it to drivers/irqchip
where it belongs. There's no device-tree support for any dm* board so
there's no IRQCHIP_OF_DECLARE() - there's only the exported init
function called from machine code.
Signed-off-by: Bartosz
From: Bartosz Golaszewski
Modify the aintc driver to take all its configuration from the new
config structure. Stop referencing davinci_soc_info in any way.
Move the declaration for davinci_aintc_init() to irq-davinci-aintc.h
and make it take the new config structure as parameter. Convert all
From: Bartosz Golaszewski
Replace the GPLv2 or later license boilerplate with an SPDX identifier.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/irq.c | 26 ++
1 file changed, 6 insertions(+), 20 deletions(-)
diff --git a/arch/arm/mach-davinci/irq.c
From: Bartosz Golaszewski
There's no need to have a local header for cp-intc. Move the only
declaration for a public function to common.h. Move all register
offsets into the driver source file and drop all unused defines.
Make cp_intc_of_init() static.
Signed-off-by: Bartosz Golaszewski
From: Bartosz Golaszewski
In order to support SPARSE_IRQ we first need to make davinci use the
generic irq handler for ARM. Translate the legacy assembly to C and
put the irq handlers into their respective drivers (aintc and cp-intc).
Signed-off-by: Bartosz Golaszewski
---
arch/arm/Kconfig
From: Bartosz Golaszewski
The existence of irqs.h in mach-davinci/include/mach only makes sense
without SPARSE_IRQ as it's then expected to define NR_IRQS and is
included from asm/irq.h. As we now support SPARSE_IRQ, this header can
be moved to mach-davinci and used as the source of HW interrupt
From: Bartosz Golaszewski
NOTE: resending due to missing irqchip maintainers in Cc
This series ports the davinci platform to using SPARSE_IRQ, cleans up
the irqchip drivers and moves them over to drivers/irqchip.
The series can be logically split into four parts. The first (1-8) aims
at
From: Bartosz Golaszewski
We need to create an irq domain if we want to select SPARSE_IRQ. The
cp-intc driver already supports it, but aintc doesn't. Use the helpers
provided by the generic irq chip abstraction.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/irq.c | 35
Mon, Feb 11, 2019 at 12:40:00AM CET, f.faine...@gmail.com wrote:
>In preparation for allowing switchdev enabled drivers to veto specific
>attribute settings from within the context of the caller, introduce a
>new switchdev notifier type for port attributes.
>
>Suggested-by: Ido Schimmel
From: Bartosz Golaszewski
We now use the generic ARM irq handler on davinci. There are no more
users that check davinci_intc_type. Remove the variable and all its
references.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/mach-davinci/common.c | 1 -
Mon, Feb 11, 2019 at 12:39:59AM CET, f.faine...@gmail.com wrote:
>Update the section about switchdev drivers having to implement a
>switchdev_port_attr_get() function to return
>SWITCHDEV_ATTR_ID_PORT_PARENT_ID since that is no longer valid after
>commit bccb30254a4a ("net: Get rid of
Hello,
On Mon, Feb 11, 2019 at 04:56:27PM +0530, Yash Shah wrote:
> On Thu, Feb 7, 2019 at 3:47 PM Uwe Kleine-König
> wrote:
> > On Tue, Jan 29, 2019 at 05:13:19PM +0530, Yash Shah wrote:
> > > +struct pwm_sifive_ddata {
> > > + struct pwm_chip chip;
> > > + struct notifier_block
Mon, Feb 11, 2019 at 12:40:01AM CET, f.faine...@gmail.com wrote:
>Following patches will change the way we communicate getting or setting
>a port's attribute and use a blocking notifier to perform those tasks.
>
>Prepare rocker to support receiving notifier events targeting
"addr" function argument is not used in alloc_consistency_checks() at
all, so remove it.
Fixes: becfda68abca ("slub: convert SLAB_DEBUG_FREE to SLAB_CONSISTENCY_CHECKS")
Signed-off-by: Qian Cai
---
mm/slub.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/mm/slub.c
Am Montag, 11. Februar 2019, 12:31:28 CET schrieb Manivannan Sadhasivam:
> Hi Peter,
>
> On Fri, Feb 08, 2019 at 04:45:01PM +, Peter Robinson wrote:
> > Hi Mani,
> >
> > On Thu, Feb 7, 2019 at 5:54 AM Manivannan Sadhasivam
> >
> > wrote:
> > > Add on-board WiFi/BT support for Rock960
On 11/02/2019 13:23, Ingo Molnar wrote:
>
> * Juergen Gross wrote:
>
>>> If PCI devices had physical mmio memory areas above this range, we'd
>>> still expect them to work - the option was really only meant to limit
>>> RAM.
>>
>> No, in this case it seems to be real RAM added via PCI. The
Mon, Feb 11, 2019 at 12:40:02AM CET, f.faine...@gmail.com wrote:
>Following patches will change the way we communicate getting or setting
>a port's attribute and use a blocking notifier to perform those tasks.
>
>Prepare mlxsw to support receiving notifier events targeting
Hi Gustavo,
On 11/02/19 2:45 PM, Gustavo Pimentel wrote:
> On 11/02/2019 05:48, Kishon Vijay Abraham I wrote:
>> Hi Lorenzo,
>>
>> On 08/02/19 5:50 PM, Lorenzo Pieralisi wrote:
>>> On Thu, Dec 06, 2018 at 08:52:25PM +0800, Wen Yang wrote:
kmemdup has implemented the function that kmalloc() +
On Mon, Feb 11, 2019 at 1:06 PM Miklos Szeredi wrote:
>
> On Mon, Feb 11, 2019 at 8:38 AM Amir Goldstein wrote:
> >
> > On Sun, Feb 10, 2019 at 8:23 PM syzbot
> > wrote:
>
> > > -> #1 (_i_mutex_key[depth]){+.+.}:
> > > down_write+0x38/0x90 kernel/locking/rwsem.c:70
> > >
Mon, Feb 11, 2019 at 12:40:03AM CET, f.faine...@gmail.com wrote:
>Following patches will change the way we communicate getting or setting
>a port's attribute and use a blocking notifier to perform those tasks.
>
>Prepare ocelot to support receiving notifier events targeting
On 11/02/19 3:49 PM, Gustavo Pimentel wrote:
> Hi,
>
> On 14/01/2019 11:14, Kishon Vijay Abraham I wrote:
>> Hi Lorenzo,
>>
>> The Endpoint controller driver uses features member in 'struct pci_epc'
>> to advertise the list of supported features to the endpoint function
>> driver.
>>
>> There
Mon, Feb 11, 2019 at 12:40:04AM CET, f.faine...@gmail.com wrote:
>Following patches will change the way we communicate getting or setting
>a port's attribute and use a blocking notifier to perform those tasks.
>
>Prepare ethsw to support receiving notifier events targeting
Mon, Feb 11, 2019 at 12:40:05AM CET, f.faine...@gmail.com wrote:
>Following patches will change the way we communicate getting or setting
>a port's attribute and use a blocking notifier to perform those tasks.
>
>Prepare DSA to support receiving notifier events targeting
On 11.02.19 at 12:40, Andy Shevchenko wrote:
On Mon, Feb 11, 2019 at 10:49 AM David Engraf wrote:
On 11.02.19 at 08:56, David Engraf wrote:
On 09.02.19 at 11:35, Andy Shevchenko wrote:
On Sat, Feb 9, 2019 at 12:08 AM Andrew Morton
wrote:
On Fri, 8 Feb 2019 21:45:21 +0200 Andy Shevchenko
201 - 300 of 2376 matches
Mail list logo
