From: Stefan Wahren <wahrenst@gmx•net>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse•de>,
Rob Herring <robh+dt@kernel•org>,
Mark Rutland <mark.rutland@arm•com>,
Eric Anholt <eric@anholt•net>,
Florian Fainelli <f.fainelli@gmail•com>,
Ray Jui <rjui@broadcom•com>,
Scott Branden <sbranden@broadcom•com>,
Matthias Brugger <mbrugger@suse•com>,
Guillaume Gardet <Guillaume.Gardet@arm•com>,
Adrian Hunter <adrian.hunter@intel•com>
Cc: devicetree@vger•kernel.org,
bcm-kernel-feedback-list@broadcom•com,
linux-arm-kernel@lists•infradead.org,
Will Deacon <will@kernel•org>,
Catalin Marinas <catalin.marinas@arm•com>
Subject: Re: [PATCH V3 0/8] ARM: Add minimal Raspberry Pi 4 support
Date: Thu, 3 Oct 2019 19:24:55 +0200 [thread overview]
Message-ID: <d4774e5a-abc2-4c43-c97d-76600f74132d@gmx.net> (raw)
In-Reply-To: <3853cd8425743b4991f5d599ec1c0fbbf4232f95.camel@suse.de>
Hi Nicolas,
Am 03.10.19 um 19:09 schrieb Nicolas Saenz Julienne:
> On Sat, 2019-09-28 at 14:07 +0200, Stefan Wahren wrote:
>> This series adds minimal support for the new Raspberry Pi 4, so we are able
>> to login via debug UART.
>>
>> Patch 1-2: Fix some DT schema warnings
>> Patch 3-4: Prepare DTS for the new SoC BMC2711
>> Patch 5-7: Add Raspberry Pi 4 DTS support
>> Patch 8: Update MAINTAINERS
>>
>> Unfortunately the Raspberry Pi Foundation didn't released a
>> peripheral documentation for the new SoC yet. So we only have a preliminary
>> datasheet [1] and reduced schematics [2].
>>
>> Known issues:
>> Since Linux 5.3-rc1 DMA doesn't work properly on that platform.
>> Nicolas Saenz Julienne investigates on that issue. As a temporary workaround
>> i reverted the following patch to test this series:
>>
>> 79a98672 "dma-mapping: remove dma_max_pfn"
>> 7559d612 "mmc: core: let the dma map ops handle bouncing"
> [ adding Matthias and Guillaume who first saw this ]
> [ also adding Adrian Hunter just in case ]
>
> Hi,
> we stubled upon a bug in RPi's sdhci-iproc while testing this series.
>
> It only shows-up on slow SD cards, the class 4 ones. On each SD operation we
> get the following warning:
>
> [ 2.093328] mmc1: Got data interrupt 0x00000002 even though no data operation was in progress.
> [ 2.102072] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
> [ 2.108603] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
> [ 2.115134] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000000
> [ 2.121664] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000033
> [ 2.128195] mmc1: sdhci: Present: 0x1fff0000 | Host ctl: 0x00000017
> [ 2.134725] mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
> [ 2.141255] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000107
> [ 2.147785] mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
> [ 2.154314] mmc1: sdhci: Int enab: 0x03ff100b | Sig enab: 0x03ff100b
> [ 2.160843] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
> [ 2.167373] mmc1: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525
> [ 2.173902] mmc1: sdhci: Cmd: 0x00000c1a | Max curr: 0x00080008
> [ 2.180432] mmc1: sdhci: Resp[0]: 0x00000b00 | Resp[1]: 0x00edc87f
> [ 2.186961] mmc1: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x00400e00
> [ 2.193490] mmc1: sdhci: Host ctl2: 0x00000001
> [ 2.197992] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0xec040208
> [ 2.204521] mmc1: sdhci: ============================================
>
> Aside from the serial console noise the RPi still boots alright. But as it's
> printing one of these per SD operation which is a lot...
>
> I've been able to reproduce this both with arm and arn64 on multiple SD cards.
> Just copying the contents of a class 4 card into a class 10 one fixes the
> issue.
>
> Any ideas?
i saw this once during testing. AFAIR there has been some changes to
sdhci in the downstream tree, maybe they was related to this issue.
>
> Regards,
> Nicolas
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-03 17:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 12:07 [PATCH V3 0/8] ARM: Add minimal Raspberry Pi 4 support Stefan Wahren
2019-09-28 12:07 ` [PATCH V3 1/8] ARM: dts: bcm283x: Remove simple-bus from fixed clocks Stefan Wahren
2019-09-28 12:07 ` [PATCH V3 2/8] ARM: dts: bcm283x: Remove brcm, bcm2835-pl011 compatible Stefan Wahren
2019-09-28 12:07 ` [PATCH V3 3/8] ARM: dts: bcm283x: Move BCM2835/6/7 specific to bcm2835-common.dtsi Stefan Wahren
2019-09-28 12:07 ` [PATCH V3 4/8] dt-bindings: arm: Convert BCM2835 board/soc bindings to json-schema Stefan Wahren
2019-10-01 13:46 ` Rob Herring
2019-09-28 12:07 ` [PATCH V3 5/8] dt-bindings: arm: bcm2835: Add Raspberry Pi 4 to DT schema Stefan Wahren
2019-10-01 13:46 ` Rob Herring
2019-09-28 12:07 ` [PATCH V3 6/8] ARM: bcm: Add support for BCM2711 SoC Stefan Wahren
2019-09-28 19:16 ` Florian Fainelli
2019-09-28 23:09 ` Stefan Wahren
2019-09-30 8:21 ` Nicolas Saenz Julienne
2019-09-28 12:07 ` [PATCH V3 7/8] ARM: dts: Add minimal Raspberry Pi 4 support Stefan Wahren
2019-09-28 19:58 ` Florian Fainelli
2019-10-02 16:24 ` Stefan Wahren
2019-10-02 16:43 ` Florian Fainelli
2019-10-06 13:28 ` Stefan Wahren
2019-09-29 11:25 ` Marc Zyngier
2019-09-28 12:07 ` [PATCH V3 8/8] MAINTAINERS: Add BCM2711 to BCM2835 ARCH Stefan Wahren
2019-09-28 20:01 ` [PATCH V3 0/8] ARM: Add minimal Raspberry Pi 4 support Florian Fainelli
2019-10-03 17:09 ` Nicolas Saenz Julienne
2019-10-03 17:24 ` Stefan Wahren [this message]
2019-10-03 22:42 ` Matthias Brugger
2019-10-04 1:03 ` Stefan Wahren
2019-10-04 5:11 ` Matthias Brugger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4774e5a-abc2-4c43-c97d-76600f74132d@gmx.net \
--to=wahrenst@gmx$(echo .)net \
--cc=Guillaume.Gardet@arm$(echo .)com \
--cc=adrian.hunter@intel$(echo .)com \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=eric@anholt$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=mbrugger@suse$(echo .)com \
--cc=nsaenzjulienne@suse$(echo .)de \
--cc=rjui@broadcom$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
--cc=sbranden@broadcom$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox