Paging Hartley who I think uses this chip.
On Thu, Dec 24, 2020 at 12:22 PM Nikita Shubin
wrote:
> I was lucky enough to became an owner of some splendid piece's of
> antiques called ts7250 based on the top of Cirrus Logic EP9302.
>
> I don't know what fate expects this hardware (it's not EOL
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: 18c07d23da5a48525b2955aa269b8bb108c19300 csky: Fixup calltrace panic
date: 8 months ago
config: csky-randconfig-r004-20201227 (attached as .config)
compiler
Similar to commit<1bd54d85>,kgdbts_option_setup does not check input argument
before passing it to strlen. The argument would be a NULL pointer.
Signed-off-by: Defang Bo
---
drivers/misc/kgdbts.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/misc/kgdbts.c
Dear Linux folks,
Using an initrd created by tiny-initramfs [1], the boot stalls for two
minutes *after* the initrd has run and systemd has already started. An
F2FS root partition is used.
```
[0.00] microcode: microcode updated early to revision 0xa0b,
date = 2010-09-28
[
From: Hongtao Wu
This series adds PCIe controller driver for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Signed-off-by: Hongtao Wu
---
drivers/pci/controller/dwc/Kconfig | 12 ++
drivers/pci/controller/dwc/Makefile| 1 +
drivers/pci/controller/dwc/pcie-sprd.c | 293
From: Hongtao Wu
This series adds PCIe bindings for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Signed-off-by: Hongtao Wu
---
.../devicetree/bindings/pci/sprd-pcie.yaml | 91 ++
1 file changed, 91 insertions(+)
create mode 100644
From: Hongtao Wu
This series adds PCIe controller driver for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Changes from v1:
1) Test this patch on top of Rob Herring's 40 part series of DWC clean-ups:
https://lore.kernel.org/linux-pci/20200821035420.380495-1-r...@kernel.org/
Here is the series to enable RAVB on V3U. I took the DTS patches
from the BSP, the rest was developed on mainline tree. Note that only
RAVB0 could be tested because the other ones did not have PHYs attached.
Also, the last patch is a workaround. 'reset-gpios' cannot be obtained
currently which
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
b/drivers/clk/renesas/r8a779a0-cpg-mssr.c
index 04514140e615..5be70a6a7904 100644
---
Retrieving a GPIO currently fails, so probing the whole driver fails
then. Remove them for now to get a working AVB device for testing.
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
From: Tho Vu
Define the Falcon board dependent part of the Ethernet-AVB device nodes.
Only AVB0 was tested because it was the only port with a PHY on current
hardware.
Signed-off-by: Tho Vu
[wsa: rebased]
Signed-off-by: Wolfram Sang
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 195
From: Tho Vu
Define the generic parts of Ethernet-AVB device nodes. Only AVB0 was
tested because it was the only port with a PHY on current hardware.
Signed-off-by: Tho Vu
[wsa: double checked & rebased]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 270
Document the compatible value for the RAVB block in the Renesas R-Car
V3U (R8A779A0) SoC. This variant has no stream buffer, so we only need
to add the new compatible.
Signed-off-by: Wolfram Sang
---
Documentation/devicetree/bindings/net/renesas,etheravb.yaml | 1 +
1 file changed, 1
CC Arnd
On Sun, Dec 27, 2020 at 3:48 AM Randy Dunlap wrote:
>
> Make mandatory in include/asm-generic/Kbuild
> and remove all arch/*/include/asm/local64.h arch-specific files since
> they only #include .
>
> This fixes build errors on arch/c6x/ and arch/nios2/ for
> block/blk-iocost.c.
>
>
Hi Mauro,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: 5b552b198c2557295becd471bff53bb520fefee5 media: atomisp: re-enable
warnings again
date: 7 months ago
[Why]
Similar to commit<0fa375e6>. If amdgpu_switcheroo_can_switch access
the drm_device when dev is not bound, a null pointer dereference can happen.
[How]
Add sanity checks to prevent it.
Signed-off-by: Defang Bo
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 3 +++
1 file changed, 3
Hi Markus
> This should be caused by
> commit <9b947a13e7f6> ("")
> I suggest to omit angle brackets from such information.
> * Will another imperative wording become helpful for the commit description?
> * How do you think about to add the tag “Fixes”?
Do you mean so?
commit:
Hi Yu Kuai,
On Sat, Dec 26, 2020 at 06:28:06PM +0800, Yu Kuai wrote:
> When sharing a tag set, if most disks are issuing small amount of IO, and
> only a few is issuing a large amount of IO. Current approach is to limit
> the max amount of tags a disk can get equally to the average of total
>
On Fri, Dec 25, 2020 at 04:51:13PM +0300, Konstantin Komarov wrote:
> +static int ntfs_readdir(struct file *file, struct dir_context *ctx)
> +{
> + const struct INDEX_ROOT *root;
> + u64 vbo;
> + size_t bit;
> + loff_t eod;
> + int err = 0;
> + struct inode *dir =
Hi,
I love your patch! Yet something to improve:
[auto build test ERROR on soc/for-next]
[also build test ERROR on next-20201223]
[cannot apply to robh/for-next arm/for-next keystone/next rockchip/for-next
arm64/for-next/core shawnguo/for-next xlnx/master kvmarm/next mediatek/for-next
v5.10]
Hi YANG,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on song-md/md-next]
[also build test WARNING on v5.10 next-20201223]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as
On Sun, Dec 27, 2020 at 04:56:45PM +0530, Angshuman Sengupta wrote:
> Warning found by checkpatch.pl script.
>
> Signed-off-by: Angshuman Sengupta
> ---
> drivers/staging/android/ashmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/android/ashmem.c
Hi Linus:
This push fixes a number of autobuild failures due to missing
Kconfig dependencies.
The following changes since commit 93cebeb1c21a65b92636aaa278a32fbc0415ec67:
crypto: qat - add capability detection logic in qat_4xxx (2020-12-11 21:54:16
+1100)
are available in the Git repository
Bert,
On Sat, 26 Dec 2020 15:02:21 +,
Bert Vermeulen wrote:
>
> On 12/23/20 5:18 PM, Marc Zyngier wrote:
> >> + /* Set up interrupt routing */
> >> + writel(RTL8380_IRR0_SETTING, REG(RTL8380_IRR0));
> >> + writel(RTL8380_IRR1_SETTING, REG(RTL8380_IRR1));
> >> +
Warning found by checkpatch.pl script.
Signed-off-by: Angshuman Sengupta
---
drivers/staging/android/ashmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
index 4789d36ddfd3..2cb665e0228c 100644
---
Hi,
On Fri 11 Sep 20, 09:25, Hamish Martin wrote:
> Some integrated OHCI controller hubs do not expose all ports of the hub
> to pins on the SoC. In some cases the unconnected ports generate
> spurious over-current events. For example the Broadcom 56060/Ranger 2 SoC
> contains a nominally 3 port
On 23.12.20 02:20, Tony Krowiak wrote:
> The vfio_ap device driver registers a group notifier with VFIO when the
> file descriptor for a VFIO mediated device for a KVM guest is opened to
> receive notification that the KVM pointer is set (VFIO_GROUP_NOTIFY_SET_KVM
> event). When the KVM pointer
Hi Nathan,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: afe956c577b2d5a3d9834e4424587c1ebcf90c4c kbuild: Enable
-Wtautological-compare
date: 9 months ago
Document the binding for enabling mtk svs on MediaTek SoC.
Signed-off-by: Roger Lu
---
.../bindings/soc/mediatek/mtk-svs.yaml| 75 +++
1 file changed, 75 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mtk-svs.yaml
diff --git
The Smart Voltage Scaling(SVS) engine is a piece of hardware
which calculats suitable SVS bank voltages to OPP voltage table.
Then, DVFS driver could apply those SVS bank voltages to PMIC/Buck
when receiving OPP_EVENT_ADJUST_VOLTAGE.
Signed-off-by: Roger Lu
---
drivers/soc/mediatek/Kconfig |
Signed-off-by: Roger Lu
---
.../bindings/soc/mediatek/mtk-svs.yaml| 26 +++
1 file changed, 26 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/mtk-svs.yaml
b/Documentation/devicetree/bindings/soc/mediatek/mtk-svs.yaml
index
The purpose of SVS is to help find the suitable voltages
for DVFS. Therefore, if SVS bank voltages are concerned
to be wrong, we can adjust SVS bank voltages by this patch.
Signed-off-by: Roger Lu
---
drivers/soc/mediatek/mtk-svs.c | 324 +
1 file changed, 324
Signed-off-by: Roger Lu
---
drivers/soc/mediatek/mtk-svs.c | 494 -
1 file changed, 488 insertions(+), 6 deletions(-)
diff --git a/drivers/soc/mediatek/mtk-svs.c b/drivers/soc/mediatek/mtk-svs.c
index ef3aeb4b7dbd..9201e5480c6c 100644
---
add compitable/reg/irq/clock/efuse setting in svs node
Signed-off-by: Roger Lu
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index
1. SVS driver uses OPP adjust event in [1] to update OPP table voltage part.
2. SVS driver gets thermal/GPU device by node [2][3] and do device_link_add()
to make sure probe/suspend callback priority.
3. SVS driver gets CPU device by get_cpu_device() and do device_link_add()
to make sure
add compitable/reg/irq/clock/efuse/reset setting in svs node
Signed-off-by: Roger Lu
---
arch/arm64/boot/dts/mediatek/mt8192.dtsi | 34
1 file changed, 34 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8192.dtsi
b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: 9b80e4c4ddaca3501177ed41e49d0928ba2122a8 overflow: Add __must_check
attribute to check_*() helpers
date: 3 months ago
config: arm-randconfig-r031-20201226
Hi all!
On Sat, 2020-12-26 at 14:30 -0800, Theodore Dubois wrote:
[...]
> thing on macOS (please don't question my sanity :), and I've run
> into various issues stemming from macOS having a case-insensitive
> filesystem.
Case-insensitive filesystems are broken by design.
Kind regards,
Em Sat, 26 Dec 2020 13:18:58 +
Nícolas F. R. A. Prado escreveu:
> During the process of converting the documentation to reST, some links
> were converted using the following wrong syntax (and sometimes using %20
> instead of spaces):
>
The patch itself looks ok, although the description
Linus,
Please pull the latest locking/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-2020-12-27
# HEAD: 91ea62d58bd661827c328a2c6c02a87fa4aae88b softirq: Avoid bad tracing
/ lockdep interaction
Misc fixes/updates:
- Fix static keys usage
Linus,
Please pull the latest objtool/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
objtool-urgent-2020-12-27
# HEAD: 44f6a7c0755d8dd453c70557e11687bb080a6f21 objtool: Fix seg fault with
Clang non-section symbols
Fix a segfault that occurs when built
Linus,
Please pull the latest timers/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-2020-12-27
# HEAD: f6f5cd840ae782680c5e94048c72420e4e6857f9 timekeeping: Fix spelling
mistake in Kconfig "fullfill" -> "fulfill"
Update/fix two CPU sanity
Linus,
Please pull the latest sched/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-2020-12-27
# HEAD: ae7927023243dcc7389b2d59b16c09cbbeaecc36 sched: Optimize
finish_lock_switch()
Fix a context switch performance regression.
Thanks,
Currently openrisc will print a message and then hang in an infinite
loop when rebooting.
This patch adopts some code from ARM, which calls the common restart
infrastructure and hangs after a small delay if the restart infra
doesn't do anything.
Signed-off-by: Joel Stanley
---
Geert has a
[Why]
Similar to commit<0fa375e6>. If the set_state/can_switch code access the
drm_device when dev is not bound,
a null pointer dereference can happen.
[How]
Add sanity checks to prevent it.
Signed-off-by: Defang Bo
---
drivers/gpu/drm/radeon/radeon_device.c | 6 ++
1 file changed, 6
Hi Hsin-Hsiung,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20201223]
[cannot apply to regulator/for-next robh/for-next v5.10 v5.10-rc7 v5.10-rc6
v5.10]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
On Mon, Dec 21, 2020 at 04:50:31PM +0800, Dinghao Liu wrote:
> mlx5e_create_ttc_table_groups() frees ft->g on failure of
> kvzalloc(), but such failure will be caught by its caller
> in mlx5e_create_ttc_table() and ft->g will be freed again
> in mlx5e_destroy_flow_table(). The same issue also
On Wed, Dec 23, 2020 at 11:30:41AM -0800, t...@redhat.com wrote:
> From: Tom Rix
>
> This change fixes the checkpatch warning described in this commit
> commit cbacb5ab0aa0 ("docs: printk-formats: Stop encouraging use of
> unnecessary %h[xudi] and %hh[xudi]")
>
> Standard integer promotion is
On Mon, Dec 21, 2020 at 07:27:31PM +0800, Dinghao Liu wrote:
> When mlx5_create_flow_group() fails, ft->g should be
> freed just like when kvzalloc() fails. The caller of
> mlx5e_create_l2_table_groups() does not catch this
> issue on failure, which leads to memleak.
>
> Signed-off-by: Dinghao Liu
201 - 249 of 249 matches
Mail list logo
