The reduce_memory() function clampls the available memory to a limit
defined by the "mem=" command line parameter. It takes into account the
amount of already reserved memory and excludes it from the limit
calculations.
Rather than traverse memblocks and remove them by hand, use
pon., 11 lut 2019 o 14:08 Marc Zyngier napisał(a):
>
> On 11/02/2019 12:26, Bartosz Golaszewski wrote:
> > 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
> >
Am Montag, den 11.02.2019, 17:51 -0800 schrieb Andrey Smirnov:
> PCIe IP block has additional clock, "pcie_aux", that needs to be
> controlled by the driver. Add code to support that.
>
> Signed-off-by: Andrey Smirnov
> Cc: Bjorn Helgaas
> Cc: Fabio Estevam
> Cc: Chris Healy
> Cc: Lucas Stach
On Tue, Feb 12, 2019 at 3:00 PM Maxime Ripard wrote:
>
> On Mon, Feb 11, 2019 at 07:37:57PM +0530, Jagan Teki wrote:
> > Hi Maxime,
> >
> > On Fri, Feb 1, 2019 at 8:01 PM Maxime Ripard
> > wrote:
> > >
> > > On Tue, Jan 29, 2019 at 11:01:31PM +0530, Jagan Teki wrote:
> > > > On Tue, Jan 29,
Thanks Again Lee,
On Tue, Feb 12, 2019 at 09:17:23AM +, Lee Jones wrote:
> On Fri, 08 Feb 2019, Matti Vaittinen wrote:
>
> > > I think an exported function with comments would be better.
> > So do you mean you would prefer exported function over the pointer from
> Yes please. Call-back
On 11.02.19 18:02, Greg Kroah-Hartman wrote:
Dear Greg,
No idea if this is the proper location to report this or if I should inform
stable@vger.. , but:
This backport alone is useless without backporting following 2 commits below
also, unless the 2 wifi devices using dynack start off at
On Tue, Feb 12, 2019 at 8:07 AM Viresh Kumar wrote:
>
> Implement the light-weight tear down and bring up helpers to reduce the
> amount of work to do on CPU offline/online operation.
>
> Signed-off-by: Viresh Kumar
> ---
> drivers/cpufreq/cpufreq-dt.c | 17 +
> 1 file changed,
On Mon, Feb 11, 2019 at 04:34:02PM +0100, Maxime Ripard wrote:
> On Mon, Feb 11, 2019 at 02:35:52PM +, Priit Laes wrote:
> > On Wed, Feb 06, 2019 at 04:52:27PM +0100, Maxime Ripard wrote:
> > > Hi,
> > >
> > > On Wed, Feb 06, 2019 at 10:03:09AM +, Priit Laes wrote:
> > > > > > I'm
On Fri, Feb 1, 2019 at 9:12 PM Jagan Teki wrote:
>
> Here is next version changes for Allwinner A64 MIPI-DSI support
>
> This series grouped the changes like previous version[1] with different
> sets to support three different panels types that can fit into the DSI
> controller.
>
> set:1, for
On Fri, Feb 01, 2019 at 01:02:32PM +0530, Rajneesh Bhardwaj wrote:
> Icelake can resue most of the CNL PCH IPs as they are mostly similar.
> This patch enables the PMC Core driver for ICL family.
>
> It also addresses few other minor issues like upper case conversions and
> some tab alignments.
>
On Mon 2019-02-11 08:08:13, Josh Poimboeuf wrote:
> Anyway, I'm not sure about this approach. This patch makes the s390
> livepatch code no longer compilable, turning it into completely dead
> code. So if something changes in the s390 code which causes it to stop
> compiling, nobody will notice.
On Tue, Feb 12, 2019 at 10:40:14AM +0100, Koen Vandeputte wrote:
>
> On 11.02.19 18:02, Greg Kroah-Hartman wrote:
> > >
> > > Dear Greg,
> > >
> > > No idea if this is the proper location to report this or if I should
> > > inform
> > > stable@vger.. , but:
> > >
> > > This backport alone is
With commit 876dd866c084 ("apparmor: Initial implementation of raw
policy blob compression") and SECURITY_APPARMOR is set to '=y'
ZLIB_DEFLATE must be enabled as well for the linker to see the symbols.
aarch64-linux-gnu-ld: security/apparmor/policy_unpack.o: in function
`deflate_compress':
On 12-02-19, 10:43, Rafael J. Wysocki wrote:
> On Tue, Feb 12, 2019 at 8:07 AM Viresh Kumar wrote:
> >
> > Implement the light-weight tear down and bring up helpers to reduce the
> > amount of work to do on CPU offline/online operation.
> >
> > Signed-off-by: Viresh Kumar
> > ---
> >
Add support for hi3559v100-shub-pwm and hisilicon,hi3559v100-pwm
platforms.
Signed-off-by: Mathieu Othacehe
---
Documentation/devicetree/bindings/pwm/pwm-hibvt.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/pwm/pwm-hibvt.txt
Add support for hi3559v100-shub-pwm and hisilicon,hi3559v100-pwm
platforms. They require a special quirk: pwm has to be enabled again
to force duty_cycle refresh.
Signed-off-by: Mathieu Othacehe
---
drivers/pwm/pwm-hibvt.c | 26 +++---
1 file changed, 23 insertions(+), 3
On 2019/2/12 17:14, Li, Aubrey wrote:
> On 2019/2/12 16:22, Thomas Gleixner wrote:
>> On Tue, 12 Feb 2019, Aubrey Li wrote:
>>> diff --git a/arch/x86/include/asm/processor.h
>>> b/arch/x86/include/asm/processor.h
>>> index d53c54b842da..60ee932070fe 100644
>>> ---
From: Jordan Crouse
Try to get the interconnect path for the GPU and vote for the maximum
bandwidth to support all frequencies. This is needed for performance.
Later we will want to scale the bandwidth based on the frequency to
also optimize for power but that will require some device tree
From: Michal Hocko
We have seen several bugs where zonelists have not been initialized
properly and it is not really straightforward to track those bugs down.
One way to help a bit at least is to dump zonelists of each node when
they are (re)initialized.
Signed-off-by: Michal Hocko
---
From: Michal Hocko
Pingfan Liu has reported the following splat
[5.772742] BUG: unable to handle kernel paging request at 2088
[5.773618] PGD 0 P4D 0
[5.773618] Oops: [#1] SMP NOPTI
[5.773618] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.20.0-rc1+ #3
[
Hi,
this has been posted as an RFC previously [1]. There didn't seem to be
any objections so I am reposting this for inclusion. I have added a
debugging patch which prints the zonelist setup for each numa node
for an easier debugging of a broken zonelist setup.
[1]
On Tue, 12 Feb 2019, Bartosz Golaszewski wrote:
> wt., 12 lut 2019 o 09:36 Lee Jones napisał(a):
> >
> > On Tue, 05 Feb 2019, Bartosz Golaszewski wrote:
> >
> > > From: Bartosz Golaszewski
> > >
> > > Add the core mfd driver for max77650 PMIC. We define five sub-devices
> > > for which the
On Tue, 2019-02-05 at 16:53 -0800, Eduardo Valentin wrote:
> On Fri, Feb 01, 2019 at 03:38:10PM +0800, michael@mediatek.com wrote:
> > From: Michael Kao
> >
> > One thermal controller can read four sensors at most,
> > so we need to add controller_offset for the project with
> > more than
On 19-02-11 17:50:09, Lucas Stach wrote:
> Add compatible for i.MX8MQ and add both i.MX7D/S and i.M8MQ
> to the description.
>
> Signed-off-by: Lucas Stach
> ---
> Documentation/devicetree/bindings/nvmem/imx-ocotp.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git
On Tue, Feb 12, 2019 at 10:19:20AM +0100, Bartosz Golaszewski wrote:
> wt., 12 lut 2019 o 10:10 Marc Zyngier napisał(a):
> >
> > On 29/01/2019 08:44, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski
> > >
> > > Provide a more specialized variant of irq_sim_fire() that allows to
> > >
On Mon, Feb 11, 2019 at 07:52:05PM -0800, Bjorn Andersson wrote:
> GPIOs on the SPMI PMIC are numbered 1..ngpio, so the boundary check in
> pmic_gpio_domain_translate() is off by one, correct this.
>
> Fixes: ca69e2d165eb ("qcom: spmi-gpio: add support for hierarchical IRQ chip")
> Signed-off-by:
Commit a893ea15d764 ("tpm: move tpm_chip definition to
include/linux/tpm.h") introduced a build error when both ima and efi is
enabled. What happens is that both headers (ima.h and efi.h) defines the
same 'NONE' constant, and it broke when they started getting included
from the same file.
In file
Commit a893ea15d764 ("tpm: move tpm_chip definition to
include/linux/tpm.h") introduced a build error when both ima and efi is
enabled. What happens is that both headers (ima.h and efi.h) defines the
same 'NONE' constant, and it broke when they started getting included
from the same file.
In file
On Tue, 12 Feb 2019 at 11:09, Anders Roxell wrote:
>
> Commit a893ea15d764 ("tpm: move tpm_chip definition to
> include/linux/tpm.h") introduced a build error when both ima and efi is
> enabled. What happens is that both headers (ima.h and efi.h) defines the
> same 'NONE' constant, and it broke
wt., 12 lut 2019 o 10:55 Lee Jones napisał(a):
>
> On Tue, 12 Feb 2019, Bartosz Golaszewski wrote:
>
> > wt., 12 lut 2019 o 09:36 Lee Jones napisał(a):
> > >
> > > On Tue, 05 Feb 2019, Bartosz Golaszewski wrote:
> > >
> > > > From: Bartosz Golaszewski
> > > >
> > > > Add the core mfd driver for
On 11/02/2019 14:18, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.156 release.
> There are 137 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
> Alternative implementation could be replacing disable preemption with
> rcu_read_lock_sched and stop_machine() with synchronize_sched().
JFYI, starting with v4.20-rc1, synchronize_rcu{,expedited}() also wait
for preempt-disable sections (the intent seems to retire the RCU-sched
update-side
wt., 12 lut 2019 o 11:06 Uwe Kleine-König
napisał(a):
>
> On Tue, Feb 12, 2019 at 10:19:20AM +0100, Bartosz Golaszewski wrote:
> > wt., 12 lut 2019 o 10:10 Marc Zyngier napisał(a):
> > >
> > > On 29/01/2019 08:44, Bartosz Golaszewski wrote:
> > > > From: Bartosz Golaszewski
> > > >
> > > >
On Tue, Feb 12, 2019 at 11:52:38AM +0200, Georgi Djakov wrote:
> From: Jordan Crouse
>
> Try to get the interconnect path for the GPU and vote for the maximum
> bandwidth to support all frequencies. This is needed for performance.
> Later we will want to scale the bandwidth based on the
Hi Steve,
On Mon, 2019-02-11 at 10:24 -0800, Steve Longerbeam wrote:
[...]
> Looking more closely at these coefficients now, I see you are right,
> they are the BT.601 YUV full-range coefficients (Y range 0 to 1, U and V
> range -0.5 to 0.5). Well, not even that -- the coefficients are not
>
On Tue, Feb 12, 2019 at 11:46 AM Anshuman Gupta
wrote:
> On Fri, Feb 01, 2019 at 01:02:32PM +0530, Rajneesh Bhardwaj wrote:
> > Icelake can resue most of the CNL PCH IPs as they are mostly similar.
> > This patch enables the PMC Core driver for ICL family.
> >
> > It also addresses few other
On Tue, 12 Feb 2019, Bartosz Golaszewski wrote:
> wt., 12 lut 2019 o 10:55 Lee Jones napisał(a):
> >
> > On Tue, 12 Feb 2019, Bartosz Golaszewski wrote:
> >
> > > wt., 12 lut 2019 o 09:36 Lee Jones napisał(a):
> > > >
> > > > On Tue, 05 Feb 2019, Bartosz Golaszewski wrote:
> > > >
> > > > >
On Tue, Feb 12, 2019 at 12:16 PM Ard Biesheuvel
wrote:
> On Tue, 12 Feb 2019 at 11:09, Anders Roxell wrote:
> >
> > Commit a893ea15d764 ("tpm: move tpm_chip definition to
> > include/linux/tpm.h") introduced a build error when both ima and efi is
> > enabled. What happens is that both headers
On Tue, Feb 12, 2019 at 10:53:41AM +0100, Michal Hocko wrote:
> Hi,
> this has been posted as an RFC previously [1]. There didn't seem to be
> any objections so I am reposting this for inclusion. I have added a
> debugging patch which prints the zonelist setup for each numa node
> for an easier
On 11/02/2019 14:16, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.99 release.
> There are 205 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Tue, Feb 12, 2019 at 12:15 PM Anders Roxell wrote:
>
> Commit a893ea15d764 ("tpm: move tpm_chip definition to
> include/linux/tpm.h") introduced a build error when both ima and efi is
> enabled. What happens is that both headers (ima.h and efi.h) defines the
> same 'NONE' constant, and it
From: Michal Hocko
Tetsuo has reported that creating a thousands of processes sharing MM
without SIGHAND (aka alien threads) and setting
/proc//oom_score_adj will swamp the kernel log and takes ages [1]
to finish. This is especially worrisome that all that printing is done
under RCU lock and
On Tue, Feb 12, 2019 at 12:21 PM Andy Shevchenko
wrote:
>
> On Tue, Feb 12, 2019 at 12:15 PM Anders Roxell
> wrote:
> >
> > Commit a893ea15d764 ("tpm: move tpm_chip definition to
> > include/linux/tpm.h") introduced a build error when both ima and efi is
> > enabled. What happens is that both
On Tue, Feb 12, 2019 at 12:38 PM Christoph Hellwig wrote:
>
> On Sat, Jan 19, 2019 at 01:28:59PM +, Anup Patel wrote:
> > This patch implements keepinitrd kernel parameter. By default,
> > keepinitrd=1 but users can pass "keepinitrd=0" to free-up
> > initrd memory at boot-time in
On Mon, Feb 11, 2019 at 02:12:25PM -0300, Ezequiel Garcia wrote:
> On Mon, 2019-02-11 at 15:39 +0100, Maxime Ripard wrote:
> >
> > diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> > index d6eed479c3a6..6fc955926bdb 100644
> > --- a/include/uapi/linux/videodev2.h
> >
wt., 12 lut 2019 o 11:18 Lee Jones napisał(a):
>
> On Tue, 12 Feb 2019, Bartosz Golaszewski wrote:
>
> > wt., 12 lut 2019 o 10:55 Lee Jones napisał(a):
> > >
> > > * The declaration of a superfluous struct
> > > * 100 lines of additional/avoidable code
> > > * Hacky hoop jumping trying to
On Mon, Feb 11, 2019 at 8:32 PM Bhardwaj, Rajneesh
wrote:
> On 11-Feb-19 10:11 PM, Anshuman Gupta wrote:
> > On Fri, Feb 01, 2019 at 01:02:33PM +0530, Rajneesh Bhardwaj wrote:
> >> This patch introduces a new debugfs entry to read current Package
> >> cstate residency counters. A similar variant
On Tue, Feb 12, 2019 at 10:49 AM Viresh Kumar wrote:
>
> On 12-02-19, 10:43, Rafael J. Wysocki wrote:
> > On Tue, Feb 12, 2019 at 8:07 AM Viresh Kumar
> > wrote:
> > >
> > > Implement the light-weight tear down and bring up helpers to reduce the
> > > amount of work to do on CPU offline/online
On 09. 02. 19, 12:25, Borislav Petkov wrote:
>> @@ -57,7 +56,7 @@
>> #if defined(CONFIG_TRACE_IRQFLAGS) \
>> || defined(CONFIG_DEBUG_LOCK_ALLOC) \
>> || defined(CONFIG_PREEMPT)
>> -.L_restore:
>> +SYM_CODE_START_LOCAL_NOALIGN(.L_restore)
>> popq %r11
>> popq %r10
>> popq %r9
>>
On 12/02/2019 09:19, Bartosz Golaszewski wrote:
> wt., 12 lut 2019 o 10:10 Marc Zyngier napisał(a):
>>
>> On 29/01/2019 08:44, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski
>>>
>>> Provide a more specialized variant of irq_sim_fire() that allows to
>>> specify the type of the fired
On Tue, Feb 12, 2019 at 4:31 AM Marcos Paulo de Souza
wrote:
> On 2/11/19 5:14 PM, João Paulo Rechi Vita wrote:
> > Hello Marcos,
> > On Sun, Feb 10, 2019 at 5:05 PM Marcos Paulo de Souza
> > wrote:
> > You can check what is being sent by the kernel with evtest, and what
> > is being sent by X
On Thu, Jan 31, 2019 at 3:02 PM Greg KH wrote:
>
> On Thu, Jan 31, 2019 at 11:54:11AM +0800, Kyle Tso wrote:
> > Provide a function to get the partner Source Capabilities.
> >
> > Signed-off-by: Kyle Tso
> > ---
> > drivers/usb/typec/tcpm/tcpm.c | 23 +++
> >
On Fri, Feb 1, 2019 at 2:22 AM Guenter Roeck wrote:
>
> On Thu, Jan 31, 2019 at 08:02:38AM +0100, Greg KH wrote:
> > On Thu, Jan 31, 2019 at 11:54:11AM +0800, Kyle Tso wrote:
> > > Provide a function to get the partner Source Capabilities.
> > >
> > > Signed-off-by: Kyle Tso
> > > ---
> > >
On 12-Feb-19 3:55 PM, Andy Shevchenko wrote:
On Mon, Feb 11, 2019 at 8:32 PM Bhardwaj, Rajneesh
wrote:
On 11-Feb-19 10:11 PM, Anshuman Gupta wrote:
On Fri, Feb 01, 2019 at 01:02:33PM +0530, Rajneesh Bhardwaj wrote:
This patch introduces a new debugfs entry to read current Package
cstate
On Tue, Feb 12, 2019 at 09:30:31AM +0100, Lukas Wunner wrote:
> Instead of modifying the logic in pciehp_handle_presence_or_link_change(),
> you could amend pcie_wait_for_link() to poll PDS until it's set, in
> addition to DLLLA. The rationale would be that although the link is up,
> the
On Feb 12 2019, Anup Patel wrote:
> So in case of initrd we might not want to free-up the RAM but
> we can certainly free-up in case of initramfs.
But the default should be keepinitrd=0, shoudn't it?
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9
wt., 12 lut 2019 o 11:27 Marc Zyngier napisał(a):
>
> On 12/02/2019 09:19, Bartosz Golaszewski wrote:
> > wt., 12 lut 2019 o 10:10 Marc Zyngier napisał(a):
> >>
> >> On 29/01/2019 08:44, Bartosz Golaszewski wrote:
> >>> From: Bartosz Golaszewski
> >>>
> >>> Provide a more specialized variant of
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 +++
From: Bartosz Golaszewski
Add a missing call to request_mem_region() before calling ioremap() to
make sure the region is not being used by anyone else.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/irq.c | 9 +
1 file changed, 9 insertions(+)
diff --git
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
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 | 2 +-
1 file
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
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
The mach/ and asm/ includes are not needed in davinci_keyscan, but they
will cause build problems once we make mach/irqs.h a private header for
mach-davinci.
Remove all unused header includes.
Signed-off-by: Bartosz Golaszewski
---
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 five parts. The first patch
preemptively fixes a problem in an input driver that would have caused
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
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
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
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
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
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
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
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
Add a missing call to request_mem_region() before calling ioremap() to
make sure it's not been requested by another user.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/cp_intc.c | 9 +
1 file changed, 9 insertions(+)
diff --git
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
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
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 | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git
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
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
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
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
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
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
Instead of dumping stack traces, just print a specific error message
in aintc driver.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/irq.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git
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
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
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
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
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/dm355.c | 2 +-
arch/arm/mach-davinci/dm365.c
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
Hi
> -Original Message-
> From: Heikki Krogerus
> Sent: 2019年2月12日 16:51
> To: Jun Li
> Cc: Greg Kroah-Hartman ; Andy Shevchenko
> ; Chen Yu ; Hans de
> Goede ; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2 6/9] usb: roles: Find the muxes by also
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
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 -
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
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
On Tue, Feb 12, 2019 at 12:34 PM Bhardwaj, Rajneesh
wrote:
> On 12-Feb-19 3:55 PM, Andy Shevchenko wrote:
> > On Mon, Feb 11, 2019 at 8:32 PM Bhardwaj, Rajneesh
> > wrote:
> >> On 11-Feb-19 10:11 PM, Anshuman Gupta wrote:
> >>> On Fri, Feb 01, 2019 at 01:02:33PM +0530, Rajneesh Bhardwaj wrote:
Hi Will,
On Mon, Feb 11, 2019 at 9:34 PM Will Deacon wrote:
> Ensure that inX() provides the same ordering guarantees as readX()
> by hooking up __io_par() so that it maps directly to __iormb().
>
> Reported-by: Andrew Murray
> Signed-off-by: Will Deacon
Thanks for your patch!
> ---
Hi,
On Mon, Feb 11, 2019 at 08:21:31PM +0100, Jernej Škrabec wrote:
> > + reg = 0;
> > + /*
> > +* FIXME: This bit tells the video engine to use the default
> > +* quantization matrices. This will obviously need to be
> > +* changed to support the profiles supporting custom
> > +
101 - 200 of 1653 matches
Mail list logo
