Add a device tree bindings for the board management controller found on
the Kontron SMARC-sAL28 board.
Signed-off-by: Michael Walle
Reviewed-by: Rob Herring
---
Changes since v8:
- none
Changes since v7:
- none
Changes since v6:
- renamed "sl28cpld-r1" to "sl28cpld"
- made paths relative
On Sat, 29 Aug 2020 14:00:16 +0100, Valentin Schneider wrote:
> In the absence of ACPI or DT topology data, we fallback to haphazardly
> decoding *something* out of MPIDR. Sadly, the contents of that register are
> mostly unusable due to the implementation leniancy and things like Aff0
> having to
On Mon, 7 Sep 2020 22:15:16 +0800 Luo bin wrote:
> When calling hinic_close in hinic_set_channels, all queues are
> stopped after netif_tx_disable, but some queue may be rewaken in
> free_tx_poll by mistake while drv is handling tx irq. If one queue
> is rewaken core may call hinic_xmit_frame to
On Wed, Sep 02, 2020 at 03:59:04PM -0700, Nick Desaulniers wrote:
> Adds a compile time #error to compiler-clang.h setting the effective
> minimum supported version to clang 10.0.1. A separate patch has already
> been picked up into the Documentation/ tree also confirming the version.
Modulo my
On Wed, Sep 02, 2020 at 03:59:11PM -0700, Nick Desaulniers wrote:
> As Kees suggests, doing so provides developers with two useful pieces of
> information:
I struggle to parse this. "doing so" what? These things are supposed to
be in the imperative.
Will
Hello,
syzbot found the following issue on:
HEAD commit:7a695657 Add linux-next specific files for 20200903
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=152eff5d90
kernel config: https://syzkaller.appspot.com/x/.config?x=39134fcec6c78e33
dashboard
Hello,
syzbot found the following issue on:
HEAD commit:a8205e31 Merge tag 'io_uring-5.9-2020-09-06' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16f5880d90
kernel config: https://syzkaller.appspot.com/x/.config?x=9b0e48dac62b2233
Hello,
syzbot found the following issue on:
HEAD commit:f4d51dff Linux 5.9-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=126a23e190
kernel config: https://syzkaller.appspot.com/x/.config?x=7954285d6e960c0f
dashboard link:
Hello,
syzbot found the following issue on:
HEAD commit:9322c47b Merge tag 'xfs-5.9-fixes-2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1670fe5990
kernel config: https://syzkaller.appspot.com/x/.config?x=bd46548257448703
Hello,
syzbot found the following issue on:
HEAD commit:9322c47b Merge tag 'xfs-5.9-fixes-2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16cf729e90
kernel config: https://syzkaller.appspot.com/x/.config?x=e1c560d0f4e121c9
Per the datasheet the i2c functions use MPP_Sel=0x1. They are documented
as using MPP_Sel=0x4 as well but mixing 0x1 and 0x4 is clearly wrong. On
the board tested 0x4 resulted in a non-functioning i2c bus so stick with
0x1 which works.
Fixes: d7ae8f8dee7f ("pinctrl: mvebu: pinctrl driver for
I noticed these while adding support for i2c recovery for a couple of our
boards. They date back to when I initially added support for the 98dx3236. They
probably haven't been causing a problem because the HW defaults are correct and
unless you attempt to use the specific pinctrl functions there
The switches with integrated CPUs have only got a single i2c controller.
They incorrectly gained one when they were split from the Armada-XP.
Fixes: 43e28ba87708 ("ARM: dts: Use armada-370-xp as a base for
armada-xp-98dx3236")
Signed-off-by: Chris Packham
Reviewed-by: Andrew Lunn
---
Changes
On Fri, 4 Sep 2020 14:00:59 +0530, Anshuman Khandual wrote:
> Kernel virtual region [BPF_JIT_REGION_START..BPF_JIT_REGION_END] is missing
> from address_markers[], hence relevant page table entries are not displayed
> with /sys/kernel/debug/kernel_page_tables. This adds those missing markers.
>
Add pinctrl information for the 98dx3236 (and variants). There is only
one choice for i2c0 MPP14 and MPP15.
Signed-off-by: Chris Packham
Reviewed-by: Andrew Lunn
---
Changes in v2:
- Add reviewed-by from Andrew
arch/arm/boot/dts/armada-xp-98dx3236.dtsi | 7 +++
1 file changed, 7
On Mon, Sep 7, 2020 at 2:06 AM Willem de Bruijn
wrote:
>
> The CAP_SYS_RAWIO exception indeed was requested to be able to
> purposely test devices against bad inputs. The gmane link
> unfortunately no longer works, but this was the discussion thread:
>
On 8/09/20 9:07 am, Andrew Lunn wrote:
> On Mon, Sep 07, 2020 at 09:04:48PM +, Chris Packham wrote:
>> On 8/09/20 3:45 am, Andrew Lunn wrote:
>>> On Mon, Sep 07, 2020 at 02:41:48PM +1200, Chris Packham wrote:
The switches with integrated CPUs have only got a single i2c controller.
On Mon, 7 Sep 2020 12:31:40 -0400 Sasha Levin wrote:
> [ Upstream commit 9f13457377907fa253aef560e1a37e1ca4197f9b ]
> @@ -2024,10 +2033,14 @@ static int do_reset(struct ibmvnic_adapter *adapter,
> } else {
> rc = reset_tx_pools(adapter);
>
On Mon, Sep 07, 2020 at 09:04:48PM +, Chris Packham wrote:
>
> On 8/09/20 3:45 am, Andrew Lunn wrote:
> > On Mon, Sep 07, 2020 at 02:41:48PM +1200, Chris Packham wrote:
> >> The switches with integrated CPUs have only got a single i2c controller.
> >> The incorrectly gained one when they were
On 8/09/20 3:45 am, Andrew Lunn wrote:
> On Mon, Sep 07, 2020 at 02:41:48PM +1200, Chris Packham wrote:
>> The switches with integrated CPUs have only got a single i2c controller.
>> The incorrectly gained one when they were split from the Armada-XP.
Someone pointed out a small grammo instead of
Hi Linus,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f4d51dffc6c01a9e94650d95ce0104964f8ae822
commit: 11f74023888f4e50fd33d3428ce473a10e1f1969 mtd: parsers: Move BCM47xx
parser
date: 12 months ago
config:
On Mon, Sep 07, 2020 at 03:15:37PM +0200, Joerg Roedel wrote:
> @@ -347,7 +348,13 @@ bool sme_active(void)
>
> bool sev_active(void)
> {
> - return sme_me_mask && sev_enabled;
> + return !!(sev_status & MSR_AMD64_SEV_ENABLED);
Dropped those "!!" here too while applying.
--
On Mon, Sep 07, 2020 at 09:14:03PM +0200, Karol Herbst wrote:
> > - changes in the nouveau driver. Mika told me the PCIe regression
> > "pcieport :00:01.0: PME: Spurious native interrupt!" is supposed
> > to be fixed in 5.8, but I still get a 4mn hang or so during boot and
> > with 5.8,
On Mon, 7 Sep 2020 22:12:07 +0800 Wang Hai wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/ethernet/dnet.c: In function dnet_start_xmit
> drivers/net/ethernet/dnet.c:511:15: warning: variable ‘len’ set but not used
> [-Wunused-but-set-variable]
>
> commit 4796417417a6
On Mon, 2020-09-07 at 20:44 +0530, Ayush wrote:
> Commits which mentioned/referenced "revert commits" in their description will
> get error even if they follow the proper syntax.
I think all your examples are broken.
I think all should start with revert
i.e.: Reverts commit ("description...")
This kills using the do_each_thread/while_each_thread combo to
iterate all threads and uses for_each_process_thread() instead,
maintaining semantics. while_each_thread() is ultimately racy
and deprecated; although in this particular case there is no
concurrency so it doesn't matter. Still lets
On 9/7/2020 6:22 PM, Keita Suzuki wrote:
When wlc_phy_txpwr_srom_read_lcnphy fails in wlc_phy_attach_lcnphy,
the allocated pi->u.pi_lcnphy is leaked, since struct brcms_phy will be
freed in the caller function.
Fix this by calling wlc_phy_detach_lcnphy in the error handler of
On 9/7/20 12:18 PM, Guenter Roeck wrote:
> On 9/7/20 8:46 AM, Jan Kiszka wrote:
>> On 07.09.20 17:31, Guenter Roeck wrote:
>>> On 9/7/20 4:20 AM, Jan Kiszka wrote:
Hi all,
Arsalan reported that the upstream driver for sp5100_tco does not work
for embedded Ryzen. Meanwhile, I
Hi,
The aim of this series is to add support for reporting push
events from rotary encoders with integrated push button
functionality (which are quite common).
I added a few more additional cleanup patches, since I worked
on the driver anyways.
Changes since PATCHv1 [0]:
* Added patch
The DT binding specifies 24 being used by default, but driver
initializes to 0. The steps variable will be used for a modulo
operation at a later step, so do not allow 0 (does not make
sense in any case).
Signed-off-by: Sebastian Reichel
---
drivers/input/misc/rotary_encoder.c | 5 +
1 file
Convert rotary-encoder bindings to YAML schema.
Signed-off-by: Sebastian Reichel
---
.../bindings/input/rotary-encoder.txt | 50 -
.../bindings/input/rotary-encoder.yaml| 100 ++
2 files changed, 100 insertions(+), 50 deletions(-)
delete mode 100644
From: Mylène Josserand
Add the support of a gpio that can be defined as a push button.
Thanks to that, it is possible to emit a keycode in case of a
"push" event, if the rotary supports that.
The keycode to emit is defined using "linux,code" property
(such as in gpio-keys).
Signed-off-by:
Simplify driver a bit by making use of dev_err_probe.
Signed-off-by: Sebastian Reichel
---
drivers/input/misc/rotary_encoder.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/input/misc/rotary_encoder.c
b/drivers/input/misc/rotary_encoder.c
index
From: Alex Williamson
commit 11c4cd07ba111a09f49625f9e4c851d83daf0a22 upstream.
Rather than calling remap_pfn_range() when a region is mmap'd, setup
a vm_ops handler to support dynamic faulting of the range on access.
This allows us to manage a list of vmas actively mapping the area that
we can
On Mon, 7 Sep 2020 13:14:05 + Radhey Shyam Pandey wrote:
> > From: Zhang Changzhong
> > Sent: Monday, September 7, 2020 6:32 PM
> > To: Radhey Shyam Pandey ; da...@davemloft.net;
> > k...@kernel.org; Michal Simek
> > Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject:
From: Alex Williamson
commit abafbc551fddede3e0a08dee1dcde08fc0eb8476 upstream.
Accessing the disabled memory space of a PCI device would typically
result in a master abort response on conventional PCI, or an
unsupported request on PCI express. The user would generally see
these as a -1
From: Alex Williamson
commit 41311242221e3482b20bfed10fa4d9db98d87016 upstream.
With conversion to follow_pfn(), DMA mapping a PFNMAP range depends on
the range being faulted into the vma. Add support to manually provide
that, in the same way as done on KVM with hva_to_pfn_remapped().
CVE-2020-12888 Kernel: vfio: access to disabled MMIO space of some
devices may lead to DoS scenario
The VFIO modules allow users (guest VMs) to enable or disable access to the
devices' MMIO memory address spaces. If a user attempts to access (read/write)
the devices' MMIO address space when
On Mon, 7 Sep 2020 13:14:50 + Andy Duan wrote:
> From: Zhang Changzhong Sent: Monday, September
> 7, 2020 8:50 PM
> > Because clk_prepare_enable() and clk_disable_unprepare() already checked
> > NULL clock parameter, so the additional checks are unnecessary, just remove
> > them.
> >
> >
On Mon, 7 Sep 2020 20:57:24 +0800 Zhang Changzhong wrote:
> Because clk_prepare_enable() and clk_disable_unprepare() already checked
> NULL clock parameter, so the additional checks are unnecessary, just
> remove them.
>
> Reported-by: Hulk Robot
> Signed-off-by: Zhang Changzhong
Applied.
On Mon, 7 Sep 2020 20:46:54 +0800 Zhang Changzhong wrote:
> Because clk_prepare_enable() and clk_disable_unprepare() already checked
> NULL clock parameter, so the additional checks are unnecessary, just
> remove them.
>
> Reported-by: Hulk Robot
> Signed-off-by: Zhang Changzhong
Applied.
On Mon, Aug 31, 2020 at 9:04 PM John Stultz wrote:
> On Wed, Aug 12, 2020 at 3:23 AM Rajendra Nayak wrote:
> > This OPP table was based on the clock VDD-FMAX tables seen in
> > downstream code, however it turns out the downstream clock
> > driver does update these tables based on
On Mon, Sep 07, 2020 at 01:16:43PM -0700, Andy Lutomirski wrote:
> > + asm volatile("rdmsr" : EAX_EDX_RET(val, low, high) : "c" (msr));
>
> I don't like this. Plain rdmsrl() will at least print a nice error if it
> fails.
I think you read my commit message too quickly :)
The point is to
All dra7/am57 boards converted to use new driver, so drop legacy
cpsw dt node.
Signed-off-by: Grygorii Strashko
---
arch/arm/boot/dts/dra7-l4.dtsi | 54 --
arch/arm/boot/dts/dra7.dtsi| 4 +--
2 files changed, 2 insertions(+), 56 deletions(-)
diff --git
Switch all TI AM5728 BeagleBoard-X15 boards to use new cpsw switch driver.
Those boards have 2 Ext. port wired and configured in dual_mac mode by
default. Hence, dual_mac mode has been preserved the same way between
legacy and new driver it's safe to switch drivers.
Signed-off-by: Grygorii
Switch CompuLab CL-SOM-AM57x board to use new cpsw switch driver. Those
board configured in dual_mac mode by default. Hence, dual_mac mode has been
preserved the same way between legacy and new driver it's safe to switch
drivers.
Signed-off-by: Grygorii Strashko
---
Switch all am571/2/4-idk boards to use new cpsw switch driver.
Those boards have 2 Ext. port wired and configured in dual_mac mode by
default. Hence, dual_mac mode has been preserved the same way between
legacy and new driver it's safe to switch drivers.
Signed-off-by: Grygorii Strashko
---
Switch all TI DRA7x boards to use new cpsw switch driver. Those boards
configured in dual_mac mode by default. Hence, dual_mac mode has been
preserved the same way between legacy and new driver it's safe to switch
drivers.
Signed-off-by: Grygorii Strashko
---
arch/arm/boot/dts/dra7-evm.dts
From: Alex Williamson
commit abafbc551fddede3e0a08dee1dcde08fc0eb8476 upstream.
Accessing the disabled memory space of a PCI device would typically
result in a master abort response on conventional PCI, or an
unsupported request on PCI express. The user would generally see
these as a -1
From: Alex Williamson
commit 41311242221e3482b20bfed10fa4d9db98d87016 upstream.
With conversion to follow_pfn(), DMA mapping a PFNMAP range depends on
the range being faulted into the vma. Add support to manually provide
that, in the same way as done on KVM with hva_to_pfn_remapped().
CVE-2020-12888 Kernel: vfio: access to disabled MMIO space of some
devices may lead to DoS scenario
The VFIO modules allow users (guest VMs) to enable or disable access to the
devices' MMIO memory address spaces. If a user attempts to access (read/write)
the devices' MMIO address space when
Switch BeagleBone AI to use new cpsw switch driver.
It has one Ext. port only and fits dual_mac mode with no issues.
Signed-off-by: Grygorii Strashko
---
arch/arm/boot/dts/am5729-beagleboneai.dts | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git
Hi Tony,
Since Kernel v5.5 commits:
111cf1ab4da3 ("net: ethernet: ti: introduce cpsw switchdev based driver part 2
- switch")
ed3525eda4c4 ("net: ethernet: ti: introduce cpsw switchdev based driver part 1
- dual-emac")
the new CPSW driver with switchdev support has been introduced and one
From: Alex Williamson
commit 11c4cd07ba111a09f49625f9e4c851d83daf0a22 upstream.
Rather than calling remap_pfn_range() when a region is mmap'd, setup
a vm_ops handler to support dynamic faulting of the range on access.
This allows us to manage a list of vmas actively mapping the area that
we can
On Mon, Sep 7, 2020 at 7:25 AM Christian Brauner
wrote:
>
> On Mon, Sep 07, 2020 at 07:15:52AM -0700, Andy Lutomirski wrote:
> >
> >
> > > On Sep 7, 2020, at 3:15 AM, Christian Brauner
> > > wrote:
> > >
> > > On Fri, Sep 04, 2020 at 04:31:44PM -0400, Gabriel Krisman Bertazi wrote:
> > >>
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script below and has been
hand modified to replace GFP_ with a correct flag.
It has been compile tested.
When memory is allocated in 'mpi_map_card()' GFP_KERNEL can be used because
On Mon, 07 Sep 2020, Daniel Thompson wrote:
No objections to the change but kdb doesn't use tsk->thread_group,
it uses do_each_thread/while_each_thread. Can we change this to
say that is osbsolete and racy to use while_each_thread() (that's
pretty much what the description of the patch that
On Mon, 7 Sep 2020 at 08:00, Christoph Hellwig wrote:
>
> On Thu, Sep 03, 2020 at 09:18:37PM +0100, Tom Murphy wrote:
> > Disable combining sg segments in the dma-iommu api.
> > Combining the sg segments exposes a bug in the intel i915 driver which
> > causes visual artifacts and the screen to
On Sun, Sep 6, 2020 at 2:21 PM Borislav Petkov wrote:
>
> Hi,
>
> Ingo and I talked about this thing this morning and tglx has had it on
> his to-fix list too so here's a first attempt at it.
>
> Below is just a brain dump of what we talked about so let's start with
> it and see where it would
Hi,
Some style comments below.
On Mon, Sep 07, 2020 at 08:00:58PM +0200, Gerald Schaefer wrote:
> From: Alexander Gordeev
>
> Since pXd_addr_end() macros take pXd page-table entry as a
> parameter it makes sense to check the entry type on compile.
> Even though most archs do not make use of
On Mon, Aug 31, 2020 at 12:08:10PM -0600, Jens Axboe wrote:
> We have a set of flags that are shared between the two and inherired
> in kiocb_set_rw_flags(), but we check and set these individually.
> Reorder the IOCB flags so that the bottom part of the space is synced
> with the RWF flag space,
On Mon, Sep 07, 2020 at 08:00:55PM +0200, Gerald Schaefer wrote:
> This is v2 of an RFC previously discussed here:
> https://lore.kernel.org/lkml/20200828140314.8556-1-gerald.schae...@linux.ibm.com/
>
> Patch 1 is a fix for a regression in gup_fast on s390, after our conversion
> to common
On Mon, 7 Sep 2020 11:50:10 +0800 Po-Hsu Lin wrote:
> The kci_test_encap_fou() test from kci_test_encap() in rtnetlink.sh
> needs the fou module to work. Otherwise it will fail with:
>
> $ ip netns exec "$testns" ip fou add port ipproto 47
> RTNETLINK answers: No such file or directory
On Sun, Sep 06, 2020 at 11:21:30PM +0200, Borislav Petkov wrote:
> Hi,
>
> Ingo and I talked about this thing this morning and tglx has had it on
> his to-fix list too so here's a first attempt at it.
>
> Below is just a brain dump of what we talked about so let's start with
> it and see where
On Sun, Sep 06, 2020 at 09:29:30PM +0200, Paul Cercueil wrote:
> 128 IRQs is not enough to support Ingenic SoCs.
>
> Signed-off-by: Paul Cercueil
> ---
>
> Notes:
> v2-v3: No change
>
> arch/mips/include/asm/mach-generic/irq.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
Use the sysfs_emit API.
Signed-off-by: Joe Perches
---
drivers/base/devcoredump.c | 2 +-
drivers/base/firmware_loader/fallback.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/base/devcoredump.c b/drivers/base/devcoredump.c
index
Hi Neil.
On Mon, Sep 07, 2020 at 01:10:27PM +0200, Neil Armstrong wrote:
> This adds support for the TDO TL070WSH30 TFT-LCD panel module.
> The panel has a 1024×600 resolution and uses 24 bit RGB per pixel.
> It provides a MIPI DSI interface to the host, a built-in LED backlight
> and touch
On 8/31/20 12:08 PM, Jens Axboe wrote:
> We have a set of flags that are shared between the two and inherired
> in kiocb_set_rw_flags(), but we check and set these individually.
> Reorder the IOCB flags so that the bottom part of the space is synced
> with the RWF flag space, and then we can do
On 9/7/20 8:06 AM, Wang Hai wrote:
> The sparse tool complains as follows:
>
> kernel/trace/blktrace.c:796:5: warning:
> symbol 'blk_trace_bio_get_cgid' was not declared. Should it be static?
>
> This function is not used outside of blktrace.c, so this commit
> marks it static.
Applied,
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script below and has been
hand modified to replace GFP_ with a correct flag.
It has been compile tested.
The only file where some GFP_ flags are updated is 'pci.c'.
When memory is
Hi Neil.
On Mon, Sep 07, 2020 at 03:24:47PM +0200, Neil Armstrong wrote:
> Hi,
>
> On 07/09/2020 13:45, Sam Ravnborg wrote:
> > Hi Neil.
> >
> > On Mon, Sep 07, 2020 at 01:10:26PM +0200, Neil Armstrong wrote:
> >> This add the bindings for the 1024*600 tl070wsh30 DSI panel.
> >
> > The binding
On 9/7/20 8:46 AM, Jan Kiszka wrote:
> On 07.09.20 17:31, Guenter Roeck wrote:
>> On 9/7/20 4:20 AM, Jan Kiszka wrote:
>>> Hi all,
>>>
>>> Arsalan reported that the upstream driver for sp5100_tco does not work
>>> for embedded Ryzen. Meanwhile, I was able to confirm that on an R1505G:
>>>
>>> [
.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Fabien-Parent/dt-bindings-clock-mediatek-add-bindings-for-MT8167-clocks/20200907-210215
base: https://git.kernel.org/pub/scm/linux
On Sun, Sep 6, 2020 at 8:52 PM Marc MERLIN wrote:
>
> Ok, I have an update to this problem. I added the nouveau list because
> I can't quite tell if the issue is:
> - the PCIe changes that went in 5.6 I think (or 5.5?), referenced below
>
> - a new issue with thunderbold on thinkpad P73, that
> -Original Message-
> From: Dexuan Cui
> Sent: Friday, September 4, 2020 7:55 PM
> To: wei@kernel.org; KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger ;
> lorenzo.pieral...@arm.com; bhelg...@google.com; linux-hyp...@vger.kernel.org;
> linux-...@vger.kernel.org;
On 2020-09-01 17:46, Rob Clark wrote:
> From: Rob Clark
>
> NOTE: I have re-ordered the series, and propose that we could merge this
>series in the following order:
>
> 1) 01-11 - merge via drm / msm-next
> 2) 12-15 - merge via iommu, no dependency on msm-next pull req
>
> Re: [PATCH 3/8] asm-generic: fix unaligned access hamdling in raw_copy_{from,
> to}_user
nit: handling
--Sean
Make modifications to the GRU mappings to accommodate changes for UV5.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Steve Wahl
---
arch/x86/kernel/apic/x2apic_uv_x.c | 30 --
1 file changed, 24 insertions(+), 6 deletions(-)
---
Subject: [PATCH 00/12] x86/platform/uv: Updates for UV5
Add changes needed for new UV5 UV architecture. Chief among the changes
are 52 bits of physical memory address and 57 bits of virtual address space.
0001 Remove UV BAU TLB Shootdown Handler
- removes BAU TLB code being replaced by
There is a symbol clash from the auto-generated uv_mmrs.h file that
clashes with code in the UV kernel modules (is_uv() is the symbol).
Change those prior to the symbol clash so as to not cause a compile error.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Steve Wahl
Make modifications to the MMIOH mappings to accommodate changes for UV5.
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
---
arch/x86/kernel/apic/x2apic_uv_x.c | 213 +
1 file changed, 144 insertions(+), 69 deletions(-)
---
UV class systems no longer use System Controller for monitoring of CPU
activity provided by this driver. Other methods have been developed
for BIOS and the management controller (BMC). This patch removes that
supporting code.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
---
A patch to add and process the UV Arch Type field in the UVsystab passed
from UV BIOS to the kernel. This allows the system to be recognized
without relying on the OEM_ID which OEMs want to change.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Steve Wahl
---
when kmalloc() fails in kvm_io_bus_unregister_dev(), before removing
the bus, we should iterate over all other devices linked to it and call
kvm_iodevice_destructor() for them
Fixes: 90db10434b16 ("KVM: kvm_io_bus_unregister_dev() should never fail")
Cc: sta...@vger.kernel.org
Add new references to UV5 (and UVY class) system MMR addresses and
fields primarily caused by the expansion from 46 to 52 bits of
physical memory address.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_hub.h | 49
The changes in the UV5 arch shrunk the NODE PRESENT table to just 2x64
entries (128 total) so are in to 64 bit MMRs instead of a depth of 64
bits in an array. Adjust references when counting up the nodes present.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Steve Wahl
Update check of BIOS TSC sync status to include both possible "invalid"
states provided by newer UV5 BIOS.
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_hub.h |2 +-
arch/x86/kernel/apic/x2apic_uv_x.c | 24 ++--
2 files changed,
The Broadcast Assist Unit (BAU) TLB shootdown handler is being rewritten
to become the UV BAU APIC driver. It is designed to speed up sending
IPI's to selective CPUs within the system. Remove the current TLB
shutdown handler (tlb_uv.c) file and a couple of kernel hooks in the
interim.
Make modifications to the GAM MMR mappings to accommodate changes for UV5.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Steve Wahl
---
arch/x86/kernel/apic/x2apic_uv_x.c | 30 +-
1 file changed, 25 insertions(+), 5 deletions(-)
---
The UV NMI MMR addresses and fields moved between UV4 and UV5
necessitating a rewrite of the UV NMI handler. Adjust references
to accommodate those changes.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_hub.h | 13 ---
> As a result of this cleanup should be binary DTB file for V7 with same
> structure as DTB file without such cleanup patch, right?
Should be. If need be, you can decompile the DTB back to a DTS and
make sure it looks correct.
Andrew
On 2020-09-04 16:55, Bjorn Andersson wrote:
> Based on previous attempts and discussions this is the latest attempt at
> inheriting stream mappings set up by the bootloader, for e.g. boot splash or
> efifb.
>
> Per Will's request this builds on the work by Jordan and Rob for the Adreno
> SMMU
.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Fabien-Parent/dt-bindings-clock-mediatek-add-bindings-for-MT8167-clocks/20200907-210215
base: https://git.kernel.org/pub/scm/linux
The fixed clocks are kept under dedicated 'clocks' node but this causes
multiple dtschema warnings:
clocks: $nodename:0: 'clocks' does not match
'^([a-z][a-z0-9\\-]+-bus|bus|soc|axi|ahb|apb)(@[0-9a-f]+)?$'
clocks: #size-cells:0:0: 0 is not one of [1, 2]
clocks: oscillator@0:reg:0: [0] is
The fixed clocks are kept under dedicated 'clocks' node but this causes
multiple dtschema warnings:
clocks: $nodename:0: 'clocks' does not match
'^([a-z][a-z0-9\\-]+-bus|bus|soc|axi|ahb|apb)(@[0-9a-f]+)?$'
clocks: #size-cells:0:0: 0 is not one of [1, 2]
clocks: oscillator@0:reg:0: [0] is
Although PWM is used on S3C24xx as clocksource/timer, the dtschema
expects the node to be named in certain format:
timer@5100: $nodename:0: 'timer@5100' does not match
'^pwm(@.*|-[0-9a-f])*$'
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s3c24xx.dtsi | 2 +-
1 file
The PWM has only three cells, not four, as pointed out by dtschema:
timer@5100: #pwm-cells:0:0: 3 was expected
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s3c24xx.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/s3c24xx.dtsi
The SROM bank 5 is at address 0xa800, just like the one put in "reg"
property of ethernet node. Fix the unit address of ethernet node.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-smdkv210.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi,
This is last serie of big dtschema cleanups for Samsung DTS. It fixes
almost all dtschema violations, except:
s3c6410-mini6410.dt.yaml: srom-cs1-bus@1800: ethernet@1800:reg:0:
[402653184, 2, 402653188, 2] is too long
which is similar to the case with SMDK5410 (Exynos5410).
The
Only the specific compatible (arm,arm1176jzf-s) is allowed by dtschema:
cpu@0: compatible: ['arm,arm1176jzf-s', 'arm,arm1176'] is too long
cpu@0: compatible: Additional items are not allowed ('arm,arm1176' was
unexpected)
Signed-off-by: Krzysztof Kozlowski
---
201 - 300 of 1482 matches
Mail list logo
