[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKmtTBbsXgWuT__kkPneRKpveUO24pJqFn+aAa9-3n11Pu0PwQ@mail.gmail.com>
Date: Tue, 14 Nov 2023 12:06:28 +0100
From: Mathieu Moneyron <mathieu.moneyron@...il.com>
To: Aubin Constans <aubin.constans@...rochip.com>
Cc: Adrian Hunter <adrian.hunter@...el.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Eugen Hristev <eugen.hristev@...labora.com>,
Ludovic Desroches <ludovic.desroches@...rochip.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
linux-mmc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mmc: Fix force card detect in sdhci
On Fri, Nov 10, 2023 at 8:57 PM Aubin Constans
<aubin.constans@...rochip.com> wrote:
>
> On 23/09/2023 16:23, Mathieu Moneyron wrote:
>
> In the device tree, has PIN_PA13__SDMMC0_CD been removed from the
> pinctrl for sdmmc0?
Yes the pin is not present in the pinctrl. Only PA0 to PA10 configured as
SDMMC0 function.
>
> In case the above behaviour was due to hardware, it would likely point
> out a flaw in the Parallel Input/Output Controller (PIO) rather than in
> the SDMMC Controller.
>
> Would you read back the relevant PIO_CFGRx register, with only "PA13"
> set in PIO_MSKRx, and provide me with the value read?
> Assuming PA13 is Non-Secure; if PA13 is configured as Secure,
> S_PIO_CFGRx and S_PIO_MSKRx should be accessed instead.
I'm not sure if that's the best way to achieve this but I enabled debug
messages in pinctrl-at91-pio4 driver.
The messages I got regarding the PA13 pin is the following:
'enable pin 13 as GPIO'
With PIO_CFGR0 register for PA13 only is 0x0400.
Also from PA0 to PA10 the pins used for the in the mmc pinctrl:
'enable function A group PA0'
For all these pins funcion A is SDMMC0.
Also as a side note, I will no longer have access to the hardware from the
beginning of december as I have resigned from my current job.
Best regards,
Mathieu
Powered by blists - more mailing lists