On Mon, Dec 28, 2020 at 09:51:20PM +0800, Zheng Yongjun wrote:
> spinlock can be initialized automatically with DEFINE_SPINLOCK()
> rather than explicitly calling spin_lock_init().
>
> Signed-off-by: Zheng Yongjun
Applied to for-next, thanks!
signature.asc
Description: PGP signature
On Tue, Dec 22, 2020 at 09:31:31PM +0800, Zheng Yongjun wrote:
> Don't open-code DIV_ROUND_UP() kernel macro.
>
> Signed-off-by: Zheng Yongjun
Applied to for-next, thanks!
signature.asc
Description: PGP signature
nd SPI.
>
> Use enums to group all compatible devices together.
>
> Signed-off-by: Andre Przywara
Acked-by: Wolfram Sang # for I2C
signature.asc
Description: PGP signature
Hi Geert,
thank you for the reviews!
> breakout-board, while AVB1-5 are wired to 88Q2110 PHYs connected to a
> 5port MATEnet connector on the Ethernet sub board. So all PHYs are
> present?
I was under the assumption that we don't have the ethernet sub board in
the lab. Sorry if I was wrong.
> > I think that makes sense, and I'm okay with these patches going in as
> > they are now.
> >
> > Acked-by: Ray Jui
>
> Thank you.
Yes, thank you everyone.
All applied to for-next, thanks!
> --
> This electronic communication and the information and any files transmitted
> with it, or
> + geni_status = readl_relaxed(gi2c->se.base + SE_GENI_STATUS);
> + if (!(geni_status & M_GENI_CMD_ACTIVE))
> + goto out;
> +
> + cur = gi2c->cur;
> + geni_i2c_abort_xfer(gi2c);
> + if (cur->flags & I2C_M_RD)
> + geni_i2c_rx_msg_cleanup(gi2c, cur);
> +
On Mon, Dec 21, 2020 at 06:08:00PM +0530, Roja Rani Yarubandi wrote:
> Store DMA mapping data in geni_i2c_dev struct to enhance DMA mapping
> data scope. For example during shutdown callback to unmap DMA mapping,
> this stored DMA mapping data can be used to call geni_se_tx_dma_unprep
> and
On Fri, Nov 20, 2020 at 10:59:12AM -0800, Evan Green wrote:
> On Thu, Nov 19, 2020 at 7:24 AM Andy Shevchenko
> wrote:
> >
> > On Thu, Nov 19, 2020 at 1:40 AM Evan Green wrote:
> > >
> > > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> > > property translates directly to a
On Tue, Dec 15, 2020 at 10:33:27AM -0800, t...@redhat.com wrote:
> From: Tom Rix
>
> See Documentation/core-api/printk-formats.rst.
> h should no longer be used in the format specifier for printk.
>
> Signed-off-by: Tom Rix
Adding Jean to CC. Jean, I'd think %02x would be better, what do you
> Could you help me add:
> Fixes: 8426fe70cfa4("i2c: mediatek: Add apdma sync in i2c driver")
Thanks, added!
signature.asc
Description: PGP signature
> Jean, Wolfram, Benjamin, or someone else, could you please check Thomas'
> questions above and let us know what you think?
Sending this message here again because Bugzilla didn't know about the
mailing lists. Sorry for the noise!
===
Okay, here is some context about HostNotify. It is a
On Mon, Jan 04, 2021 at 07:29:59PM +0100, Wolfram Sang wrote:
> On Thu, Dec 24, 2020 at 08:26:07PM +0800, qii.w...@mediatek.com wrote:
> > From: Qii Wang
> >
> > With the apdma remove hand-shake signal, it requirs special
> > operation timing to reset i2c manual
On Thu, Dec 24, 2020 at 08:26:07PM +0800, qii.w...@mediatek.com wrote:
> From: Qii Wang
>
> With the apdma remove hand-shake signal, it requirs special
> operation timing to reset i2c manually, otherwise the interrupt
> will not be triggered, i2c transmission will be timeout.
>
> Signed-off-by:
On Mon, Dec 14, 2020 at 12:58:50PM +0800, Chunyan Zhang wrote:
> From: Chunyan Zhang
>
> If the i2c device SCL bus being pulled up due to some exception before
> message transfer done, the system cannot receive the completing interrupt
> signal any more, it would not exit waiting loop until
On Sun, Dec 27, 2020 at 02:04:06PM +0100, Wolfram Sang wrote:
> 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
I just pushed out another version of
_list()")
Signed-off-by: Wolfram Sang
Cc: Thomas Gleixner
Cc: Marc Zyngier
---
arch/arm/kernel/smp.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
index 5c48eb4fd0e5..74679240a9d8 100644
--- a/arch/arm/kernel/smp.c
+++ b/arch/arm/kernel/smp.c
t_cpu() in
arch_show_interrupts()")
Signed-off-by: Wolfram Sang
Cc: Thomas Gleixner
Cc: Marc Zyngier
---
arch/arm64/kernel/smp.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
index 6bc3a3698c3d..376343d6f13a 100644
--- a/arch/arm64/ke
SCIF0 has been enabled by the firmware, so it worked already. Still, add
the proper nodes to make it work in any case.
Signed-off-by: Wolfram Sang
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 25 +++
1 file changed, 25 insertions(+)
diff --git a/arch/arm64/boot/dts
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
b/drivers/clk/renesas/r8a779a0-cpg-mssr.c
index d85c31a465e1..f518c9e12a49 100644
--- a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
Mainly for testing the HSCIF0 node. We could make this switch permanent,
but we never did for any other SoC. So, I think this is not to be
applied.
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts | 14 +-
1 file changed, 9 insertions(+), 5 deletions
HSCIF support
Wolfram Sang (5):
arm64: dts: renesas: r8a779a0: add & update SCIF nodes
arm64: dts: renesas: falcon: add SCIF0 nodes
dt-bindings: serial: renesas,hscif: Add r8a779a0 support
clk: renesas: r8a779a0: add HSCIF support
WIP: arm64: dts: renesas: falcon: switch to from S
This is the result of multiple patches taken from the BSP, combined,
rebased, and properly sorted. SCIF0 gets DMA properties, other SCIFs are
entirely new.
Signed-off-by: Linh Phung
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 50 +++
1 file
From: Linh Phung
Define the generic parts of the HSCIF[0-3] device nodes.
Signed-off-by: Linh Phung
[wsa: double checked & rebased]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 64 +++
1 file changed, 64 insertions(+)
diff --git a/
Signed-off-by: Wolfram Sang
---
Documentation/devicetree/bindings/serial/renesas,hscif.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/serial/renesas,hscif.yaml
b/Documentation/devicetree/bindings/serial/renesas,hscif.yaml
index c139c5edb93e
On Sun, Dec 27, 2020 at 06:41:59PM +0100, Wolfram Sang wrote:
> From: Takeshi Saito
>
> Add a device node for MMC.
>
> Signed-off-by: Koji Matsuoka
> [wsa: double checked & rebased]
> Signed-off-by: Wolfram Sang
I just noticed that Saito-san's SoB is mis
Signed-off-by: Wolfram Sang
---
Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml
b/Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml
index 6bbf29b5c239..5908a717d2e8 100644
From: Takeshi Saito
Add a device node for MMC.
Signed-off-by: Koji Matsuoka
[wsa: double checked & rebased]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a779a0.dts
From: Takeshi Saito
Enable MMC on the Falcon board.
Signed-off-by: Koji Matsuoka
[wsa: double checked & rebased]
Signed-off-by: Wolfram Sang
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 41 +++
1 file changed, 41 insertions(+)
diff --git a/arch/arm64/boot/dts/ren
We want to reuse SD clock handling for other SoCs and, thus, need to
generalize it. So, don't access cpg_quirks in that realm.
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/rcar-gen3-cpg.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/clk
to comments. The branch is here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/v3u/sdhi
Happy hacking,
Wolfram
Takeshi Saito (2):
arm64: dts: renesas: r8a779a0: Add MMC node
arm64: dts: renesas: falcon: Enable MMC
Wolfram Sang (4):
dt-bindings: mmc: renesas,sdhi
We use the shiny new CPG library for that.
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/Kconfig | 1 +
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 17 +++--
2 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/renesas/Kconfig b/drivers/clk
-by: Wolfram Sang
---
drivers/clk/renesas/Kconfig | 4 +
drivers/clk/renesas/Makefile| 1 +
drivers/clk/renesas/rcar-cpg-lib.c | 270
drivers/clk/renesas/rcar-cpg-lib.h | 33
drivers/clk/renesas/rcar-gen3-cpg.c | 252 +-
5
the host
successfully. So, I think at least the first three patches are ready.
Let me know your thoughts!
All the best,
Wolfram
Tho Vu (2):
arm64: dts: renesas: r8a779a0: Add Ethernet-AVB support
arm64: dts: renesas: falcon: Add Ethernet-AVB support
Wolfram Sang (3):
dt-bindings: net
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
--- a/drivers/clk/renesas/r8a779a0-cpg
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 |
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 insertion
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
b/drivers/clk/renesas/r8a779a0-cpg-mssr.c
index bf9fdcdd7d85..989b83c26421 100644
--- a/drivers/clk/renesas/r8a779a0-cpg
Signed-off-by: Wolfram Sang
---
Documentation/devicetree/bindings/i2c/renesas,i2c.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/i2c/renesas,i2c.txt
b/Documentation/devicetree/bindings/i2c/renesas,i2c.txt
index 96d869ac3839..5762d2d1ab9c 100644
From: Koji Matsuoka
Signed-off-by: Koji Matsuoka
[wsa: rebased]
Signed-off-by: Wolfram Sang
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 28 +++
1 file changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
b/arch/arm64/boot/dts/renesas
Not for upstream!
Not-Signed-off-by: Wolfram Sang
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 65 +++
1 file changed, 65 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
b/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
index 7de3eed96ceb
From: Koji Matsuoka
Add I2C devicetree description to V3U
Signed-off-by: Koji Matsuoka
[wsa: rebased and double checked]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 122 ++
1 file changed, 122 insertions(+)
diff --git a/arch/arm64/boot/dts
: renesas: Add I2C support for falcon board
Wolfram Sang (3):
dt-bindings: i2c: renesas,i2c: add r8a779a0 (V3U) support
clk: renesas: r8a779a0: add clocks for I2C
v3u: enable other I2C busses for testing
.../devicetree/bindings/i2c/renesas,i2c.txt | 1 +
.../boot/dts/renesas/r8a779a0
> No interrupts property? ;-)
> As we don't have it described yet for the other R-Car Gen3 SoCs, I
> suggest we do that in one batch...
Yes, I'll try to find some time for this as a seperate series.
signature.asc
Description: PGP signature
> + reg = <0 0xe602 0 0x0c>;
I just understood that we sort by reg value and not by name. So, this
needs to be moved to another place then.
signature.asc
Description: PGP signature
I work on a system where I currently need to reboot via watchdog.
Because the watchdog needs a bit of time to fire, add a grace period
like on arm32 to avoid the false positive warning message.
Signed-off-by: Wolfram Sang
---
arch/arm64/kernel/process.c | 3 +++
1 file changed, 3 insertions
This comment was probably copied from arm32 and then shortened. It fits
to single line now.
Signed-off-by: Wolfram Sang
---
arch/arm64/kernel/process.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
index
Found these while working with a new prototype board.
Wolfram Sang (2):
arm64: add grace period when rebooting
arm64: proper comment formatting in reboot handler
arch/arm64/kernel/process.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.29.2
Other Gen3 SoCs do this in the bootloader. Maybe V3U will also later?
For now, add it so we can properly reboot via remote.
Not to be applied yet, just for demonstration.
Signed-off-by: Wolfram Sang
---
drivers/soc/renesas/rcar-rst.c | 8
1 file changed, 8 insertions(+)
diff --git
trees :)
Looking forward to comments.
Happy hacking and have a nice weekend!
Hoang Vo (2):
arm64: dts: renesas: r8a779a0: Add RWDT node
arm64: dts: renesas: falcon: Enable watchdog timer
Wolfram Sang (3):
dt-bindings: watchdog: renesas,wdt: add r8a779a0 (V3U) support
clk: renesas
And introduce critical clocks, too, because RWDT is one.
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
b/drivers/clk/renesas/r8a779a0-cpg-mssr.c
index aa5389b04d74
From: Hoang Vo
Enable the watchdog on the Falcon board.
Signed-off-by: Hoang Vo
[wsa: rebased to mainline]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
From: Hoang Vo
Add a device node for the Watchdog Timer (WDT) controller on the
R8A779A0 SoC.
Signed-off-by: Hoang Vo
[wsa: rebased to mainline]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch
Signed-off-by: Wolfram Sang
---
Please apply it to the watchdog-tree.
Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
b/Documentation/devicetree/bindings/watchdog
pty stub for runtime pm
Wolfram Sang (2):
Merge tag '20201013212531.428538-1-diand...@chromium.org' of
https://git.kernel.org/.../qcom/linux into i2c/for-5.11
Merge branch 'i2c/for-current' into i2c/for-5.11
Yash Shah (1):
dt-bindings: i2c: Update DT binding docs to supp
)
Diego Santa Cruz (1):
misc: eeprom: at24: fix NVMEM name with custom AT24 device name
Wolfram Sang (1):
Merge tag 'at24-fixes-for-v5.10' of git://git.kernel.org/.../brgl/linux
into i2c/for-current
drivers/misc/eeprom/at24.c | 1 -
1 file changed, 1
Hi,
thanks for your patch!
> If the i2c device SCL bus being pulled up due to some exception before
> message transfer done, the system cannot receive the completing interrupt
> signal any more, it would not exit waiting loop until MAX_SCHEDULE_TIMEOUT
> jiffies eclipse, that would make the
- unlikely(dma_mapping_error(dev, dma_addr))
> + dma_mapping_error(dev, dma_addr)
>
> Signed-off-by: Heiner Kallweit
Acked-by: Wolfram Sang # for I2C
signature.asc
Description: PGP signature
___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
- unlikely(dma_mapping_error(dev, dma_addr))
> + dma_mapping_error(dev, dma_addr)
>
> Signed-off-by: Heiner Kallweit
Acked-by: Wolfram Sang # for I2C
signature.asc
Description: PGP signature
- unlikely(dma_mapping_error(dev, dma_addr))
> + dma_mapping_error(dev, dma_addr)
>
> Signed-off-by: Heiner Kallweit
Acked-by: Wolfram Sang # for I2C
signature.asc
Description: PGP signature
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
On Sun, Oct 04, 2020 at 01:07:11PM +0300, Codrin Ciubotariu wrote:
> Starting with
> commit 75820314de26 ("i2c: core: add generic I2C GPIO recovery")
> GPIO bus recovery is supported by the I2C core, so we can remove the
> driver implementation and use that one instead.
>
> Signed-off-by: Codrin
On Sat, Nov 28, 2020 at 01:05:16PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:56:07AM +0200, Cristian Ciocaltea wrote:
> > Add I2C controller nodes for Actions Semi S500 SoC.
> >
> > Signed-off-by: Cristian Ciocaltea
>
> Reviewed-by: Manivannan Sadhasivam
DTS changes
On Fri, Nov 20, 2020 at 01:56:06AM +0200, Cristian Ciocaltea wrote:
> Add S500 variant to the list of devices supported by the Actions Semi
> Owl I2C driver.
>
> Signed-off-by: Cristian Ciocaltea
Applied to for-next, thanks!
signature.asc
Description: PGP signature
On Fri, Nov 20, 2020 at 01:56:04AM +0200, Cristian Ciocaltea wrote:
> Convert the Actions Semi Owl I2C DT binding to a YAML schema for
> enabling DT validation.
>
> Additionally, add a new compatible string corresponding to the I2C
> controller found in the S500 variant of the Actions Semi Owl
On Fri, Nov 20, 2020 at 01:56:05AM +0200, Cristian Ciocaltea wrote:
> The Actions Semi Owl I2C DT binding has been converted to YAML schema,
> therefore update accordingly the entry in MAINTAINERS.
>
> Signed-off-by: Cristian Ciocaltea
Squashed with 10/18 and applied to for-next, thanks!
On Wed, Dec 09, 2020 at 09:03:50AM -0800, Kevin Herbert wrote:
> What is the protocol for the I2C_SLAVE_STOP event? I am working on my own
> backend, and I've only tried it with this i.mx driver, and I do not receive
> I2C_SLAVE_STOP at the end of every I2C transaction. It was my expectation
> I'd
Linus,
here are some more I2C driver updates. IMX updates are a tad bigger, but
not exceptionally big.
Please pull.
Thanks,
Wolfram
The following changes since commit b65054597872ce3aefbc6a666385eabdf9e288da:
Linux 5.10-rc6 (2020-11-29 15:50:50 -0800)
are available in the Git
On Thu, Dec 03, 2020 at 11:32:50PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> If this is not enabled, the interfaces used in this driver do not work:
>
> drivers/i2c/busses/i2c-mlxbf.c:1888:3: error: implicit declaration of
> function 'i2c_slave_event'
On Tue, Nov 24, 2020 at 12:57:43PM -0600, Bjorn Andersson wrote:
> A combination of recent bug fixes by Doug Anderson and the proper
> definition of iommu streams means that this hack is no longer needed.
> Let's clean up the code by reverting '127068abe85b ("i2c: qcom-geni:
> Disable DMA
On Tue, Nov 24, 2020 at 12:57:43PM -0600, Bjorn Andersson wrote:
> A combination of recent bug fixes by Doug Anderson and the proper
> definition of iommu streams means that this hack is no longer needed.
> Let's clean up the code by reverting '127068abe85b ("i2c: qcom-geni:
> Disable DMA
> With Doug's recent fixes in the DMA handling and the introduction of
> proper iommu configuration, which Caleb tested [1], I think we're good
> without this on the OnePlus. Caleb, please confirm.
Yes, he confirmed already. I missed it was private only.
Thanks for your heads up, too!
On Tue, Nov 24, 2020 at 09:08:35PM +0800, Youling Tang wrote:
> 'pci_set_dma_mask()' + 'pci_set_consistent_dma_mask()' can be replaced by
> an equivalent 'dma_set_mask_and_coherent()' which is much less verbose.
>
> Signed-off-by: Youling Tang
Please use "i2c: ismt:", so driver maintainers know
On Mon, Nov 16, 2020 at 10:10:58PM +0800, Zhihao Cheng wrote:
> Fix to return the error code from qup_i2c_change_state()
> instaed of 0 in qup_i2c_bam_schedule_desc().
>
> Fixes: fbf9921f8b35d9b2 ("i2c: qup: Fix error handling")
> Reported-by: Hulk Robot
> Signed-off-by: Zhihao Cheng
Applied
> >> - if (!of_machine_is_compatible("lenovo,yoga-c630"))
> >> + if (!of_machine_is_compatible("lenovo,yoga-c630") &&
> >> + !of_machine_is_compatible("oneplus,oneplus6"))
> > This hack seems to have been working around two separate issues. First
> > with iommu active the GENI wrappers
Hi,
> Some i2c device driver indirectly uses I2C driver when it is now
> being suspended. The i2c devices driver is suspended during the
> NOIRQ phase and this cannot be changed due to other dependencies.
> Therefore, we also need to move the suspend handling for the I2C
> controller driver to
On Sat, Nov 07, 2020 at 01:51:51PM +0530, Vaibhav Gupta wrote:
> After the commit c5eb1190074c ("PCI / PM: Allow runtime PM without callback
> functions") we no more need empty stubs for runtime-pm to work.
>
> The driver has no device specific task(s) for .suspend() . The stub was
> placed just
> So, applied to for-next, thanks!
I am very sorry. Due to my mistake, this patch got lost. I reapplied it
now. Sorry again!
signature.asc
Description: PGP signature
On Wed, Nov 11, 2020 at 07:32:55PM +0800, Biwen Li wrote:
> From: Biwen Li
>
> The patch supports slave mode for imx I2C driver
>
> Signed-off-by: Biwen Li
Applied to for-next, thanks!
signature.asc
Description: PGP signature
> > Applied to for-next, thanks!
> >
> I cannot find my patches in kernel/git/wsa/linux.git, branch "for-next".
> Did they get lost?
It seems like it :( I seem to have forgotten to push out and then
continued to to work on another computer with an older state. It is
highly embarassing but I
> All review comments are scattered now, please let me know what has to be
> done further,
> Are we going to change the tasklet to irq thread ?
> Are we going to remove batching 64 packets if transaction > 64B and use rx
> fifo threshold ?
>
> I don't see any issue with current code but if it
er is cast from pointer
>
> Reported-by: kernel test robot
> Reported-by: Dan Carpenter
> Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Wolfram Sang
signature.asc
Description: PGP signature
Linus,
here are driver bugfixes for I2C. Most of them are for the new mlxbf
driver which got more exposure after rc1. The sh_mobile patch should
already have reached you during the merge window, but I accidently
dropped it. However, since it fixes a problem with rebooting, I think it
is still
On Sat, Oct 10, 2020 at 01:19:42PM +0200, Wolfram Sang wrote:
> On Mon, Oct 05, 2020 at 02:49:49PM +0200, Geert Uytterhoeven wrote:
> > The Mellanox BlueField I2C controller is only present on Mellanox
> > BlueField SoCs. Hence add a dependency on MELLANOX_PLATFORM, to prevent
>
> Not exactly. There're an interrupt state name "RD_REQ" but no one named
> like "WR_REQ".
>
> For read-request, the slave will get a RD_REQ interrupt.
> For write-request, the slave won't be interrupted until data arrived to
> trigger interrupt "RX_FULL".
>
> I tried to use GPIO to simulate
On Fri, Oct 09, 2020 at 12:44:41AM +0300, Cristian Ciocaltea wrote:
> Speed up the boot process by using the asynchronous probing feature
> supported by the recent kernels.
>
> For SBCs based on the Actions Semi S500 SoC, the overall boot time is
> expected to be reduced by 200-300 ms.
>
>
On Fri, Oct 09, 2020 at 12:44:40AM +0300, Cristian Ciocaltea wrote:
> Atomic transfers are required to properly power off a machine through
> an I2C controlled PMIC, such as the Actions Semi ATC260x series.
>
> System shutdown may happen with interrupts being disabled and, as a
> consequence, the
On Wed, Oct 21, 2020 at 07:50:14AM -0700, Sagar Shrikant Kadam wrote:
> The FU540-C000 has a broken IRQ and support was added earlier
> so that it will operate in polling mode, but seems to work only
> in case interrupts property is missing from the i2c0 dt-node.
> This should not be the case and
On Fri, Oct 30, 2020 at 07:58:01PM +0800, qii.w...@mediatek.com wrote:
> From: Qii Wang
>
> The i2c driver default do dma reset after i2c reset, but sometimes
> i2c reset will trigger dma tx2rx, then apdma write data to dram
> which has been i2c_put_dma_safe_msg_buf(kfree). Move dma reset
>
Hi Michael,
> Documentation/i2c/slave-interface.rst says that I2C_SLAVE_WRITE_REQUESTED,
> which is mandatory, should be sent while the data did not arrive yet. It
> means in a write-request I2C_SLAVE_WRITE_REQUESTED should be reported
> before any I2C_SLAVE_WRITE_RECEIVED.
Correct.
>
On Wed, Sep 30, 2020 at 04:56:54PM +0200, Alexandre Belloni wrote:
> Commit dc6df6e90de9 ("i2c: at91: remove legacy DMA support") removed legcy
> DMA support from the driver. Remove the last use of the definitions from
> linux/platform_data/dma-atmel.h and stop including this header.
>
>
> Sounds good, please find the series applied on top of v5.10-rc1 at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git
> tags/20201013212531.428538-1-diand...@chromium.org
Thanks, pulled.
signature.asc
Description: PGP signature
> Wolfram, would you like to pick this patch or would you prefer that it
> goes together with the other two through the soc tree?
Actually, I prefer the soc tree because of the functional dependency. I
am not aware of any pending qcom-geni patches, yet I think an immutable
branch for me to pull
Linus,
I2C has a regression fix which should go into rc1 and to stable kernels
as well.
Please pull.
Thanks,
Wolfram
The following changes since commit d76913908102044f14381df865bb74df17a538cb:
Merge tag 'block-5.10-2020-10-24' of git://git.kernel.dk/linux-block
(2020-10-24 12:46:42
alsa-de...@alsa-project.org
> Cc: linux-...@vger.kernel.org
> Cc: linux-...@lists.infradead.org
> Cc: linux-ser...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> Signed-off-by: Rob Herring
Acked-by: Wolfram Sang # for I2C
signature.asc
Description: PGP signature
__
alsa-de...@alsa-project.org
> Cc: linux-...@vger.kernel.org
> Cc: linux-...@lists.infradead.org
> Cc: linux-ser...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> Signed-off-by: Rob Herring
Acked-by: Wolfram Sang # for I2C
signature.asc
Description: PGP signature
o (1):
i2c: Switch to using the new API kobj_to_dev()
Tom Rix (1):
i2c: amd_mp2: handle num is 0 input for i2c_amd_xfer
Vadym Kochan (1):
eeprom: at24: set type id as EEPROM
Wang ShaoBo (1):
i2c: efm32: Use devm_platform_get_and_ioremap_resource()
Wolfram Sang (9):
i2c: a
> Fixes: a8335c64c5f0 ("i2c: add slave testunit driver")
> Signed-off-by: Mauro Carvalho Chehab
As discussed with v1, I already fixed it (correctly). Patch is in
linux-next:
On Fri, Oct 09, 2020 at 01:03:19PM +0200, Christian Eggers wrote:
> Arbitration Lost (IAL) can happen after every single byte transfer. If
> arbitration is lost, the I2C hardware will autonomously switch from
> master mode to slave. If a transfer is not aborted in this state,
> consecutive
> Changes in v5:
Changes in v6 were missing... Because patch 1 was updated, I reverted it
from for-current and will apply this series to for-next instead to give
it some more time for testing.
signature.asc
Description: PGP signature
501 - 600 of 16180 matches
Mail list logo
