Hi Biju,
On Wed, 2019-05-22 at 08:05 +, Biju Das wrote:
> Hi Heikki,
>
> Thanks for the feedback.
>
> > Subject: Re: [PATCH v5 4/6] usb: roles: add API to get usb_role_switch by
> > node
> >
> > On Mon, May 20, 2019 at 09:45:46AM +, Biju Das wrote:
> > >
> > >
> > > Hi Heikki,
> > >
> >
Hi Andrey,
Am Mittwoch, den 22.05.2019, 00:12 -0700 schrieb Andrey Smirnov:
> Cabling used to connect devices to USBH1 on RDU2 does not meet USB
> spec cable quality and cable length requirements to operate at High
> Speed, so limit the port to Full Speed only.
Really? I thought this issue is spe
On Wed, May 22, 2019 at 02:23:23AM +0300, Aaro Koskinen wrote:
> Hi,
>
> On Mon, May 20, 2019 at 09:05:33PM +0200, Corentin Labbe wrote:
> > Hello
> >
> > I am working on adding a maximum set of qemu machine on kernelCI.
>
> That's cool.
>
> > For OMAP, five machine exists and I fail to boot an
On May 22, 2019 4:13:59 AM CDT, James Morse wrote:
>Hi Boris,
>
>On 21/05/2019 19:21, Borislav Petkov wrote:
>> On Tue, May 21, 2019 at 11:00:59AM +0530, Yash Shah wrote:
>>> The prerequisite patch (sifive_l2_cache driver) has been merged into
>>> mainline v5.2-rc1
>>> It should be OK to merge thi
Hi Andrey,
Am Mittwoch, den 22.05.2019, 00:12 -0700 schrieb Andrey Smirnov:
> Add node for UCS1002 USB charger chip connected to front panel USB and
> replace "regulator-fixed" previously used to control VBUS.
I've had a similar version of this patch, but also added GPIO hogs for
the UCS1002 conf
Include corresponding headerfile for
function at91_suspend_entering_slow_clock().
../arch/arm/mach-at91/pm.c:279:5: warning: no previous prototype for
‘at91_suspend_entering_slow_clock’ [-Wmissing-prototypes]
int at91_suspend_entering_slow_clock(void)
^~~~
Sign
On Tue, May 21, 2019 at 09:46:55PM -0300, Fabio Lima wrote:
> This patch resolves the following warning from checkpatch.pl
> WARNING: Missing a blank line after declarations
>
> Signed-off-by: Fabio Lima
> ---
> drivers/staging/rtl8723bs/core/rtw_debug.c | 2 ++
> 1 file changed, 2 insertions(+)
Include corresponing header file for function
arch_timer_arch_init().
../arch/arm/kernel/arch_timer.c:34:12: warning: no previous prototype for
‘arch_timer_arch_init’ [-Wmissing-prototypes]
int __init arch_timer_arch_init(void)
^~~~
Signed-off-by: Philippe Mazenauer
No. This isn't the right fix. We should declare them as int instead.
regards,
dan carpenter
Replace kmalloc + memcpy with kmemdup.
This was reported by coccinelle.
Signed-off-by: Bharath Vedartham
---
drivers/message/fusion/mptbase.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/message/fusion/mptbase.c b/drivers/message/fusion/mptbase.c
index d8882b0..
On Thu, 16 May 2019 18:30:32 -0500
Parav Pandit wrote:
> This patch addresses below two issues and prepares the code to address
> 3rd issue listed below.
>
> 1. mdev device is placed on the mdev bus before it is created in the
> vendor driver. Once a device is placed on the mdev bus without crea
Include corresponding header file "core.h" for function
highbank_pm_init().
../arch/arm/mach-highbank/pm.c:54:13: warning: no previous prototype for
‘highbank_pm_init’ [-Wmissing-prototypes]
void __init highbank_pm_init(void)
^~~~
Signed-off-by: Philippe Mazenauer
---
On Thu, 16 May 2019 18:30:33 -0500
Parav Pandit wrote:
> If device is removal is initiated by two threads as below, mdev core
> attempts to create a syfs remove file on stale device.
> During this flow, below [1] call trace is observed.
>
> cpu-0cpu-1
>
Include corresponding header file for function
module_frob_arch_sections().
../arch/arm/kernel/module-plts.c:191:5: warning: no previous prototype for
‘module_frob_arch_sections’ [-Wmissing-prototypes]
int module_frob_arch_sections(Elf_Ehdr *ehdr, Elf_Shdr *sechdrs,
^~~
On Mon, 20 May 2019 19:54:59 +
Parav Pandit wrote:
> Seems 3rd patch will take few more days to settle down with new flag and its
> review.
> Given that fix of 3rd patch is fixing a different race condition, if patch 1
> and 2 look ok, shall we move forward with those 2 fixes it in 5.2-rc?
Starting with GCC 9, -Warray-bounds detects cases when memset is called
starting on a member of a struct but the size to be cleared ends up
writing over further members.
Such a call happens in the trace code to clear, at once, all members
after and including `seq` on struct trace_iterator:
In
There is ecspi ERR009165 on i.mx6/7 soc family, which cause FIFO
transfer to be send twice in DMA mode. Please get more information from:
https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf. The workaround is adding
new sdma ram script which works in XCH mode as PIO inside sdma instead
of SMC mode,
There are two ways for SDMA accessing SPBA devices: one is SDMA->AIPS
->SPBA(masterA port), another is SDMA->SPBA(masterC port). Please refer
to the 'Figure 58-1. i.MX 6Dual/6Quad SPBA connectivity' of i.mx6DQ
Reference Manual. SDMA provide the corresponding app_2_mcu/mcu_2_app and
shp_2_mcu/mcu_
Make function machine_crash_nonpanic_core() static, as it is only
referenced in this file.
../arch/arm/kernel/machine_kexec.c:82:6: warning: no previous prototype for
‘machine_crash_nonpanic_core’ [-Wmissing-prototypes]
void machine_crash_nonpanic_core(void *unused)
^~~
There are two ways for SDMA accessing SPBA devices: one is SDMA->AIPS
->SPBA(masterA port), another is SDMA->SPBA(masterC port). Please refer
to the 'Figure 58-1. i.MX 6Dual/6Quad SPBA connectivity' of i.mx6DQ
Reference Manual. SDMA provide the corresponding app_2_mcu/mcu_2_app and
shp_2_mcu/mcu_
Since sdma_transfer_init() will do sdma_load_context before any
sdma transfer, no need once more in sdma_config_channel().
Signed-off-by: Robin Gong
Acked-by: Vinod Koul
---
drivers/dma/imx-sdma.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/dma/imx-sdma.c b/d
ERR009165 fixed from i.mx6ul, add its compatible name in binding
doc.
Signed-off-by: Robin Gong
Acked-by: Mark Brown
---
Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt
b/Documenta
This reverts commit ad0d92d7ba6aecbe2705907c38ff8d8be4da1e9c, because
in spi-imx case, burst length may be changed dynamically.
Signed-off-by: Robin Gong
---
drivers/dma/imx-sdma.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 99d
ECSPI issue fixed from i.mx6ul at hardware level, no need
ERR009165 anymore on those chips such as i.mx8mq. Add i.mx6sx
from where i.mx6ul source.
Signed-off-by: Robin Gong
Acked-by: Vinod Koul
---
drivers/dma/imx-sdma.c | 51 +-
1 file changed, 5
Add i.mx6ul and i.mx6sx compatible name in binding doc.
Signed-off-by: Robin Gong
---
Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt
b/Documentation/devicetree/bindings/dma/fsl-i
ERR009165 fixed on i.mx6ul/6ull/6sll. All other i.mx6/7 and
i.mx8m/8mm still need this errata. Please refer to nxp official
errata document from https://www.nxp.com/ .
For removing workaround on those chips. Add new i.mx6ul type.
Signed-off-by: Robin Gong
Acked-by: Mark Brown
---
drivers/spi/s
On 22/05/2019 10:53, Dan Carpenter wrote:
> No. This isn't the right fix. We should declare them as int instead.
Doh, brown paper bag time. I'll do a V2.
>
> regards,
> dan carpenter
>
Add mcu_2_ecspi script to fix ecspi errata ERR009165.
Signed-off-by: Robin Gong
Acked-by: Vinod Koul
---
drivers/dma/imx-sdma.c | 3 +++
include/linux/platform_data/dma-imx-sdma.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-
Change to XCH mode even in dma mode, please refer to the below
errata:
https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf
Signed-off-by: Robin Gong
Acked-by: Mark Brown
---
drivers/spi/spi-imx.c | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/drivers/spi/spi
All LXT PHYs implement the standard "power down" bit 11 of
BMCR, so this patch adds support using the generic
genphy_{suspend,resume} functions.
LXT970 is left aside because all registers get cleared upon
"power down" exit.
Fixes: 0f0ca340e57b ("phy: power management support")
Signed-off-by: Chri
On 5/22/19 2:09 AM, Paolo Valente wrote:
>
> First, thank you very much for testing my patches, and, above all, for
> sharing those huge traces!
>
> According to the your traces, the residual 20% lower throughput that you
> record is due to the fact that the BFQ injection mechanism takes a few
>
Correct sdma compatible since ecspi errata ERR009165 has been fixed
on i.mx6sll as i.mx6ul.
Signed-off-by: Robin Gong
---
arch/arm/boot/dts/imx6sll.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/imx6sll.dtsi b/arch/arm/boot/dts/imx6sll.dtsi
index 1b489
Enable SDMA support on i.mx8mq/8mm chips, including enabling
CONFIG_FW_LOADER_USER_HELPER/CONFIG_FW_LOADER_USER_HELPER_FALLBACK
for firmware loaded by udev.
Signed-off-by: Robin Gong
---
arch/arm64/configs/defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/configs/defcon
Because the number of ecspi1 rx event on i.mx8mm is 0, the condition
check ignore such special case without dma channel enabled, which caused
ecspi1 rx works failed. Actually, no need to check event_id0/event_id1
and replace checking 'event_id1' with 'DMA_DEV_TO_DEV', so that configure
event_id1 on
Add dma support on ecspi.
Signed-off-by: Robin Gong
---
arch/arm/boot/dts/imx6ul.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/imx6ul.dtsi b/arch/arm/boot/dts/imx6ul.dtsi
index bbf010c..880b9ee 100644
--- a/arch/arm/boot/dts/imx6ul.dtsi
+++ b/arch/arm/boot/dt
This adds support for printing stack frame description on invalid stack
accesses. The frame description is embedded by the compiler, which is
parsed and then pretty-printed.
Currently, we can only print the stack frame info for accesses to the
task's own stack, but not accesses to other tasks' sta
On 5/22/19 2:12 AM, Paolo Valente wrote:
>
>> Il giorno 22 mag 2019, alle ore 11:02, Srivatsa S. Bhat
>> ha scritto:
>>
>>
>> Let's continue here on LKML itself.
>
> Just done :)
>
>> The only reason I created the
>> bugzilla entry is to attach the tarball of the traces, assuming
>> that it wo
I've sent v3. If possible, please replace current version with v3,
which also includes the fix.
Many thanks,
-- Marco
On Wed, 22 May 2019 at 04:10, Andrew Morton wrote:
>
> On Sun, 19 May 2019 04:48:21 +0800 kbuild test robot wrote:
>
> > Hi Marco,
> >
> > Thank you for the patch! Perhaps some
Make function cpu_corepower_mask() static, as it is only referenced in
this file.
../arch/arm/kernel/topology.c:195:23: warning: no previous prototype for
‘cpu_corepower_mask’ [-Wmissing-prototypes]
const struct cpumask *cpu_corepower_mask(int cpu)
^~
Sign
On 21.05.2019 20:28, Jann Horn wrote:
> On Tue, May 21, 2019 at 7:04 PM Kirill Tkhai wrote:
>> On 21.05.2019 19:20, Jann Horn wrote:
>>> On Tue, May 21, 2019 at 5:52 PM Kirill Tkhai wrote:
On 21.05.2019 17:43, Andy Lutomirski wrote:
> On Mon, May 20, 2019 at 7:01 AM Kirill Tkhai wrote:
Hi Daniel,
On 5/21/19 4:23 PM, Daniel Vetter wrote:
> This is unused code since
>
> commit 6104c37094e729f3d4ce65797002112735d49cd1
> Author: Daniel Vetter
> Date: Tue Aug 1 17:32:07 2017 +0200
>
> fbcon: Make fbcon a built-time depency for fbdev
>
> when fbcon was made a compile-time
Commit 984203ceff27 ("net: stmmac: mdio: remove reset gpio free")
removed the reset gpio free, when the driver is unbinded or rmmod,
we miss the gpio free.
This patch uses managed API to request the reset gpio, so that the
gpio could be freed properly.
Signed-off-by: Jisheng Zhang
Fixes: 984203c
Move the reset gpio dt parse and request to stmmac_mdio_register(),
thus makes the mdio code straightforward.
This patch also replace stack var mdio_bus_data with data to simplify
the code.
Signed-off-by: Jisheng Zhang
---
.../net/ethernet/stmicro/stmmac/stmmac_mdio.c | 58 ---
Function sha512_arm_final() is only used in this file, therefore should
be static
../arch/arm/crypto/sha512-glue.c:40:5: warning: no previous prototype for
‘sha512_arm_final’ [-Wmissing-prototypes]
int sha512_arm_final(struct shash_desc *desc, u8 *out)
^~~~
Signed-off-by: Phili
On Wed, May 22, 2019 at 02:42:04PM +1000, Aleksa Sarai wrote:
> Prior to [1], all non-GPL modules were able to make use of SIMD on x86
> by making use of the __kernel_fpu_* API. Given that __kernel_fpu_* were
> both EXPORT_SYMBOL'd and kernel_fpu_* are such trivial wrappers around
> the now-static
Hi Robin,
Am Mittwoch, den 22.05.2019, 09:59 + schrieb Robin Gong:
> There is ecspi ERR009165 on i.mx6/7 soc family, which cause FIFO
> transfer to be send twice in DMA mode. Please get more information from:
> https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf. The workaround is adding
> new s
Hi,
On 22-05-19 06:54, Danct12 wrote:
On Chuwi Hi10 Plus, the Silead device id is MSSL0017.
Signed-off-by: Danct12
Patch looks good to me:
Reviewed-by: Hans de Goede
Regards,
Hans
---
drivers/input/touchscreen/silead.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/inp
On Tue, 21 May 2019, Joe Perches wrote:
> On Wed, 2019-05-22 at 13:32 +0900, Masahiro Yamada wrote:
> > (Perhaps, checkpatch.pl can suggest newer tags in case
> > patch submitters do not even know that deprecation.)
>
> I'd still prefer the kernel use of a single SPDX style.
>
> I don't know why
The rate_discrete needs to be assigned to clk->rate_discrete,
then scmi_clk_round_rate could get the value.
Fixes: 5f6c6430e904 ("firmware: arm_scmi: add initial support for clock
protocol")
Signed-off-by: Peng Fan
---
drivers/firmware/arm_scmi/clock.c | 2 ++
1 file changed, 2 insertions(+)
d
Reorder code a bit and then remove no longer needed function
prototypes.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/video/fbdev/pvr2fb.c | 141 ++-
1 file changed, 61 insertions(+), 80 deletions(-)
Index: b/drivers/video/fbdev/pvr2fb.c
Rename nr_activate{0,1} into nr_activate{anon,file} since this
is exported into userspace, e.g., it's shown here:
/sys/kernel/debug/tracing/events/vmscan/mm_vmscan_lru_shrink_inactive/format
v2: Changed suggested person (sorry, Mathieu :))
Suggested-by: Mathieu Desnoyers
Signed-off-by: Kirill T
From: Colin Ian King
The u8 variables ramp_ups and ramp_downs are being compared to less
than zero, this will always be false. Fix this by making the ramp
variables ints.
Addresses-Coverity: ("Unsigned compared against 0")
Fixes: 9a8e66ebeaa2 ("leds: TI LMU: Add common code for TI LMU devices")
On Wed, 22 May 2019 at 10:36, Theodore Ts'o wrote:
>
> On Tue, May 21, 2019 at 11:27:21PM +0530, Naresh Kamboju wrote:
> > Steps to reproduce is,
> > running LTP three test cases in sequence on x86 device.
> > # cd ltp/runtest
> > # cat syscalls ( only three test case)
> > open12 open12
> > madvis
On Wed, May 22, 2019 at 11:18:59AM +0200, Pavel Machek wrote:
> On Mon 2019-05-20 14:14:13, Greg Kroah-Hartman wrote:
> > From: Theodore Ts'o
> >
> > commit 345c0dbf3a30872d9b204db96b5857cd00808cae upstream.
> >
> > Add the blocks which belong to the journal inode to block_validity's
> > system
On Wed, May 22, 2019 at 11:15:07AM +0200, Pavel Machek wrote:
> On Mon 2019-05-20 14:13:44, Greg Kroah-Hartman wrote:
> > From: Jeremy Soller
> >
> > commit 80a5052db75131423b67f38b21958555d7d970e4 upstream.
> >
> > On the System76 Gazelle (gaze14), there is a headset microphone input
> > attach
On 20/05/19 21:01, Sean Christopherson wrote:
> Would it make sense to inject a #GP if the guest attempts to set bits that
> are reserved to be zero, e.g. based on guest CPUID?
Yes, though it was not clear from the SDM quote that hardware enforces
that (I guess the hint is that they "must" be writ
On Wed, May 22, 2019 at 10:15:56AM +0200, Jiri Slaby wrote:
> On 22. 05. 19, 10:06, Gen Zhang wrote:
> > On Wed, May 22, 2019 at 06:25:36AM +0200, Jiri Slaby wrote:
> >> On 22. 05. 19, 3:40, Gen Zhang wrote:
> >>> In alloc_tty_struct(), tty->dev is assigned by tty_get_device(). And it
> >>> calls c
On 22. 05. 19, 12:29, Johan Hovold wrote:
>> Sure, but can class_find_device return NULL in this tty case here?
>
> Yes, it can and will and that's fine, not all ttys have a struct device
> (e.g. ptys).
IOW, the code needs a comment, if anything.
thanks,
--
js
suse labs
On Tue, May 21, 2019 at 06:03:28PM +0200, Clément Péron wrote:
> Allwinner H6 has a second watchdog on the r-blocks which is
> compatible with the A31.
>
> This commit add the H6 compatible for the r_watchdog.
>
> Signed-off-by: Clément Péron
Unless you have some evidence that the two blocks are
Switch to using the CoreSight device instead of the real
amba device.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-catu.c | 13 +++--
drivers/hwtracing/coresight/coresight-catu.h | 1 -
2 files changed, 7 insertions(+), 7 deleti
In preparation to use a consistent device naming scheme,
clean up the device link tracking in funnel driver.
Use the "coresight" device instead of the "real" parent device
for all internal purposes. All other requests (e.g, power management,
DMA operations) must use the "real" device which is the p
Rename the firmware handling file to a more generic
name, in preparation for adding ACPI support. Right now
we only support DT and we have all the platform handling
code in of_coresight.c. Let us rename the file to
coresight-platform.c in order to keep the platform handling
in a single place for DT
All AMBA devices are handled via ACPI AMBA scan notifier
infrastructure. The platform devices get the ACPI id
added to their driver.
Cc: "Rafael J. Wysocki"
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/acpi/acpi_amba.c | 9 +
1 file changed, 9 insertions(+)
We match of_node while searching for a device. Make this
more generic in preparation for the ACPI support by using
fwnode_handle.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-platform.c | 16 +---
1 file changed, 9 insertions
Rename the of_coresight_alloc_memory() => coresight_alloc_conns()
as it is independent of the underlying firmware type. This is in
preparation for the ACPI support.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-platform.c | 34 +++
CPU field is only used by ETMs and there is a separate API
for fetching the same. So, let us use that instead of using
the common platform probing helper. Also, remove it from the
platform_data.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresig
When a device is unregistered, we remove all connection
references to it, by searching the connection records of
all devices in the coresight bus, via coresight_remove_conns.
We could avoid searching if this device doesn't have an input
port (e.g, a source). Also document the purpose of the functio
So far we have hard coded the DT platform parsing code in
every driver. Introduce generic helper to parse the information
provided by the firmware in a platform agnostic manner, in preparation
for the ACPI support.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtraci
This series adds the support for CoreSight devices on ACPI based
platforms. The device connections are encoded as _DSD graph property[0],
with CoreSight specific extensions to indicate the direction of data
flow as described in [1]. Components attached to CPUs are listed
as child devices of the cor
Switch to using the coresight device instead of the parent
amba device.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-tpiu.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/hwtracing/coresight/coresight-
In preparation to use a consistent device naming scheme,
clean up the device link tracking in replicator driver.
Use the "coresight" device instead of the "real" parent device
for all internal purposes. All other requests (e.g, power management,
DMA operations) must use the "real" device which is t
So far we have reused the name of the "platform" device for
the CoreSight device. But this is not very intuitive when
we move to ACPI. Also, the ACPI device names have ":" in them
(e.g, ARMHC97C:01), which the perf tool doesn't like very much.
This patch introduces a generic naming scheme, givin mo
We rely on the device names to find a CoreSight device on the
coresight bus. The device name however is obtained from the platform,
which is bound to the real platform/amba device. As we are about
to use different naming scheme for the coresight devices, we can't
rely on the platform device name to
Add support for parsing the ACPI platform description
for CoreSight. The connections are encoded in a DSD graph
property with CoreSight specific variation of the property.
The ETMs are listed as the children device of the respective
CPU.
Cc: "Rafael J. Wysocki"
Reviewed-by: Mathieu Poirier
Sign
ACPI bindings for CoreSight components on the Juno-r0 board.
Please note that the bindings apply only for the juno-r0.
The layout on r1 and r2 are slightly different and will need
dynamic ACPI table support to be able to use a single UEFI
image.
Signed-off-by: Suzuki K Poulose
---
Platform/ARM/J
Add support for platform devices which do not appear on the AMBA
bus.
Cc: "Rafael J. Wysocki"
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-replicator.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/driver
We are about to introduce methods to clean up the platform data
as we switch to tracking the device reference from "name" to "fwnode
handles" for device connections. This requires us to drop the fwnode
handle references when the data is no longer required - i.e, when
the device probe fails or the d
The stimulus base for STM device must be listed as the second memory
resource, followed by the programming base address as described in
"Section 2.3 Resources" in ACPI for CoreSightTM 1.0 Platform Design
documen (DEN0067).
Add support for parsing the information for ACPI.
Cc: "Rafael J. Wysocki"
Add a helper to clean up the platform specific data provided
by the firmware. This will be later used for dropping the necessary
references when we switch to the fwnode handles for tracking
connections.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight
As we are about to refactor the platform specific handling,
make the default buffer size probing generic.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-tmc.c | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
di
The platform specific information describes the connections and
the ports of a given coresigh device. This information is also
recorded in the coresight device as separate fields. Let us reuse
the original platform description to streamline the handling
of the data.
Reviewed-by: Mathieu Poirier
S
As we prepare to add support for ACPI bindings, let us make sure we do
the compatible check only if we are sure we are dealing with a DT based
system.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-funnel.c | 3 ++-
drivers/hwtracing/c
We are about to use a name independent of the parent AMBA device
name. As such, there is no need to have it in the platform description.
Let us move this to coresight description instead.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-catu
The CoreSight components ETM and CPU-Debug are always associated
with CPUs. Replace the of_coresight_get_cpu() with a platform
agnostic helper, in preparation to add ACPI support.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-cpu-debug.c
Track the coresight device instead of the real device.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etb10.c | 32 +--
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/hwtracing/coresight/cor
As we are about to refactor the platform specific handling
re-arrange some of the DT specific property handling.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-stm.c | 23 +++
1 file changed, 19 insertions(+), 4 deletio
From: Mathieu Poirier
Move to using the coresight device name instead of the parent
device name for SINK attribute for PMU.
Signed-off-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etm-perf.c | 8
1 file changed, 4 insertions(+), 4 dele
As we are about to refactor the platform specific handling,
move the DT property handling to generic helpers.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etm3x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/driver
Track the coresight device instead of the real device.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etm.h| 6 ++
.../hwtracing/coresight/coresight-etm3x-sysfs.c| 12 ++--
drivers/hwtracing/coresight/coresight-etm
Keep track of the STM coresight device which is a child device
of the AMBA device. Since we can get to the coresight_device
from the "device" instance, remove the explicit field.
Reviewed-by: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-stm.c | 21 ++
In preparation to use a consistent device naming scheme,
clean up the device link tracking in replicator driver.
Use the "coresight" device instead of the "real" parent device
for all internal purposes. All other requests (e.g, power management,
DMA operations) must use the "real" device which is t
On Tue, 21 May 2019, Benjamin Tissoires wrote:
> On Tue, May 21, 2019 at 3:38 PM Benjamin Tissoires
> wrote:
> >
> > Since kernel v5.0, one single win8 touchscreen device failed.
> > And it turns out this is because it reports 2 InRange usage per touch.
> >
> > It's a first, and I *really* wonder
The protocol is not allowing to obtain a byte of 0xff for PIO_ACCESS_READ
call. It is very likely that the slave was not addressed properly and
it is just not respoding (leaving the bus in logic high state) during
the read of sampled PIO value.
We cannot just call w1_reset_resume_command() because
Hi,
since a recent update the kernel is reporting d_lookup errors.
They appear randomly and after each error the affected file or directory
is no longer accessible.
The kernel is built with GCC 9.1.0 on ARM64.
Four traces from different workloads follow.
This trace is from v5.1-12511-g72cf0b07418
Hi Rob,
On Tue, May 21, 2019 at 04:23:24PM -0500, Rob Herring wrote:
> +allOf:
> + - $ref: "spi-controller.yaml#"
You're using a different construct on the spi-gpio binding you just
sent (/schemas/spi/spi-controller.yaml).
Is that on purpose?
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux an
Hello Alan,
On 21.05.2019 20:20, Alan Stern wrote:
> On Tue, 21 May 2019 laurentiu.tu...@nxp.com wrote:
>
>> From: Laurentiu Tudor
>>
>> For HCs that have local memory, replace the current DMA API usage
>> with a genalloc generic allocator to manage the mappings for these
>> devices. To help use
While parsing "memory-region" node lists if a node is
"disabled", parsing halts. Therefore the nodes whose
"status" is "okay" or "ok" are not parsed.
The change ignores disabled nodes in the memory-region
nodes list and returns 0 to continue parsing next nodes.
---
v2:
* Fixed typo in commit mess
From: Krishna Reddy
Ignore disabled nodes in the memory-region
nodes list and continue to initialize the rest
of enabled nodes.
Check if the "reserved-memory" node is available
and if it's not available, return 0 to ignore the
"reserved-memory" node and continue parsing with
next node in mem
Hi,
I'm not splitting this series in two after all. After thinking about
this for some time, I decided to add support for static software
nodes. I did not want to support them because I don't want to make it
easy to maintain board files, but in end they make the use of the
software nodes so much m
Software nodes are not forced to have device properties.
Adding check to property_entries_dup() to make it possible
to create software nodes that don't have any properties.
Signed-off-by: Heikki Krogerus
---
drivers/base/swnode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/bas
101 - 200 of 1311 matches
Mail list logo
