* Paul E. McKenney wrote:
> --- a/include/linux/rcupdate.h
> +++ b/include/linux/rcupdate.h
> @@ -383,20 +383,22 @@ do {
> \
> } while (0)
>
> /**
> - * rcu_swap_protected() - swap an RCU and a regular pointer
> - * @
On 10/16/2019 8:53 PM, Jiri Olsa wrote:
On Wed, Oct 16, 2019 at 06:51:07PM +0800, Jin, Yao wrote:
On 10/16/2019 6:15 PM, Jiri Olsa wrote:
On Tue, Oct 15, 2019 at 10:53:18PM +0800, Jin, Yao wrote:
SNIP
+static struct block_header_column{
+ const char *name;
+ int width;
+} bl
From: Maulik Shah
Add sc7180 pdc irqchip
Signed-off-by: Maulik Shah
Signed-off-by: Rajendra Nayak
Cc: Lina Iyer
Cc: Marc Zyngier
---
v2: No change
drivers/irqchip/qcom-pdc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/irqchip/qcom-pdc.c b/drivers/irqchip/qcom-pdc.c
index fa
Add the compatible string for sc7180 SoC from Qualcomm.
Signed-off-by: Rajendra Nayak
Cc: Lina Iyer
Cc: Marc Zyngier
---
v2: No change
.../devicetree/bindings/interrupt-controller/qcom,pdc.txt| 1 +
1 file changed, 1 insertion(+)
diff --git
a/Documentation/devicetree/bindings/interr
From: Maulik Shah
Add pdc interrupt controller for sc7180
Signed-off-by: Maulik Shah
Signed-off-by: Rajendra Nayak
Cc: Lina Iyer
Cc: Marc Zyngier
---
v2: No change
arch/arm64/boot/dts/qcom/sc7180.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/
From: Kiran Gunda
Add the rpmh regulators for the sc7180 idp platform. This platform
consists of PMIC PM6150 and PM6150l
Signed-off-by: Kiran Gunda
Signed-off-by: Rajendra Nayak
---
v2: Moved the contents of sc7180-regulators.dtsi into sc7180-idp.dts
arch/arm64/boot/dts/qcom/sc7180-idp.dts |
Add skeletal sc7180 SoC dtsi and idp board dts files.
Co-developed-by: Taniya Das
Signed-off-by: Taniya Das
Signed-off-by: Rajendra Nayak
---
v2:
* Sorted the nodes in alphabetical order
* Dropped the bi_tcxo/bi_tcxo_ao nodes
arch/arm64/boot/dts/qcom/Makefile | 1 +
arch/arm64/boot/dt
Add a SoC string 'sc7180' for the qualcomm SC7180 SoC.
Also add a new board type 'idp'
Signed-off-by: Rajendra Nayak
Reviewed-by: Vinod Koul
---
v2: Added Vinod's Reviewed-by:
Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/de
Add the soc specific compatible for sc7180 smmu-500
Signed-off-by: Rajendra Nayak
Cc: Joerg Roedel
Cc: Mark Rutland
---
v2: No change
Documentation/devicetree/bindings/iommu/arm,smmu.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.txt
This is a collection of a few floating DT patches, and a few new
ones, adding support for basic peripherals on qualcomm's sc7180 SoC,
drivers for which are already upstream.
I have marked all as v2 to be consistent.
Each patch captures the delta if any from v1:
All the dts files have a dependency
From: Kiran Gunda
Add PM6150/PM6150L peripherals such as PON, GPIOs, ADC and other
PMIC infra modules.
Signed-off-by: Kiran Gunda
Signed-off-by: Rajendra Nayak
---
v2:
* Changed to BSD-3-Clause licence
* Included headers in sc7180-idp.dts
arch/arm64/boot/dts/qcom/pm6150.dtsi| 85
From: Taniya Das
Add node for rpmhcc clock driver.
Signed-off-by: Taniya Das
Signed-off-by: Rajendra Nayak
---
v2: No change
arch/arm64/boot/dts/qcom/sc7180.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi
b/arch/arm64/boot/dts/qcom/
From: Maulik Shah
Command_db provides mapping for resource key and address managed
by remote processor. Add cmd_db reserved memory area.
Signed-off-by: Maulik Shah
Signed-off-by: Rajendra Nayak
---
v2: No change
arch/arm64/boot/dts/qcom/sc7180.dtsi | 12
1 file changed, 12 inser
From: Kiran Gunda
Add SPMI PMIC arbiter device to communicate with PMICs
attached to SPMI bus.
Signed-off-by: Kiran Gunda
Signed-off-by: Rajendra Nayak
---
v2: No change
arch/arm64/boot/dts/qcom/sc7180.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm64/b
From: Maulik Shah
Add device bindings for the application processor's rsc. The rsc
contains the TCS that are used for communicating with the hardened
resource accelerators on Qualcomm Technologies, Inc. (QTI) SoCs.
Signed-off-by: Maulik Shah
Signed-off-by: Rajendra Nayak
---
v2: No change
ar
From: Vivek Gautam
Adding device node for APPS SMMU that is connected to
devices such as display, video, usb, mmc, etc. on SC7180
chipset.
Signed-off-by: Vivek Gautam
Signed-off-by: Rajendra Nayak
---
v2: No change
arch/arm64/boot/dts/qcom/sc7180.dtsi | 88
1 fil
> btw2:
>
> I really dislike all the code inconsistencies and
> unnecessary code duplication with miscellaneous changes
> in the rtl staging drivers
>
> Horrid stuff.
I'm not sure what you mean by "miscellaneous changes". Do you mean that
all issues should be fixed for one file before moving
On Sun, Oct 20, 2019 at 11:47 PM Alexander Sverdlin
wrote:
> On 20/10/2019 13:49, Arnd Bergmann wrote:
> >>> Ah, that makes sense. so all interrupt numbers need to
> >>> be shifted by a fixed number (e.g. 1) like we did for
> >>> other platforms (see attachment).
> >> Yes, the below patch resolved
On Sun, Oct 20, 2019 at 05:22:30PM +, Anatol Belski wrote:
> From: Anatol Belski
Better to add commit message even for small patches like this.
Do you have compiler / sparse / etc warning? Cite it here as well!
--
With Best Regards,
Andy Shevchenko
Below is the list of build error/warning regressions/improvements in
v5.4-rc4[1] compared to v5.3[2].
Summarized:
- build errors: +10/-3
- build warnings: +142/-119
JFYI, when comparing v5.4-rc4[1] to v5.4-rc3[3], the summaries are:
- build errors: +0/-1
- build warnings: +93/-59
Note th
Hi all,
Changes since 20191018:
New tree: realtek (resurrected)
Removed trees: actions, btrfs, hdlcd, kgdb, pcmcia, siox
(not updated for more than a year)
Renamed trees: btrfs-kdave to btrfs
kgdb-dt to kgdb
The net-next tree gained a conflict against Linus' tree.
* Linus Torvalds wrote:
> What you doing the merge does is to turn the multiple merge bases into
> just one point: the thing you merged against now becomes the common
> merge point, and now you have a "two endpoints" for the diffstat: the
> thing you merged against, and your end result are now
Add MAINTAINERS entry for RDA Micro GPIO driver and devicetree binding.
Signed-off-by: Manivannan Sadhasivam
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a69e6db80c79..0303502cd146 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2150,9 +215
Add YAML devicetree binding for RDA Micro GPIO controller.
Signed-off-by: Manivannan Sadhasivam
---
.../devicetree/bindings/gpio/gpio-rda.yaml| 50 +++
1 file changed, 50 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-rda.yaml
diff --git a/Docu
Add GPIO controllers for RDA8810PL SoC. There are 4 GPIO controllers
in this SoC with maximum of 32 gpios. Except GPIOC, all controllers
are capable of generating edge/level interrupts from first 8 lines.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/boot/dts/rda8810pl.dtsi | 48
Add support for GPIO controller from RDA Micro. This GPIO controller
is an in house IP, developed by RDA Micro (now Unisoc) for the use in
RDA88* series of SoCs. There are multiple GPIO ports present in all SoCs,
each capable of addressing 32 GPIOs. But only first 8 pins have the
interrupt capabili
Hello,
This patchset adds GPIO controller support for RDA Micro RDA8810PL
SoC. This SoC has 4 GPIO controllers and each handles 32 GPIOs. Except
GPIOC, all controllers are capable of generating edge/level interrupts
from first 8 GPIO lines. The pinctrl part for this SoC will be added
later.
This
Intel PCIe is synopsys based controller utilizes the Designware
framework for host initialization and intel application
specific register configurations.
Changes on v4:
Add lane resizing API in PCIe DesignWare driver.
Intel PCIe driver uses it for lane resizing which
is be
PCIe RC driver on Intel Gateway SoCs have a requirement
of changing link width and speed on the fly.
So add the sysfs attributes to show and store the link
properties.
Add the respective link resize function in pcie DesignWare
framework so that Intel PCIe driver can use during link
width configurat
Add YAML shcemas for PCIe RC controller on Intel Gateway SoCs
which is Synopsys DesignWare based PCIe core.
changes on v4:
Add "snps,dw-pcie" compatible.
Rename phy-names property value to pcie.
And maximum and minimum values to num-lanes.
Add ref for reset-assert-m
Add support to PCIe RC controller on Intel Gateway SoCs.
PCIe controller is based of Synopsys DesignWare pci core.
Intel PCIe driver requires Upconfig support, fast training
sequence configuration and link speed change. So adding the
respective helper functions in the pcie DesignWare framework.
It
Hi Ingo,
On Mon, 21 Oct 2019 07:51:41 +0200 Ingo Molnar wrote:
>
> Hm, that was a weird merge mishap - sorry about that, should go away in
> the next -next iteration.
Thanks.
--
Cheers,
Stephen Rothwell
pgp3bI3wEmsAy.pgp
Description: OpenPGP digital signature
Jiri Olsa writes:
> Jan reported failing ltp test for pt. It looks like the reason
> is commit 38bb8d77d0b9, that did not keep the TOPA_SHIFT for
> entry base, adding it back.
Thanks for taking care of that so quickly!
Regards,
--
Alex
+ Bala
On 2019-10-18 23:52, Matthias Kaehlcke wrote:
On Thu, Oct 17, 2019 at 10:24:02PM -0700, Bjorn Andersson wrote:
Devices with specific voltage requirements should not request voltage
from the driver, but instead rely on the system configuration to
define
appropriate voltages for each rai
Providing tcm_get_alt in tcm function to support Bulk only protocol and
USB Attached SCSI protocol
Signed-off-by: Jayshri Pawar
---
drivers/usb/gadget/function/f_tcm.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/f_tcm.c
b/drivers
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 7cb3a2445705e45af9b58dd241d26598a35b1fdd
Gitweb:
https://git.kernel.org/tip/7cb3a2445705e45af9b58dd241d26598a35b1fdd
Author:Arnaldo Carvalho de Melo
AuthorDate:Tue, 15 Oct 2019 12:30:08 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 7a12f514c408cc499e61211f234858d3d4b7f4ea
Gitweb:
https://git.kernel.org/tip/7a12f514c408cc499e61211f234858d3d4b7f4ea
Author:Arnaldo Carvalho de Melo
AuthorDate:Tue, 15 Oct 2019 12:22:37 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 6a6fac11b11299aa5bd8532ea863fc2f652af2b6
Gitweb:
https://git.kernel.org/tip/6a6fac11b11299aa5bd8532ea863fc2f652af2b6
Author:Thomas Richter
AuthorDate:Tue, 08 Oct 2019 11:38:41 +02:00
Commit
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 6080728ff8e9c9116e52e6f840152356ac2fea56
Gitweb:
https://git.kernel.org/tip/6080728ff8e9c9116e52e6f840152356ac2fea56
Author:Yunfeng Ye
AuthorDate:Tue, 15 Oct 2019 16:30:08 +08:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 98a8b2e60c69927b1f405c3b001a1de3f4e53901
Gitweb:
https://git.kernel.org/tip/98a8b2e60c69927b1f405c3b001a1de3f4e53901
Author:Andi Kleen
AuthorDate:Fri, 11 Oct 2019 11:21:40 -07:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: f948eb45e3af9fb18a0487d0797a773897ef6929
Gitweb:
https://git.kernel.org/tip/f948eb45e3af9fb18a0487d0797a773897ef6929
Author:Gustavo A. R. Silva
AuthorDate:Mon, 14 Oct 2019 12:10:47 -05:00
C
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 8daf1fb73295b43fb2f624f709449b484532ba64
Gitweb:
https://git.kernel.org/tip/8daf1fb73295b43fb2f624f709449b484532ba64
Author:Arnaldo Carvalho de Melo
AuthorDate:Tue, 15 Oct 2019 12:35:02 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: ae199c580da1754a2b051321eeb76d6dacd8707b
Gitweb:
https://git.kernel.org/tip/ae199c580da1754a2b051321eeb76d6dacd8707b
Author:Yunfeng Ye
AuthorDate:Tue, 15 Oct 2019 10:54:14 +08:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 5eca1379c0eb06e3908179665230a86d19bd2df7
Gitweb:
https://git.kernel.org/tip/5eca1379c0eb06e3908179665230a86d19bd2df7
Author:Arnaldo Carvalho de Melo
AuthorDate:Tue, 15 Oct 2019 12:44:00 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 1abecfcaa7bba21c9985e0136fa49836164dd8fd
Gitweb:
https://git.kernel.org/tip/1abecfcaa7bba21c9985e0136fa49836164dd8fd
Author:Yunfeng Ye
AuthorDate:Wed, 16 Oct 2019 16:38:45 +08:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 5a0baf5123236362fda4e9772cc63b7faa16a0df
Gitweb:
https://git.kernel.org/tip/5a0baf5123236362fda4e9772cc63b7faa16a0df
Author:Adrian Hunter
AuthorDate:Mon, 07 Oct 2019 10:02:21 +03:00
Committ
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo/Thomas,
>
> Please consider pulling,
>
> Best regards,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 4f5cafb5cb8471e54afdc9054d973535614f7675:
>
> Linux 5.4-rc3 (2019-10-13 16
On Fri, 18 Oct 2019 at 18:11, Sami Tolvanen wrote:
>
> This allows CONFIG_KRETPROBES to be disabled without disabling
> kprobes entirely.
>
> Signed-off-by: Sami Tolvanen
Can we make kretprobes work with the shadow call stack instead?
> ---
> arch/arm64/kernel/probes/kprobes.c | 2 ++
> 1 file
On Fri, 18 Oct 2019 at 18:11, Sami Tolvanen wrote:
>
> If we detect a corrupted x18 and SCS is enabled, restore the register
> before jumping back to instrumented code.
>
You'll have to elaborate a bit here and explain that this is
sufficient, given that we run EFI runtime services with interrupt
On Fri, 18 Oct 2019 at 18:10, Sami Tolvanen wrote:
>
> From: Ard Biesheuvel
>
> In preparation of using x18 as a task struct pointer register when
> running in the kernel, stop treating it as caller save in the KVM
> guest entry/exit code. Currently, the code assumes there is no need
> to preserv
Hi Linus,
On Mon, Oct 21, 2019 at 02:57:31AM +0200, Linus Walleij wrote:
> On Sat, Oct 19, 2019 at 6:05 PM Manivannan Sadhasivam
> wrote:
> > On Wed, Oct 16, 2019 at 02:41:32PM +0200, Linus Walleij wrote:
>
> > > select GPIO_GENERIC
> >
> > hmm.. I don't think this driver can use it. Please see
Hi Peter,
On 14-Oct 16:52, Peter Zijlstra wrote:
>
> The energy aware schedutil patches remimded me this was still pending.
>
> On Fri, Aug 02, 2019 at 10:47:25AM +0100, Patrick Bellasi wrote:
> > Hi Peter, Vincent,
> > is there anything different I can do on this?
>
> I think both Vincent and
On Fri, 18 Oct 2019 at 18:11, Sami Tolvanen wrote:
>
> With CONFIG_FUNCTION_GRAPH_TRACER, function return addresses are
> modified in ftrace_graph_caller and prepare_ftrace_return to redirect
> control flow to ftrace_return_to_handler. This is incompatible with
> return address protection.
>
> Sig
Hi Linus,
On Wed, Oct 16, 2019 at 02:27:44PM +0200, Linus Walleij wrote:
> On Tue, Oct 15, 2019 at 7:30 PM Manivannan Sadhasivam
> wrote:
>
> > Add YAML devicetree binding for RDA Micro GPIO controller.
> >
> > Signed-off-by: Manivannan Sadhasivam
>
> First: this looks awesome to me,
>
> Seco
On Fri, 18 Oct 2019 at 21:00, Sami Tolvanen wrote:
>
> On Fri, Oct 18, 2019 at 10:32 AM 'Nick Desaulniers' via Clang Built
> Linux wrote:
> > > and remove the mention from
> > > the LL/SC compiler flag override.
> >
> > was that cut/dropped from this patch?
> >
> > >
> > > Link: https://patchwork
On 18. 10. 19, 18:17, Sudip Mukherjee wrote:
> The build of xtensa allmodconfig gives warning of:
> In function 'get_ports.isra.0':
> warning: the frame size of 1040 bytes is larger than 1024 bytes
>
> Signed-off-by: Sudip Mukherjee
Acked-by: Jiri Slaby
Thanks.
> v2: check faliure of kzalloc
On 2019/10/18 下午10:20, Cornelia Huck wrote:
On Thu, 17 Oct 2019 18:48:35 +0800
Jason Wang wrote:
This patch introduces a new mdev transport for virtio. This is used to
use kernel virtio driver to drive the mediated device that is capable
of populating virtqueue directly.
A new virtio-mdev d
From: Nan Li
In MMC dma transfer, the region requested by dma_map_sg() may be released
by dma_unmap_sg() before the transfer is completed.
Put the unmap operation in front of mmc_request_done() to avoid this.
Signed-off-by: Nan Li
Signed-off-by: Jianxin Pan
---
drivers/mmc/host/meson-gx-mmc.
For kernel logging macro, pr_warning is completely removed and
replaced by pr_warn, using pr_warn in tools lib bpf for symmetry
to kernel logging macro, then we could drop pr_warning in the
whole linux code.
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Martin KaFai Lau
Cc: Song Liu
Cc: Yongh
To avoid doc rot, put function documentations with code, not header.
Use kernel-doc style comments for exported functions.
Signed-off-by: Gwendal Grignou
---
New in v2.
drivers/platform/chrome/cros_ec.c | 33 +++
drivers/platform/chrome/cros_ec_proto.c | 70 +
in
This reverts commit 62c3801619e16b68a37ea899b76572145dfe41c9.
This patch is not needed anymore since we clear EC_MKBP_HAS_MORE_EVENTS
flag before calling the notifiers in patch
"9d9518f5b52a (platform: chrome: cros_ec: handle MKBP more events flag)"
Signed-off-by: Gwendal Grignou
---
New to v2.
From: Enrico Granata
Add a layer of sanity checking to cros_ec_register against attempting to
register IRQ values that are not strictly greater than 0.
Signed-off-by: Enrico Granata
Signed-off-by: Gwendal Grignou
---
Changes in v2:
Remove dual Enrico's signature.
drivers/platform/chrome/cr
Expose EC minimal interrupt period through buffer/hwfifo_timeout:
- Maximal timeout is limited to 65s.
- When timeout for all sensors is set to 0, EC will not send events,
even if the sensor sampling rate is greater than 0.
- curr_sample_rate is no more, the pm functions have been removed.
Renam
To be compliant with other sensors, set and get sensor sampling
frequency in Hz, not mHz.
Fixes: ae7b02ad2f32 ("iio: common: cros_ec_sensors: Expose
cros_ec_sensors frequency range via iio sysfs")
Signed-off-by: Gwendal Grignou
---
No changes in v2.
.../cros_ec_sensors/cros_ec_sensors_core.c
- Remove duplicate code in mfd, since mfd just register
cros_ec_sensorhub if at least one sensor is present
- Change iio cros_ec driver to get the pointer to the cros_ec_dev
through cros_ec_sensorhub.
Signed-off-by: Gwendal Grignou
---
Changes in v2:
- Remove unerelated changes.
- Remove ec p
Events are timestamped in EC time space, their timestamps need to be
converted in host time space.
The assumption is the time delta between when the interrupt is sent
by the EC and when it is receive by the host is a [small] constant.
This is not always true, even with hard-wired interrupt. To miti
Report the maximum amount of sample the EC can hold.
This is not tunable, but can be useful for application to find out the
maximum amount of time it can sleep when hwfifo_timeout is set to a
large number.
Signed-off-by: Gwendal Grignou
---
Changes in v2:
- Remove double lines, add line before re
This reverts commit d096aa3eb6045a6a475a0239f3471c59eedf3d61.
This patch is not needed anymore since we clear EC_MKBP_HAS_MORE_EVENTS
flag before calling the notifiers in patch
"9d9518f5b52a (platform: chrome: cros_ec: handle MKBP more events flag)"
Signed-off-by: Gwendal Grignou
---
New to v2.
Similar to HID sensor stack, the new driver sits between cros_ec_dev
and the iio device drivers:
EC based iio device topology would be:
iio:device1 ->
...0/:00:1f.0/PNP0C09:00/GOOG0004:00/cros-ec-dev.6.auto/
cros-ec-sensorhub.7.auto/
To prevent comment rot, move function description to
cros_ec_sensors_core.c.
Signed-off-by: Gwendal Grignou
---
New in v2.
.../cros_ec_sensors/cros_ec_sensors_core.c| 69
.../linux/iio/common/cros_ec_sensors_core.h | 80 ---
2 files changed, 69 insertions(
Since cros_ec_sensorhub is shutting down the FIFO when the device
suspends, no need to slow down the EC sampling period rate.
It was necesseary to do that before command CMD_FIFO_INT_ENABLE was
introduced, but now all supported chromebooks have it.
Signed-off-by: Gwendal Grignou
---
New in v2.
EC FIFO can send sensor events in batch. Spread them based on
previous (TSa) and currnet timestamp (TSb)
EC FIFO iio events
+---+
| TSa |
+---+ +---+
| event 1 | | event 1 | TSb - (TSb
From: Enrico Granata
The ChromeOS EC has support for signaling to the host that
a single IRQ can serve multiple MKBP (Matrix KeyBoard Protocol)
events.
Doing this serves an optimization purpose, as it minimizes the
number of round-trips into the interrupt handling machinery, and
it proves benefi
cros_ec_sensorhub registers a listener and query motion sense FIFO,
spread to iio sensors registers.
To test, we can use libiio:
iiod&
iio_readdev -u ip:localhost -T 1 -s 25 -b 16 cros-ec-gyro | od -x
Signed-off-by: Gwendal Grignou
---
Changes sunce v2:
- Do not register a .remove routinge i
When EC supports FIFO, each IIO device registers a callback, to put
samples in the buffer when they arrives from the FIFO.
We can still use a trigger to collect samples, but there may be some
duplications in the buffer: EC has a single FIFO, so once one sensor is
using it, all sensors event will be
Add a new function to return the number of MEMS sensors available in a
ChromeOS Embedded Controller.
It uses MOTIONSENSE_CMD_DUMP if available or a specific memory map ACPI
registers to find out.
Also, make check_features public as it can be useful for other drivers
to know what the Embedded Contr
To improve sensor timestamp precision, given EC and AP are in
different time domains, the AP needs to try to record the exact
moment an event was signalled to the AP by the EC as soon as
possible after it happens.
First thing in the hard irq is the best place for this.
Signed-off-by: Gwendal Grig
This patchset adds a sensorhub driver for spreading sensor
events coming from the Embedded controller sensor FIFO:
+---+ +--+ +
| cros_ec_accel | | cros_ec_gyro | | ...
+---+ +--+ +
id:0 \id:1 |
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (native perf)
> failed like this:
>
> make: execvp: ./check-headers.sh: Permission denied
>
> Caused by commit
>
> 05f2f277053d ("Merge branch 'x86/core'")
>
> which somehow removed execute permi
Hello Alexandre,
On Thu, 2019-10-17 at 12:48 +0200, Alexandre Belloni wrote:
> On 17/10/2019 10:36:44+, Vaittinen, Matti wrote:
> > Hello Alexandre,
> >
> > Thanks for quick check! I'll be off for the rest of the week but I
> > will
> > re-work this patch at next week :) I agree with you rega
In the variant rc5t619 the mfd has a rtc. This patchset adds
support for it. To do so it adds the missing register defines in
rn5t618.h and general irq handling for that.
Probably the irq definitions are the same except missing rtc + charger
but due to missing information about that I do not add t
Add an RTC driver for the RTC device on Ricoh MFD rc5t619,
which is implemented as a variant of rn5t618
Signed-off-by: Andreas Kemnade
---
drivers/rtc/Kconfig | 10 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-rc5t619.c | 476 ++
3 files
The rc5t619 has a rtc which are missing in the
rn5t618. Add it as subdevice to prepare for their implementation
Signed-off-by: Andreas Kemnade
---
drivers/mfd/rn5t618-core.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/rn5t618-core.c b/drivers/mfd/
rn5t618 currently lacks irq handling. To prepare implementation
in a rn5t618-irq.c, move main file to rn5t618-core.c
Signed-off-by: Andreas Kemnade
---
drivers/mfd/Makefile | 2 ++
drivers/mfd/{rn5t618.c => rn5t618-core.c} | 0
2 files changed, 2 insertions(+)
rename driver
Defines for some rtc related registers were missing, also
they were not included in the volatile register list
Signed-off-by: Andreas Kemnade
---
drivers/mfd/rn5t618-core.c | 2 ++
include/linux/mfd/rn5t618.h | 11 +++
2 files changed, 13 insertions(+)
diff --git a/drivers/mfd/rn5t618
This adds support for irq handling in the rc5t619 which is required
for properly implementing subdevices like rtc.
For now only definitions for the variant rc5t619 are included.
Signed-off-by: Andreas Kemnade
---
drivers/mfd/Kconfig | 1 +
drivers/mfd/Makefile| 2 +-
drivers/mf
changes v3:
- ag71xx: ag71xx_mac_config: ignore MLO_AN_INBAND mode. It is not
supported by HW and SW.
- ag71xx: ag71xx_mac_validate: return all supported bits on
PHY_INTERFACE_MODE_NA
changes v2:
- move Atheros AR9331 TAG format to separate patch
- use netdev_warn_once in the tag driver to red
Add support for tag format used in Atheros AR9331 build-in switch.
Signed-off-by: Oleksij Rempel
---
include/net/dsa.h| 2 +
net/dsa/Kconfig | 6 +++
net/dsa/Makefile | 1 +
net/dsa/tag_ar9331.c | 97
4 files changed, 106 insertions(+)
The port to phylink was done as close as possible to initial
functionality.
Theoretically this HW can support flow control, practically seems to be not
enough to just enable it. So, more work should be done.
Signed-off-by: Oleksij Rempel
---
drivers/net/ethernet/atheros/Kconfig | 2 +-
driver
Add switch node supported by dsa ar9331 driver.
Signed-off-by: Oleksij Rempel
---
arch/mips/boot/dts/qca/ar9331.dtsi | 127 ++-
arch/mips/boot/dts/qca/ar9331_dpt_module.dts | 13 ++
2 files changed, 139 insertions(+), 1 deletion(-)
diff --git a/arch/mips/boot/dts/qca/
Provide basic support for Atheros AR9331 build-in switch. So far it
works as port multiplexer without any hardware offloading support.
Signed-off-by: Oleksij Rempel
---
drivers/net/dsa/Kconfig | 2 +
drivers/net/dsa/Makefile | 1 +
drivers/net/dsa/qca/Kconfig | 11 +
drivers/net/d
Atheros AR9331 has built-in 5 port switch. The switch can be configured
to use all 5 or 4 ports. One of built-in PHYs can be used by first built-in
ethernet controller or to be used directly by the switch over second ethernet
controller.
Signed-off-by: Oleksij Rempel
---
.../devicetree/bindings/
On 20-10-19, 20:56, Bjorn Andersson wrote:
> Enable the driver for the watchdog found in the application processor
> subsystem on most modern Qualcomm platforms.
Reviewed-by: Vinod Koul
With this and the node patch, I was able to test wdt on db845c:
Tested-by: Vinod Koul
>
> Signed-off-by:
Do some cleanup of the netback init and deinit code:
- add an omnipotent queue deinit function usable from
xenvif_disconnect_data() and the error path of xenvif_connect_data()
- only install the irq handlers after initializing all relevant items
(especially the kthreads related to the queue)
-
On 21.10.19 07:27, Juergen Gross wrote:
Do some cleanup of the netback init and deinit code:
- add an omnipotent queue deinit function usable from
xenvif_disconnect_data() and the error path of xenvif_connect_data()
- only install the irq handlers after initializing all relevant items
(esp
Do some cleanup of the netback init and deinit code:
- add an omnipotent queue deinit function usable from
xenvif_disconnect_data() and the error path of xenvif_connect_data()
- only install the irq handlers after initializing all relevant items
(especially the kthreads related to the queue)
-
Hello,
syzbot found the following crash on:
HEAD commit:eda57a0e Merge branch 'akpm' (patches from Andrew)
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17310520e0
kernel config: https://syzkaller.appspot.com/x/.config?x=966954bb171a60e7
dashboard li
Hello,
syzbot found the following crash on:
HEAD commit:64c5e530 Merge tag 'arc-4.19-rc8' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17add28540
kernel config: https://syzkaller.appspot.com/x/.config?x=88e9a8a39dc0be2d
da
Hello,
syzbot found the following crash on:
HEAD commit:b145b0eb Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13887f1f60
kernel config: https://syzkaller.appspot.com/x/.config?x=1ec3be9936e004f6
da
The USB id pins and wlan regulator are not platform devices, so move
them out of /soc
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 58 ++--
1 file changed, 29 insertions(+), 29 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c
1 - 100 of 335 matches
Mail list logo
