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
wlc_phy_txpwr_srom_read_lcnphy before returning.
Signed-off-b
On Monday 07 September 2020 17:43:53 Andrew Lunn wrote:
> > I would not say it is a "new feature". But rather that patch in this
> > email fixes issue that Linux kernel did not set correct MAC address for
> > DSA slave ports. I think it is something which could be backported also
> > to stable rele
Hi,
On Thu, Sep 03, 2020 at 10:00:32AM +0200, Maxime Ripard wrote:
> Hi everyone,
>
> Here's a (pretty long) series to introduce support in the VC4 DRM driver
> for the display pipeline found in the BCM2711 (and thus the RaspberryPi 4).
>
> The main differences are that there's two HDMI controll
Hi,
On Fri, Sep 04, 2020 at 10:46:26AM +0100, Dave Stevenson wrote:
> On Thu, 3 Sep 2020 at 09:03, Maxime Ripard wrote:
> >
> > From: Hoegeun Kwon
> >
> > The BCM2711 has another clock that needs to be ramped up depending on the
> > pixel rate: the pixel BVB clock. Add the code to adjust that cl
The S3C RTC requires 32768 Hz clock as input which is provided by PMIC.
However the PMIC is not described in DTS at all so at least add
a workaround to model its clock with a fixed-clock.
This fixes dtbs_check warnings:
rtc@e280: clocks: [[2, 145]] is too short
rtc@e280: clock-names:
Replace hard-coded flags with defines for readability. No functional
change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-goni.dts | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/arch/arm/boot/dts/s5pv210-goni.dts
b/arch/arm/boot/dts
On Fri, Aug 07, 2020 at 12:16:35PM -0700, Sultan Alsawaf wrote:
> From: Sultan Alsawaf
>
> There's no reason to hold an RCU read lock the entire time while
> optimistically spinning for a mutex lock. This can needlessly lengthen
> RCU grace periods and slow down synchronize_rcu() when it doesn't
On 7 Sep 2020, at 8:22, Kirill A. Shutemov wrote:
> On Wed, Sep 02, 2020 at 02:06:13PM -0400, Zi Yan wrote:
>> From: Zi Yan
>>
>> When depositing page table pages for 1GB THPs, we need 512 PTE pages +
>> 1 PMD page. Instead of counting and depositing 513 pages, we can use the
>> PMD page as a lea
From: Andres Beltran
Currently, pointers to guest memory are passed to Hyper-V as
transaction IDs in netvsc. In the face of errors or malicious
behavior in Hyper-V, netvsc should not expose or trust the transaction
IDs returned by Hyper-V to be valid guest memory addresses. Instead,
use small int
From: Andres Beltran
Currently, pointers to guest memory are passed to Hyper-V as
transaction IDs in storvsc. In the face of errors or malicious
behavior in Hyper-V, storvsc should not expose or trust the transaction
IDs returned by Hyper-V to be valid guest memory addresses. Instead,
use small i
From: Andres Beltran
Currently, VMbus drivers use pointers into guest memory as request IDs
for interactions with Hyper-V. To be more robust in the face of errors
or malicious behavior from a compromised Hyper-V, avoid exposing
guest memory addresses to Hyper-V. Also avoid Hyper-V giving back a
b
The fixed regulators are kept under dedicated "regulators" node but this
causes multiple dtschema warnings:
regulators: $nodename:0: 'regulators' does not match
'^([a-z][a-z0-9\\-]+-bus|bus|soc|axi|ahb|apb)(@[0-9a-f]+)?$'
regulators: #size-cells:0:0: 0 is not one of [1, 2]
regulators: fixed
The fixed regulators are kept under dedicated "regulators" node but this
causes multiple dtschema warnings:
regulators: $nodename:0: 'regulators' does not match
'^([a-z][a-z0-9\\-]+-bus|bus|soc|axi|ahb|apb)(@[0-9a-f]+)?$'
regulators: #size-cells:0:0: 0 is not one of [1, 2]
regulators: fixed
The S3C RTC requires 32768 Hz clock as input which is provided by PMIC.
However the PMIC is not described in DTS at all so at least add
a workaround to model its clock with a fixed-clock.
This fixes dtbs_check warnings:
rtc@e280: clocks: [[2, 145]] is too short
rtc@e280: clock-names:
Currently, VMbus drivers use pointers into guest memory as request IDs
for interactions with Hyper-V. To be more robust in the face of errors
or malicious behavior from a compromised Hyper-V, avoid exposing
guest memory addresses to Hyper-V. Also avoid Hyper-V giving back a
bad request ID that is t
"gpios" property is deprecated. Update the Aquila DTS to fix
dtbs_checks warnings like:
i2c-pmic: 'sda-gpios' is a required property
i2c-pmic: 'scl-gpios' is a required property
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-aquila.dts | 4 ++--
1 file changed, 2 insertio
"Rakesh Pillai" writes:
>> > --- a/drivers/net/wireless/ath/ath10k/qmi.c
>> > +++ b/drivers/net/wireless/ath/ath10k/qmi.c
>> > @@ -576,6 +576,8 @@ static int ath10k_qmi_cap_send_sync_msg(struct
>> ath10k_qmi *qmi)
>> >if (resp->chip_info_valid) {
>> >qmi->chip_info.chip_id = resp-
Hi Stefan,
Thank you for the patch.
On Mon, Sep 07, 2020 at 06:03:43PM +0200, Stefan Agner wrote:
> The lcdif IP does not support a framebuffer pitch (stride) other than
> the CRTC width. Check for equality and reject the state otherwise.
>
> This prevents a distorted picture when using 640x800
Replace hard-coded flags with defines for readability. No functional
change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-smdkv210.dts | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/s5pv210-smdkv210.dts
b/arch/arm/boot/dts/s5pv210-sm
The S3C RTC requires 32768 Hz clock as input which is provided by PMIC.
However the PMIC is not described in DTS at all so at least add
a workaround to model its clock with a fixed-clock.
This fixes dtbs_check warnings:
rtc@e280: clocks: [[2, 145]] is too short
rtc@e280: clock-names:
"gpios" property is deprecated. Update the Goni DTS to fix
dtbs_checks warnings like:
i2c-pmic: 'sda-gpios' is a required property
i2c-pmic: 'scl-gpios' is a required property
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-goni.dts | 4 ++--
1 file changed, 2 insertions(+
Hi all,
one of my colleagues has taken a look at device boot times and stumbled
across a pretty big amount of kernel boot time being spent in
tracer_init_tracefs(). On this particular i.MX6Q based device the
kernel spends more than 1 second in this function, which is a
significant amount of the ov
Hi!
On Fri, Sep 04, 2020 at 06:16:16PM +0800, Jian-Hong Pan wrote:
> Thanks for version 5 patch series!
>
> I applied it based on linux-next tag next-20200828 and build it with
> the config [1] to test on RPi 4
> However, It fails to get HDMI state machine clock and pixel bcb clock.
> Then, vc4-d
On Mon, Aug 03, 2020 at 03:52:40PM +1200, Mark Tomlinson wrote:
> The core interrupt code expects the irq_set_affinity call to update the
> effective affinity for the interrupt. This was not being done, so update
> iproc_msi_irq_set_affinity() to do so.
>
> Fixes: 3bc2b2348835 ("PCI: iproc: Add iP
The device tree schema expects SPI controller to be named "spi",
otherwise dtbs_check complain with a warning like:
spi-gpio-0: $nodename:0: 'spi-gpio-0' does not match '^spi(@.*|-[0-9a-f])*$'
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 2 +-
1 file changed,
Hello Ahmad,
On Mon, Sep 07, 2020 at 05:31:35PM +0200, Ahmad Fatoum wrote:
> The gpio-siox driver uses handle_nested_irq() to implement its
> interrupt support. This is only capable of handling threaded irq
> actions. For a hardirq action it triggers a NULL pointer oops.
> (It calls action->thread
Replace hard-coded flags with defines for readability. No functional
change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-goni.dts | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/s5pv210-goni.dts
b/arch/arm/boot/dts/s5pv210-goni.dts
i
dtschema expects DMA channels in specific order (tx, rx and tx-sec).
The order actually should not matter because dma-names is used however
let's make it aligned with dtschema to suppress warnings like:
i2s@eee3: dma-names: ['rx', 'tx', 'tx-sec'] is not valid under any of the
given schemas
Replace hard-coded flags with defines for readability. No functional
change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/s5pv210-aquila.dts | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/s5pv210-aquila.dts
b/arch/arm/boot/dts/s5
The fixed clocks are kept under dedicated 'external-clocks' node, thus a
fake 'reg' was added. This is not correct with dtschema as fixed-clock
binding does not have a 'reg' property. Moving fixed clocks out of
'soc' to root node fixes multiple dtbs_check warnings:
external-clocks: $nodename:0
The S3C RTC requires 32768 Hz clock as input which is provided by PMIC.
However there is no such clock provider but rather a regulator driver
which registers the clock as a regulator. This is an old driver which
will not be updated so add a workaround - a fixed-clock to fill missing
clock phandle
The ADC in S5Pv210 does not have ADC phy registers in separate block for
which syscon would be needed. Remove this requirement to fix dtbs_check
warnings like:
arch/arm/boot/dts/s5pv210-fascinate4g.dt.yaml: adc@e170:
'samsung,syscon-phandle' is a required property
Signed-off-by: Krzysztof
Add compatible for the Samsung S5Pv210 SoC PMU.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/arm/samsung/pmu.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.yaml
b/Documentation/devicetree/bindings/arm/sams
Hi
The patchset tries to remove most of the dtschema warnings. Due to lack
of hardware it was not tested.
Best regards,
Krzysztof
Krzysztof Kozlowski (25):
dt-bindings: samsung: pmu: document S5Pv210
dt-bindings: iio: adc: exynos-adc: require second interrupt with touch
screen
dt-bin
Doug Anderson writes:
> Hi,
>
> On Fri, Jun 26, 2020 at 11:02 AM Rakesh Pillai wrote:
>>
>> Add the support to vote for the chain-1
>> voltage regulator for WCN3990. This is
>> added as an optional property.
>>
>> Rakesh Pillai (2):
>> dt: bindings: Add new regulator as optional property for W
07.09.2020 11:21, Andy Shevchenko пишет:
> On Sun, Sep 6, 2020 at 9:51 PM Dmitry Osipenko wrote:
>>
>> Use clk-bulk helpers and factor out clocks initialization into separate
>> function in order to make code cleaner.
>
> Suggested-by? (If you consider it appropriate)
Sure! It turned out to be a
07.09.2020 11:20, Andy Shevchenko пишет:
> On Sun, Sep 6, 2020 at 9:51 PM Dmitry Osipenko wrote:
>>
>> The driver's probe function code is a bit difficult to read. This patch
>> reorders code of the probe function, forming groups of code that are easy
>> to work with. The reset_control_get() now m
Hi Jakub,
On 05/09/2020 03:10, Jakub Kicinski wrote:
On Sat, 5 Sep 2020 02:09:24 +0300 Grygorii Strashko wrote:
The TI J721E (CPSW9g) ALE version is similar, in general, to Sitara AM3/4/5
CPSW ALE, but has more extended functions and different ALE VLAN entry
format.
This patch adds support for
On Fri, Sep 04, 2020 at 11:06:47AM -0700, t...@redhat.com wrote:
> From: Tom Rix
>
> clang static analyzer reports this problem
>
> i2c-amd-mp2-plat.c:174:9: warning: Branch condition evaluates
> to a garbage value
> return err ? err : num;
>^~~
>
> err is not initiali
On Sat, Sep 05, 2020 at 11:17:55AM -0700, Jakub Kicinski wrote:
> On Thu, 3 Sep 2020 06:42:57 -0500 Dan Murphy wrote:
> > Add the ability to advertise the Fiber connection if the strap or the
> > op-mode is configured for 100Base-FX.
> >
> > Auto negotiation is not supported on this PHY when in fi
Hi Rob,
On 2020/09/04 7:25, Rob Herring wrote:
On Fri, Aug 21, 2020 at 1:05 AM Kunihiko Hayashi
wrote:
On 2020/08/18 1:39, Rob Herring wrote:
On Fri, Aug 7, 2020 at 4:25 AM Kunihiko Hayashi
wrote:
Even if phy driver doesn't probe, the error message can't be distinguished
from other errors
On Mon, Sep 7, 2020 at 5:23 PM Geert Uytterhoeven wrote:
>
> Hi Andy,
>
> On Mon, Sep 7, 2020 at 4:14 PM Andy Shevchenko
> wrote:
> > On Mon, Sep 07, 2020 at 03:49:23PM +0200, Bartosz Golaszewski wrote:
> > > On Mon, Sep 7, 2020 at 2:22 PM Greg Kroah-Hartman
> > > wrote:
> > > > On Mon, Sep 07,
Hi Rob,
On 2020/09/04 7:12, Rob Herring wrote:
On Fri, Aug 21, 2020 at 1:05 AM Kunihiko Hayashi
wrote:
On 2020/08/18 1:48, Rob Herring wrote:
On Fri, Aug 7, 2020 at 4:25 AM Kunihiko Hayashi
wrote:
This gets iATU register area from reg property. In Synopsys DWC version
4.80 or later, since
On Fri, 28 Aug 2020 11:18:22 +0800, Xiaoming Ni wrote:
>
Applied to arm64 (for-next/tpyos), thanks!
[1/1] arm64: fix some spelling mistakes in the comments by codespell
https://git.kernel.org/arm64/c/ad14c19242b5
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://wi
Hi Eric,
On 9/4/2020 11:21 AM, Auger Eric wrote:
Hi Diana,
On 8/26/20 11:33 AM, Diana Craciun wrote:
Currently only resetting the DPRC container is supported which
will reset all the objects inside it. Resetting individual
objects is possible from the userspace by issueing commands
towards MC
07.09.2020 18:34, Andy Shevchenko пишет:
> On Mon, Sep 7, 2020 at 6:25 PM Dmitry Osipenko wrote:
>> 07.09.2020 18:05, Andy Shevchenko пишет:
>>> On Mon, Sep 7, 2020 at 5:32 PM Dmitry Osipenko wrote:
07.09.2020 11:10, Andy Shevchenko пишет:
>
> ...
>
Would be great if anyone could put
On Wed, 26 Aug 2020 22:17:58 +0800, Zenghui Yu wrote:
> The actual size of level-1 stream table is l1size. This looks like an
> oversight on commit d2e88e7c081ef ("iommu/arm-smmu: Fix LOG2SIZE setting
> for 2-level stream tables") which forgot to update the @size in error
> message as well.
>
> As
On Tue, 4 Aug 2020 16:53:47 +0800, Yue Hu wrote:
> Currently, there are different description strings in die() such as
> die("Oops",,), die("Oops - BUG",,). And panic() called by die() will
> always show "Fatal exception" or "Fatal exception in interrupt".
>
> Note that panic() will run any panic
On Tue, 18 Aug 2020 14:36:23 +0800, Zenghui Yu wrote:
> * From v1 [1]:
> - As pointed out by Hanjun, remove two now unused inline functions.
> Compile tested with CONFIG_IOMMU_API is not selected.
>
> [1] https://lore.kernel.org/r/20200817105946.1511-1-yuzeng...@huawei.com
>
> Zenghui Yu (2
Hi Chun-Kuang,
> Why don't you add compatible of "mediatek,mt8167-mmsys"?
I forgot to remove 'mmsys' from the commit message. I decided to add
the documentation as part of the series that add support for MT8167 to
drivers/soc/mediatek/mtk-mmsys.c.
If you think it would be better to document it h
On Tue, 11 Aug 2020 13:35:05 +0800, Leo Yan wrote:
> This patch is to add the general hardware last level cache (LLC) events
> for PMUv3: one event is for LLC access and another is for LLC miss.
>
> With this change, perf tool can support last level cache profiling,
> below is an example to demons
On Tue, 1 Sep 2020 17:11:54 +0800, yanfei...@windriver.com wrote:
> Fix a typo in comment of arm64_numa_init. 'encomapssing' should
> be 'encompassing'.
Applied to arm64 (for-next/tpyos), thanks!
[1/1] arm64/numa: Fix a typo in comment of arm64_numa_init
https://git.kernel.org/arm64/c/9a747
Add compatible string for r8a7742. No driver change is needed as
"renesas,rcar-gen2-vin" will activate the right code.
Signed-off-by: Lad Prabhakar
Reviewed-by: Biju Das
---
Documentation/devicetree/bindings/media/renesas,vin.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentatio
07.09.2020 11:27, Andy Shevchenko пишет:
> On Sun, Sep 6, 2020 at 9:52 PM Dmitry Osipenko wrote:
>>
>> Reorder location of functions in the code in order to have definition
>> of functions closer to the place of the invocation. This change makes
>> easier to navigate around the code and removes th
From: Yu Chen
There are some problems at the initialization part of this phy.
Solve them.
Signed-off-by: Yu Chen
Signed-off-by: Mauro Carvalho Chehab
---
drivers/phy/hisilicon/phy-hi3670-usb3.c | 70 +++--
1 file changed, 32 insertions(+), 38 deletions(-)
diff --git a/dri
The lcdif IP does not support a framebuffer pitch (stride) other than
the CRTC width. Check for equality and reject the state otherwise.
This prevents a distorted picture when using 640x800 and running the
Mesa graphics stack. Mesa tires to use a cache aligned stride, which
leads at that particula
From: Yu Chen
The HiKey960 has a fairly complex USB configuration due to it
needing to support a USB-C port for host/device mode and multiple
USB-A ports in host mode, all using a single USB controller.
See schematics here:
https://github.com/96boards/documentation/raw/master/consumer/hikey/h
This binding driver is needed for Hikey 970 to work,
as otherwise a Serror is produced:
[1.837458] SError Interrupt on CPU0, code 0xbf02 -- SError
[1.837462] CPU: 0 PID: 74 Comm: kworker/0:1 Not tainted 5.8.0+ #205
[1.837463] Hardware name: HiKey970 (DT)
[1.8374
Use the new YAML for this physical layer.
Signed-off-by: Mauro Carvalho Chehab
---
.../bindings/phy/hisilicon,hi3670-usb3.yaml | 72 +++
.../bindings/phy/phy-hi3670-usb3.txt | 25 ---
2 files changed, 72 insertions(+), 25 deletions(-)
create mode 100644
Documenta
Add the USB3 bindings for Kirin 970 phy and Hikey 970 board.
Signed-off-by: Mauro Carvalho Chehab
---
.../boot/dts/hisilicon/hi3670-hikey970.dts| 102 ++
arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 58 ++
drivers/misc/hisi_hikey_usb.c | 29 ++---
On Fri, Aug 21, 2020 at 12:57:54PM -0700, kan.li...@linux.intel.com wrote:
> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
> index 0f3d01562ded..fa08d810dcd2 100644
> --- a/arch/x86/events/core.c
> +++ b/arch/x86/events/core.c
> @@ -1440,7 +1440,10 @@ static void x86_pmu_start(struct
Address the issues reported by checkpatch --strict,
and add a SPDX tag.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/phy/hisilicon/phy-hi3670-usb3.c | 157
1 file changed, 76 insertions(+), 81 deletions(-)
diff --git a/drivers/phy/hisilicon/phy-hi3670-usb3.c
b/driv
From: Yu Chen
Add the Hisilicon Kirin 3670 USB phy driver just after the
hi3660, using the same namespace.
This driver was imported from Linaro's official Hikey 970
tree, from the original patch, removing the addition of
the dwg3-specific parts.
Signed-off-by: Yu Chen
Signed-off-by: Mauro Carv
Rename hikey970 to hi3670, in order to use a namespace
similar to hi3660 driver.
Signed-off-by: Mauro Carvalho Chehab
---
.../bindings/phy/phy-hi3670-usb3.txt | 4 +-
drivers/phy/hisilicon/phy-hi3670-usb3.c | 98 +--
2 files changed, 51 insertions(+), 51 deletions
On Mon, Sep 07, 2020 at 04:24:00PM +1000, Herbert Xu wrote:
> On Sun, Sep 06, 2020 at 04:52:24PM +0800, kernel test robot wrote:
> >
> > >> drivers/crypto/allwinner/sun4i-ss/sun4i-ss-hash.c:483:35: sparse:
> > >> sparse: incorrect type in assignment (different base types) @@
> > >> expected u
Now that this driver was added upsream, it needs a maintainer.
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2f497c7d659c..267ba0b7a52e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
Do some changes at the DT properties in order to make it
follow the phy-hi3660-usb3 example and to simplify
usb3-phy-tx-vboost-lvl name.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/phy/hisilicon/phy-hi3670-usb3.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a
Add the PHY layer for Hikey 970 and a misc driver that it is
required for the USB hub to work. The same USB hub is needed
by Hikey 960.
That's the second version, addressing the points raised by
Mark on the RFC version and adding an extra patch in order for
it to use the dwc3-of-simple driver. Su
Hello,
syzbot found the following issue on:
HEAD commit:fc3abb53 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ccc8ae90
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
das
The HiKey 970 board is similar to Hikey 960 with regards
to its USB configutation: it also relies on a USB HUB
that is used when DWC3 is at host mode.
However, it requires a few extra DT settings, as it
uses a voltage regulator and GPIO reset pin.
Add support for them.
Signed-off-by: Mauro Carva
Hi Hugues,
Thank you for the review.
On Mon, Sep 7, 2020 at 10:44 AM Hugues FRUCHET wrote:
>
> Hi Prabhakar,
>
> Thanks for your patches, good to see one more OV5640 stakeholder
> upstreaming some fixes/features.
>
> I'm also using a parallel setup with OV5640 connected on STM32 DCMI
> camera in
On Tue, Aug 11, 2020 at 09:29:24AM +0800, Anson Huang wrote:
> When devm_clk_get() returns -EPROBE_DEFER, i.MX6 PCI driver should
> NOT print error message, use dev_err_probe() to handle it.
>
> Signed-off-by: Anson Huang
> ---
> drivers/pci/controller/dwc/pci-imx6.c | 35
> +++-
On Mon, Sep 7, 2020 at 4:02 PM Marek Szyprowski
wrote:
>
> Hi Tomasz,
>
> On 07.09.2020 15:07, Tomasz Figa wrote:
> > On Fri, Sep 4, 2020 at 3:35 PM Marek Szyprowski
> > wrote:
> >> Use recently introduced common wrappers operating directly on the struct
> >> sg_table objects and scatterlist page
On Wed, Sep 02, 2020 at 04:35:33PM +0200, Takashi Iwai wrote:
> On Wed, 02 Sep 2020 13:01:03 +0200,
> Greg Kroah-Hartman wrote:
> >
> > snd_usb_pipe_sanity_check() is a great function, so let's move it into
> > the USB core so that other parts of the kernel, including the USB core,
> > can call it
Em Mon, 07 Sep 2020 17:04:31 +0300
Felipe Balbi escreveu:
> Hi Mauro,
>
> Mauro Carvalho Chehab writes:
>
> > Hi Felipe/Greg,
> >
> > What's the status of this patch?
>
> to be frank, I don't think I have this in my inbox anymore.
>
> > I tested here, together with the Hikey 970 phy RFC p
Hi All,
This patch series enables PCIe, SPI NOR flash, CAN0 and SD2 LED indication
on iWave G21D-Q7 board.
Patches apply on top of [1] and also dependent on patch [2]
[1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/
renesas-devel.git/log/?h=renesas-arm-dt-for-v5.10
[2] https://patch
This patch enables CAN1 interface exposed through connector J20 on the
carrier board.
Signed-off-by: Lad Prabhakar
Reviewed-by: Chris Paterson
---
arch/arm/boot/dts/r8a7742-iwg21d-q7.dts | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7742-iwg21d-
Add support for LED trigger on SD2 interface.
Signed-off-by: Lad Prabhakar
Reviewed-by: Chris Paterson
Reviewed-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a7742-iwg21d-q7.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7742-iwg21d-q7.dts
b/arch/arm
Add support for the SPI NOR device which is connected to MSIOF0 interface
on the iWave RainboW-G21d-q7 board.
Signed-off-by: Lad Prabhakar
Reviewed-by: Chris Paterson
Reviewed-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a7742-iwg21d-q7.dts | 31 +
1 file changed, 31
Hi, Fabien:
Fabien Parent 於 2020年9月7日 週一 下午8:57寫道：
>
> Add binding documentation for topckgen, apmixedsys, infracfg, audsys,
> imgsys, mfgcfg, mmsys, vdecsys on MT8167 SoC.
Why don't you add compatible of "mediatek,mt8167-mmsys"?
Regards,
Chun-Kuang.
>
> Signed-off-by: Fabien Parent
> ---
>
The usb_control_msg_send() and usb_control_msg_recv() calls can return
an error if a "short" write/read happens, and they can handle data off
of the stack, so move the driver over to using those calls instead,
saving some logic when dynamically allocating memory.
Cc: Marcel Holtmann
Cc: Johan Hed
On Mon, Aug 10, 2020 at 06:41:54PM +0100, Lad Prabhakar wrote:
> Hi All,
>
> This patch set adds PCIe instance to r8a7742 Soc dtsi.
> patches apply on-top of [1] + [2]
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/
> renesas-devel.git/log/?h=renesas-arm-dt-for-v5.10
> [2] http
The usb_control_msg_recv() function can handle data on the stack, as
well as properly detecting short reads, so move to use that function
instead of the older usb_control_msg() call. This ends up removing a
lot of extra lines in the driver.
Cc: Juergen Stuber
Cc: legousb-de...@lists.sourceforge.
A USB device will always haev a bi-directional endpoint 0, that's just
how the devices work, so no need to check for that in a few quirk tests
as it will always pass.
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Alexander Tsoy
Cc: alsa-de...@alsa-project.org
Reported-by: Alan Stern
Signed-off-by:
The usb_control_msg_send() call can handle data on the stack, as well as
returning an error if a "short" write happens, so move the driver over
to using that call instead. This ends up removing a helper function
that is no longer needed.
Cc: Jaroslav Kysela
Cc: alsa-de...@alsa-project.org
Review
On Mon, Sep 07, 2020 at 04:56:44PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Sep 07, 2020 at 04:51:00PM +0200, Greg Kroah-Hartman wrote:
> > There are a few calls to usb_control_msg() that can be converted to use
> > usb_control_msg_send() instead, so do that in order to make the error
> > checkin
There are a few calls to usb_control_msg() that can be converted to use
usb_control_msg_send() instead, so do that in order to make the error
checking a bit simpler and the code smaller.
Cc: Alan Stern
Signed-off-by: Greg Kroah-Hartman
---
v2:
- dropped changes to usb_req_set_sel() thanks to re
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:
>
> [ 11.607251] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
> [ 11.607337] sp5100-tco sp5
The usb_control_msg_send() and usb_control_msg_recv() calls can return
an error if a "short" write/read happens, and they can handle data off
of the stack, so move the driver over to using those calls instead,
saving some logic when dynamically allocating memory.
Cc: Jaroslav Kysela
Cc: Vasily Kh
From: Tom Rix
clang static analyzer reports this problem
sb_edac.c:959:2: warning: Undefined or garbage value
returned to caller
return type;
^~~
This is a false positive.
However by initializing the type to DEV_UNKNOWN the 3 case can be
removed from the switch, savin
On Mon, Sep 07, 2020 at 02:41:49PM +1200, Chris Packham wrote:
> 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
Andrew
The stack dumping code needs to work for both kernel and user mode,
and currently this works by using set_fs() and then calling get_user()
to carefully access a potentially invalid pointer.
Change both locations to handle user and kernel mode differently, using
get_kernel_nofault() in case of kern
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:
>>
>> [ 11.607251] sp5100_tco: SP5100/SB800 TCO WatchDo
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.
>
> Fixes: 43e28ba87708 ("ARM: dts: Use armada-370-xp as a base for
> armada-xp-98dx3236"
On Mon, Sep 07, 2020 at 02:41:47PM +1200, Chris Packham wrote:
> 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
On Mon 2020-09-07 12:36:45, John Ogness wrote:
> On 2020-09-07, Petr Mladek wrote:
> > This extra metadata are not currently read by crashdump tools.
>
> crash [0] prints dictionary data.
> [0] https://github.com/crash-utility/crash
Grr, I have missed this. It makes things more complicated.
We
> I would not say it is a "new feature". But rather that patch in this
> email fixes issue that Linux kernel did not set correct MAC address for
> DSA slave ports. I think it is something which could be backported also
> to stable releases as "ignoring" vendor/factory MAC address is not
> correct b
The epoll_wait() system call wrapper is one of the remaining users of
the set_fs() infrasturcture for Arm. Changing it to not require set_fs()
is rather complex unfortunately.
The approach I'm taking here is to allow architectures to override
the code that copies the output to user space, and let
On Mon, 7 Sep 2020 15:40:46 +0200
Marco Elver wrote:
> From: Alexander Potapenko
>
> This adds the Kernel Electric-Fence (KFENCE) infrastructure. KFENCE is a
> low-overhead sampling-based memory safety error detector of heap
> use-after-free, invalid-free, and out-of-bounds access errors.
>
>
The epoll_wait() syscall has a special version for OABI compat
mode to convert the arguments to the EABI structure layout
of the kernel. However, the later epoll_pwait() syscall was
added in arch/arm in linux-2.6.32 without this conversion.
Use the same kind of handler for both.
Fixes: 369842658a
801 - 900 of 1490 matches
Mail list logo
