This patchset adds basic support for :
- Amlogic G12B, which is very similar to G12A
- The HardKernel Odroid-N2 based on the S922X SoC
The Amlogic G12B SoC is very similar with the G12A SoC, sharing
most of the features and architecture, but with these differences :
- The first CPU cluster only
This patch adds the specific Amlogic G12B clock driver compatible.
G12B clock driver is very close, the main differences are :
- the clock tree is duplicated for the both clusters, and the
SYS_PLL are swapped between the clusters
- G12A has additional clocks like for CSI an other components
This patch support for the specific Amlogic G12B clocks.
G12B clock driver is very close, the main differences are :
- the clock tree is duplicated for the both clusters, and the
SYS_PLL are swapped between the clusters
- G12A has additional clocks like for CSI an other components
Here only
On Amlogic Meson G12b platform, the fclk_div3 seems to be necessary for
the system to operate correctly.
Disabling it cause the entire system to freeze, including peripherals.
This patch patch marks this clock as critical, fixing boot on G12b platforms.
Signed-off-by: Neil Armstrong
---
stable-rc/linux-4.14.y boot: 115 boots: 1 failed, 96 passed with 18 offline
(v4.14.110-122-g662f0922cca4)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.110-122-g662f0922cca4/
Full Build Summary:
On 04.04.19 16:57, David Hildenbrand wrote:
> On 04.04.19 14:59, Oscar Salvador wrote:
>> From: Michal Hocko
>>
>> arch_add_memory, __add_pages take a want_memblock which controls whether
>> the newly added memory should get the sysfs memblock user API (e.g.
>> ZONE_DEVICE users do not want/need
Hi Doug,
Thanks for sending this patch upstream.
On 3/4/19 23:19, Matthias Kaehlcke wrote:
> On Wed, Apr 03, 2019 at 02:08:40PM -0700, Doug Anderson wrote:
>> Hi,
>>
>> On Wed, Apr 3, 2019 at 2:04 PM Matthias Kaehlcke wrote:
+static int cros_ec_xfer_high_pri(struct cros_ec_device *ec_dev,
On Tue, Apr 2, 2019 at 2:25 PM Patrick Venture wrote:
>
> On Mon, Apr 1, 2019 at 8:36 PM Andrew Jeffery wrote:
> >
> >
> >
> > On Thu, 28 Mar 2019, at 07:52, Patrick Venture wrote:
> > > The ASPEED AST2400, and AST2500 in some configurations include a
> > > PCI-to-AHB MMIO bridge. This bridge
On 04.04.19 14:59, Oscar Salvador wrote:
> From: Michal Hocko
>
> arch_add_memory, __add_pages take a want_memblock which controls whether
> the newly added memory should get the sysfs memblock user API (e.g.
> ZONE_DEVICE users do not want/need this interface). Some callers even
> want to
Hi Matthias,
On 2019-04-03 21:44, Matthias Kaehlcke wrote:
On Wed, Apr 03, 2019 at 11:53:26AM +0530, Balakrishna Godavarthi wrote:
+ Harish to update his findings on wcn3998.
Mean time i will perform a regression to detect the failure.
On my system it typically reproduces within a few dozen
From: Shyam Saini
Sent: 04 April 2019 19:58
To: Pankaj Suryawanshi
Cc: linux-kernel@vger.kernel.org; linux...@kvack.org
Subject: [External] Re: CMA area pages information
CAUTION: This email originated from outside of the organization. Do not click
On 27/03/2019 11:51, Jerome Brunet wrote:
> On Wed, 2019-03-27 at 11:33 +0100, Neil Armstrong wrote:
>> On Amlogic Meson G12b platform, the fclk_div3 seems to be necessary for
>> the system to operate correctly.
>>
>> Disabling it cause the entire system to freeze, including peripherals.
>>
>>
On Thu, Apr 4, 2019 at 4:09 PM Christian Brauner wrote:
>
> On Wed, Apr 03, 2019 at 07:08:47PM +0200, Matteo Croce wrote:
> > On Wed, Apr 3, 2019 at 6:40 PM Matteo Croce wrote:
> > >
> > > On Wed, Apr 3, 2019 at 5:51 PM Matthew Wilcox wrote:
> > > >
> > > > On Wed, Apr 03, 2019 at 05:24:26PM
On Tue, Mar 26, 2019 at 03:17:53PM +, Shameer Kolothum wrote:
> HiSilicon erratum 162001800 describes the limitation of
> SMMUv3 PMCG implementation on HiSilicon Hip08 platforms.
>
> On these platforms, the PMCG event counter registers
> (SMMU_PMCG_EVCNTRn) are read only and as a result it
>
On 04.04.19 15:25, Oscar Salvador wrote:
> On Thu, Apr 04, 2019 at 03:18:00PM +0200, David Hildenbrand wrote:
>>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>>> index f206b8b66af1..d8a3e9554aec 100644
>>> --- a/mm/memory_hotplug.c
>>> +++ b/mm/memory_hotplug.c
>>> @@ -1451,15 +1451,11
Hi Marc,
We have considered exposing our interrupt controller both via MADT
OEM-specific entry and via DSDT.
We've chosen MADT OEM-specific entry, because it seemed like a
reasonable placeholder for custom interrupt controller, but we can move
to DSDT, if this seems like a better way to
On Thu, Apr 04, 2019 at 10:09:30AM -0300, Beatriz Martins de Carvalho wrote:
> Fix checkpatch error "ERROR: code indent should use tabs where possible"
> in hal_com_phycfg.c:1726.
>
> Signed-off-by: Beatriz Martins de Carvalho
>
> ---
Looks good. Thanks!
Reviewed-by: Dan Carpenter
regards,
On Wed, Apr 03, 2019 at 02:21:58PM -0700, Fenghua Yu wrote:
> From: Xiaoyao Li
>
> A control bit (bit 29) in TEST_CTL MSR 0x33 will be introduced in
> future x86 processors. When bit 29 is set, the processor causes #AC
> exception for split locked accesses at all CPL.
>
> Please check the
Hi,
On 04-04-19 16:17, Yue Haibing wrote:
From: YueHaibing
As Hans de Goede pointed, using this driver without ACPI
makes little sense, so add ACPI dependency to Kconfig entry
to fix a build error while CONFIG_ACPI is not set.
drivers/extcon/extcon-axp288.c: In function
Hi all
Since upgrading my routers from the 4.14 to the 4.19 kernel series, I
frequently get into the situation that my second (and also third) nic
goes down, with
igb :02:00.0 enp2s0: Reset adapter
Sometimes, it will come up again, sometimes not. I have googled and got
a lot of hits,
On Wed, Apr 3, 2019 at 2:34 PM Evan Green wrote:
>
> Add support in code for the new forms of the host sleep event.
> Detects the presence of this version of the command at runtime,
> and use whichever form the EC supports. At this time, always
> request the default timeout, and only report the
On Wed, Apr 3, 2019 at 2:34 PM Evan Green wrote:
>
> Introduce the command and response structures for the second revision
> of the host sleep event. These structures are part of a new EC change
> that enables detection of failure to enter S0ix. The EC waits a
> kernel-specified timeout (or a
On Thu, 4 Apr 2019, Nicholas Piggin wrote:
> I've been looking at ways to fix suspend breakage with CPU0 as a
> nohz CPU. I started looking at various things like allowing CPU0
> to take over do_timer again temporarily or allowing nohz full
> to be stopped at runtime (that is quite a significant
From: Thor Thayer
Use the new Stratix10 binding format for EDAC nodes.
Signed-off-by: Thor Thayer
Acked-by: Dinh Nguyen
---
v2-3 No change
Resend adds Acked-by.
---
arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 25 ---
1 file changed, 13 insertions(+), 12
From: Thor Thayer
Fix Stratix10 ECC bindings to specify only the single
bit error. On Stratix10 double bit errors are handled
as SErrors instead of interrupts.
Indicate the differences between the ARM64 and ARM32
EDAC architecture in the bindings.
Signed-off-by: Thor Thayer
Acked-by: Rob
From: Thor Thayer
Add peripheral bindings for Stratix10 EDAC to capture
the differences between the ARM64 and ARM32 architecture.
Signed-off-by: Thor Thayer
Reviewed-by: Rob Herring
---
v2-3 No change.
Resend adds Reviewed-by
---
.../devicetree/bindings/edac/socfpga-eccmgr.txt| 106
From: Thor Thayer
This patch series makes the Stratix10 EDAC Bindings
specific to the Stratix10 ARM64 architecture.
Instead of using the Arria10 (ARM32) EDAC bindings for
Stratix10 (ARM64), create Stratix10 specific EDAC bindings
to capture architecture differences between ARM32 and ARM64.
This
On 2019-04-04 07:26:37 [-0700], Andy Lutomirski wrote:
> I think that David was asking whether we could make kernel_fpu_begin()
> regions sometimes be preemptible. The answer is presumably yes, but I
> think that should be a separate effort, and it should be justified
> with improved performance
On Thu, 4 Apr 2019 17:02:01 +0300
"Dmitry V. Levin" wrote:
> According to
> https://lore.kernel.org/lkml/20190330004949.GA15705@guoren-Inspiron-7460/
> the following tags could be added to this patch:
>
> Tested-by: Guo Ren
> Acked-by: Guo Ren
Thanks! Added.
-- Steve
On Thu, 4 Apr 2019 17:02:10 +0300
"Dmitry V. Levin" wrote:
> On Mon, Apr 01, 2019 at 09:41:07AM -0400, Steven Rostedt wrote:
> > From: "Dmitry V. Levin"
> >
> > RISC-V syscall arguments are located in orig_a0,a1..a5 fields
> > of struct pt_regs.
> >
> > Due to an off-by-one bug and a bug in
On Thu, Apr 4, 2019 at 7:14 AM Sebastian Andrzej Siewior
wrote:
>
> On 2019-04-04 14:01:43 [+], David Laight wrote:
> > From: Sebastian Andrzej Siewior
> > > Sent: 03 April 2019 17:41
> > ...
> > > To access the FPU registers in kernel we need:
> > > - disable preemption to avoid that the
* Mukesh Ojha [190404 11:23]:
>
> On 4/4/2019 4:46 PM, Colin King wrote:
> > From: Colin Ian King
> >
> > There is are a couple of spelling mistakes in the Documentation. Fix them.
Thanks will pick this up for v5.2.
Regards,
Tony
From: Pankaj Suryawanshi
Sent: 01 April 2019 16:34
To: linux-kernel@vger.kernel.org; linux...@kvack.org
Subject: Re: CMA area pages information
From: Pankaj Suryawanshi
Sent: 01 April 2019 13:26
To:
From: YueHaibing
As Hans de Goede pointed, using this driver without ACPI
makes little sense, so add ACPI dependency to Kconfig entry
to fix a build error while CONFIG_ACPI is not set.
drivers/extcon/extcon-axp288.c: In function 'axp288_extcon_probe':
drivers/extcon/extcon-axp288.c:363:20:
* Ladislav Michl [190327 08:12]:
> Hello Nathan,
>
> On Tue, Mar 26, 2019 at 10:01:27PM -0700, Nathan Chancellor wrote:
> > Commit 008258d995a6 ("clocksource/drivers/timer-ti-dm: Make
> > omap_dm_timer_set_load_start() static") made omap_dm_time_set_load_start
> > static because its prototype
* Keerthy [190404 06:35]:
> omap_dm_timer_set_load_start is no longer used hence delete the
> function and remove the below warning.
>
> drivers/clocksource/timer-ti-dm.c:589:12:
> warning: ‘omap_dm_timer_set_load_start’ defined but not used
Hmm see earlier "[PATCH]
On 2019-04-04 14:01:43 [+], David Laight wrote:
> From: Sebastian Andrzej Siewior
> > Sent: 03 April 2019 17:41
> ...
> > To access the FPU registers in kernel we need:
> > - disable preemption to avoid that the scheduler switches tasks. By
> > doing so it would set TIF_NEED_FPU_LOAD and the
On Thu, Apr 4, 2019 at 5:24 AM Pavel Machek wrote:
>
> On Mon 2019-03-11 09:29:06, Nick Crews wrote:
> > Thanks for looking this over. I will fix most of your concerns, but
> > have one question.
> >
> > On Fri, Mar 8, 2019 at 2:08 PM Pavel Machek wrote:
> > >
> > > On Fri 2019-03-08 13:38:02,
Hello
I have written a Python script to scan the kernel for unchecked kmalloc()
calls. It found the following instances. I checked them manually, too. I would
like to fix them myself but I do not how to do a proper failure handling. So
maybe someone else can have a look.
Oliver
On Wed, Apr 03, 2019 at 07:08:47PM +0200, Matteo Croce wrote:
> On Wed, Apr 3, 2019 at 6:40 PM Matteo Croce wrote:
> >
> > On Wed, Apr 3, 2019 at 5:51 PM Matthew Wilcox wrote:
> > >
> > > On Wed, Apr 03, 2019 at 05:24:26PM +0200, Matteo Croce wrote:
> > > > On Wed, Apr 3, 2019 at 4:02 PM
+cc Rafael and linux-acpi
On 2019/4/4 18:39, Yue Haibing wrote:
> From: YueHaibing
>
> When building CONFIG_ACPI is not set
> gcc warn this:
>
> drivers/gpio/gpio-merrifield.c: In function mrfld_gpio_get_pinctrl_dev_name:
> drivers/gpio/gpio-merrifield.c:388:19: error: dereferencing pointer to
On Mon, Apr 01, 2019 at 09:41:07AM -0400, Steven Rostedt wrote:
> From: "Dmitry V. Levin"
>
> RISC-V syscall arguments are located in orig_a0,a1..a5 fields
> of struct pt_regs.
>
> Due to an off-by-one bug and a bug in pointer arithmetic
> syscall_get_arguments() was reading s3..s7 fields
On Mon, Apr 01, 2019 at 09:41:08AM -0400, Steven Rostedt wrote:
> From: "Dmitry V. Levin"
>
> C-SKY syscall arguments are located in orig_a0,a1,a2,a3,regs[0],regs[1]
> fields of struct pt_regs.
>
> Due to an off-by-one bug and a bug in pointer arithmetic
> syscall_get_arguments() was reading
From: Sebastian Andrzej Siewior
> Sent: 03 April 2019 17:41
...
> To access the FPU registers in kernel we need:
> - disable preemption to avoid that the scheduler switches tasks. By
> doing so it would set TIF_NEED_FPU_LOAD and the FPU registers would be
> not valid.
> - disable BH because
The patch
ASoC: cs42l51: add adc volume control
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
On Thu, Apr 04, 2019 at 09:06:04PM +0800, Chris Chiu wrote:
> On Wed, Apr 3, 2019 at 9:06 PM Andy Shevchenko
> wrote:
> > On Wed, Apr 03, 2019 at 03:06:43PM +0800, Chris Chiu wrote:
> > > On Tue, Apr 2, 2019 at 7:58 PM Andy Shevchenko
> > > wrote:
> > This better to make as a separate helper
The patch
ASoC: cs42l51: add regulator management
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: dt-bindings: update cs42l51 bindings
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: cs42l51: add reset management
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
ASoC: max98357a: add missing supported rates
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: cs42l51: add power management
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
ASoC: cs42l51: add support of master mode
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
On 4/4/19 8:31 AM, Miroslav Benes wrote:
On Fri, 22 Mar 2019, Joe Lawrence wrote:
On Fri, Mar 01, 2019 at 11:13:10AM -0300, Joao Moreira wrote:
From: Josh Poimboeuf
Create cmd_klp_convert and hook it into scripts/Makefile.modpost.
cmd_klp_convert invokes klp-convert with the right
Allwinner H6 has a watchog compatible with A31.
Declare it in the device tree.
Signed-off-by: Clément Péron
---
arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi
H6 WDT is compatible with A31, so add this in the device-tree bindings.
Signed-off-by: Clément Péron
---
Documentation/devicetree/bindings/watchdog/sunxi-wdt.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/watchdog/sunxi-wdt.txt
On Wed, 3 Apr 2019 17:32:49 -0700
Matthew Garrett wrote:
> +static void tracefs_destroy_inode(struct inode *inode)
> +{
> + if S_ISREG(inode->i_mode)
Can we please put parenthesis around the condition. I know that the
macro has them, but no other place in the kernel plays such a trick.
Hello Mark,
There are no routes in cs42l51_routes table using "Mic Bias" widget.
I use this widget in a route defined in audio graph card DT node.
I checked other DTs which are using CS42L51 codec (armada-370-db.dts
kirkwood-openrd-client.dts, kirkwood-openrd-ultimate.dts),but I did not
find
On Thu, Apr 4, 2019 at 7:05 PM Maxime Ripard wrote:
>
> On Thu, Apr 04, 2019 at 11:59:44AM +0100, Srinivas Kandagatla wrote:
> >
> >
> > On 02/04/2019 16:45, Yangtao Li wrote:
> > > Because there was an endianness issue. It seems that reg_read
> > > function which the nvmem the driver currently
On Thu, Apr 04, 2019 at 09:25:47AM -0400, Vince Weaver wrote:
>
> It looks like there are at least two bugs here, one that's a full
> hardlockup with nothing on serial console. The other is the NULL
> dereference.
>
Seems so. I've spent plenty of time yesterday trying to figure out how
we
Hi Zdenek
I add in CC linux-integr...@vger.kernel.org.
Please have a look at:
https://lore.kernel.org/linux-integrity/20190329094212.gc21...@linux.intel.com/T/#t
The patch suggested in the discussion should help.
Regards
Roberto
On 4/4/2019 3:04 PM, Zdenek Kabelac wrote:
Hello
Recently
On Mon 2019-03-25 09:24:00, Dan Murphy wrote:
> Create a TI LMU common framework for TI LMU devices that share
> common features.
>
> Currently the runtime ramp and brightness setting have
> been identified as common features with common register settings.
>
> This work is derived from Milo Kims
On Wed 2019-04-03 11:01:06, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> This adds basic support for LEDs for the max77650 PMIC. The device has
> three current sinks for driving LEDs.
>
> Signed-off-by: Bartosz Golaszewski
> Acked-by: Jacek Anaszewski
Acked-by: Pavel Machek
On Wed 2019-04-03 11:01:00, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add the DT binding document for the LEDs module of max77650.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Rob Herring
Acked-by: Pavel Machek
On Thu 2019-03-28 16:12:28, Steven Rostedt wrote:
> On Thu, 28 Mar 2019 12:45:18 -0700
> Doug Anderson wrote:
>
> > > I see solution is simple, but now we have a loop with GFP_ATOMIC
> > > allocations inside. How many "tracing spus" is this expected to loop
> > > over? Will not it exhaust
Hi!
I have not yet gone through the series in great detail.
This will change the userland ABI, right? Now, I understand that old ABI is
bad, but
will it break someone's code?
Pavel
> > > > > +- function: LED functon. Use one of the LED_FUNCTION_* prefixed
> > > > > definitions
> > > > > + from the header include/dt-bindings/leds/common.h.
> > > > > + If there is no matching LED_FUNCTION available, add a new
> > > > > one.
> > > > > +- color : Color of the
On Mon, 01 Apr 2019 09:41:04 -0400
Steven Rostedt wrote:
> [ Looking for acks ]
>
I got a couple.
> Two and a half years ago I sent out 3 patches and a title letter that
> had this[1]:
Linus,
Is this something that can go into this -rc release or would you want
me to wait till the next
On Tue, Apr 02, 2019 at 04:43:03PM -0700, Alexander Duyck wrote:
> Yes, but hopefully it should be a small enough amount that nobody will
> notice. In many cases devices such as NICs can consume much more than
> this regularly for just their Rx buffers and it is not an issue. There
> has to be a
On 2019/4/4 20:02, Hans de Goede wrote:
> Hi,
>
> On 04-04-19 12:42, Yue Haibing wrote:
>> From: YueHaibing
>>
>> When building CONFIG_ACPI is not set
>> gcc warn this:
>>
>> drivers/extcon/extcon-axp288.c: In function 'axp288_extcon_probe':
>> drivers/extcon/extcon-axp288.c:363:20: error:
On Wed, 3 Apr 2019, Cyrill Gorcunov wrote:
> On Wed, Apr 03, 2019 at 10:19:44PM +0300, Cyrill Gorcunov wrote:
> >
> > You know, seems I got what happened -- p4_general_events do
> > not cover all general events, they stop at PERF_COUNT_HW_BUS_CYCLES,
> > while more 3 general event left. This is
On Thu, Apr 04, 2019 at 03:18:00PM +0200, David Hildenbrand wrote:
> > diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> > index f206b8b66af1..d8a3e9554aec 100644
> > --- a/mm/memory_hotplug.c
> > +++ b/mm/memory_hotplug.c
> > @@ -1451,15 +1451,11 @@ static int
> >
On 4/3/19 12:01 PM, Lee Jones wrote:
> On Wed, 27 Feb 2019, Amelie Delaunay wrote:
>
>> STMicroelectronics Multi-Function eXpander (STMFX) is a slave controller
>> using I2C for communication with the main MCU. Main features are:
>> - 16 fast GPIOs individually configurable in input/output
>> - 8
On 4/4/19 3:03 PM, Peter Zijlstra wrote:
> On Thu, Apr 04, 2019 at 01:09:09PM +0200, Peter Zijlstra wrote:
>
>> That is not entirely the scenario I talked about, but *groan*.
>>
>> So what I meant was:
>>
>> CPU-0 CPU-n
>>
>>
On 4/4/19 7:49 AM, Miroslav Benes wrote:
BTW, something I *just* noticed when putting together that toy out-of-tree
module to test out multi-object livepatch modules is that we aren't
considering out-of-tree symbols in Symbols.list.
Perhaps we can save that for v4 or beyond, but maybe we
On 04.04.19 14:59, Oscar Salvador wrote:
> From: Michal Hocko
>
> check_pages_isolated_cb currently accounts the whole pfn range as being
> offlined if test_pages_isolated suceeds on the range. This is based on
> the assumption that all pages in the range are freed which is currently
> the case
From: Sandeep Singh
Some of the AMD reference boards used single GPIO line for
multiple devices. So added IRQF_SHARED flag in amd pinctrl driver.
Signed-off-by: Sandeep Singh
Signed-off-by: Shyam Sundar S K
cc: Nehal Shah
---
drivers/pinctrl/pinctrl-amd.c | 4 ++--
1 file changed, 2
On 04/03/2019 11:38 PM, Dan Williams wrote:
> On Tue, Apr 2, 2019 at 9:30 PM Anshuman Khandual
> wrote:
>>
>> This series enables memory hot remove on arm64, fixes a memblock removal
>> ordering problem in generic __remove_memory(), enables sysfs memory probe
>> interface on arm64. It also
Fix checkpatch error "ERROR: code indent should use tabs where possible"
in hal_com_phycfg.c:1726.
Signed-off-by: Beatriz Martins de Carvalho
---
Changes in v2:
- correction commit title
- added more information about the error
---
drivers/staging/rtl8723bs/hal/hal_com_phycfg.c
On Wed, Apr 3, 2019 at 9:06 PM Andy Shevchenko
wrote:
>
> On Wed, Apr 03, 2019 at 03:06:43PM +0800, Chris Chiu wrote:
> > On Tue, Apr 2, 2019 at 7:58 PM Andy Shevchenko
> > wrote:
>
> > > Instead you may need to loop over each pin in the part of the group
> > > related to
> > > one 32-bit
Hello
Recently after trying kernels above 5.1.0-0.rc0.git4.2.fc31.x86_64 on my
Fedora Rawhide - I cannot suspend Lenovo T61 laptop (2.2 C2D CPU, 4G RAM)
I can only guess it can be related to this TPM reported error:
PM: suspend exit
PM: suspend entry (s2idle)
PM: Syncing filesystems
>
> > Marc wrote:
> >
> >> scsi 0:0:0:49488: scsi_add_lun: correcting incorrect peripheral device type
> 0x0 for W-LUN 0xc150hN
> >
> > ^ Where do these crazy LUN numbers come from? That
> > looks like something which needs fixing...
>
>
On 04/04/2019 05:28 PM, Oscar Salvador wrote:
> On Thu, Apr 04, 2019 at 11:09:22AM +0530, Anshuman Khandual wrote:
>>> Do these need to be __meminit? AFAICS it's effectively redundant with the
>>> containing #ifdef, and removal feels like it's inherently a later-than-init
>>> thing anyway.
>>
On Thu, Apr 04, 2019 at 01:09:09PM +0200, Peter Zijlstra wrote:
> That is not entirely the scenario I talked about, but *groan*.
>
> So what I meant was:
>
> CPU-0 CPU-n
>
> __schedule()
> local_irq_disable()
>
>
Hi,
these patches were posted as part of patchset [1], but it was agreed that
patch#3 must be further discussed.
Whole discussion can be seen in the cover letter.
But the first two patches make sense by themselves, as the first one is a nice
code cleanup, and the second one sets up the interface
From: Michal Hocko
check_pages_isolated_cb currently accounts the whole pfn range as being
offlined if test_pages_isolated suceeds on the range. This is based on
the assumption that all pages in the range are freed which is currently
the case in most cases but it won't be with later changes, as
From: Michal Hocko
arch_add_memory, __add_pages take a want_memblock which controls whether
the newly added memory should get the sysfs memblock user API (e.g.
ZONE_DEVICE users do not want/need this interface). Some callers even
want to control where do we allocate the memmap from by
On Thu, Apr 4, 2019 at 2:46 PM Antti Keränen wrote:
>
> Do not use uninitialized variable 'port' when printing an error message
>
> Signed-off-by: Antti Keränen
> ---
> drivers/staging/mt7621-pci-phy/pci-mt7621-phy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Do not use uninitialized variable 'port' when printing an error message
Signed-off-by: Antti Keränen
---
drivers/staging/mt7621-pci-phy/pci-mt7621-phy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/mt7621-pci-phy/pci-mt7621-phy.c
Userspace can make host function calls, called hgcm-calls through the
/dev/vboxguest device.
In this case we should not accept all hgcm-function-parameter-types, some
are only valid for in kernel calls.
This commit adds proper hgcm-function-parameter-type validation to the
ioctl for doing a
On Tue, Mar 26, 2019 at 03:17:53PM +, Shameer Kolothum wrote:
> HiSilicon erratum 162001800 describes the limitation of
> SMMUv3 PMCG implementation on HiSilicon Hip08 platforms.
>
> On these platforms, the PMCG event counter registers
> (SMMU_PMCG_EVCNTRn) are read only and as a result it
>
> On Apr 4, 2019, at 1:23 AM, Huang Shijie wrote:
>
>
> + * This function is different from the get_user_pages_unlocked():
> + * The @pages may has different page order with the result
> + * got by get_user_pages_unlocked().
> + *
I suggest a slight rewrite of the comment,
+robh
On 04/04/2019 11:08, Rocky Liao wrote:
> This patchs patch adds an optional device property nvm-postfix to allow the
> driver to load customized nvm file based on this property
While text /before/ is indeed called a "prefix", text /after/ is not a
"postfix",
but a "suffix".
>
Commit ad275b8bb1e6 ("KVM: arm/arm64: vgic-new: vgic_init: implement
vgic_init") had set irq->targets in kvm_vgic_vcpu_init(), regardless of
the GIC architecture (v2 or v3). When the number of vcpu reaches 32
(in v3), UBSAN will complain about it.
On Thu, Apr 4, 2019 at 9:59 AM Colin King wrote:
>
> From: Colin Ian King
>
> There is a spelling mistake in a dev_err message, fix it.
>
> Signed-off-by: Colin Ian King
> ---
Applied to for-5.2/ish
Cheers,
Benjamin
> drivers/hid/intel-ish-hid/ishtp-fw-loader.c | 2 +-
> 1 file changed, 1
On Thu, Apr 04, 2019 at 10:44:59AM +0100, Lee Jones wrote:
> On Thu, 04 Apr 2019, Andy Shevchenko wrote:
> > On Thu, Apr 04, 2019 at 10:03:14AM +0100, Lee Jones wrote:
> > > On Thu, 04 Apr 2019, Andy Shevchenko wrote:
> > > > On Thu, Apr 04, 2019 at 08:03:57AM +0100, Lee Jones wrote:
> > > > > On
Beelink GS1 is an Allwinner H6 based TV box,
which support:
- Allwinner H6 Quad-core 64-bit ARM Cortex-A53
- GPU Mali-T720
- 2GB LPDDR3 RAM
- AXP805 PMIC
- 1Gbps GMAC via RTL8211E
- FN-Link 6222B-SRB Wifi/BT
- 1x USB 2.0 Host and 1x USB 3.0 Host
- HDMI port
- S/PDIF Tx
- IR receiver
- 5V/2A DC
Shenzhen AZW Technology Co. Ltd. is a manufacturer specialized in Android
smart TV boxes, Intel mini PCs and home cloud TV boxes with NAS.
Add the vendor prefix for AZW.
Signed-off-by: Clément Péron
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
On Thu, Apr 04, 2019 at 11:14:38AM +0200, Jiri Olsa wrote:
SNIP
> Program received signal SIGABRT, Aborted.
> 0x775e60f5 in raise () from /lib64/libc.so.6
> Missing separate debuginfos, use: dnf debuginfo-install
> bzip2-libs-1.0.6-29.fc30.x86_64 elfutils-libelf-0.176-1.fc30.x86_64
>
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
---
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
---
drivers/pci/controller/dwc/pcie-designware-host.c | 7
401 - 500 of 1406 matches
Mail list logo
