From: petter@ka-long.de
To: mkl@pengutronix.de
Cc: linux-can@vger.kernel.org
Subject: Re: MCP2518FD : Failed to detect MCP2518FD (osc=0x00000000)
Date: Tue, 1 Feb 2022 10:08:08 +0100 (CET) [thread overview]
Message-ID: <20220201090808.ABBD45B0068C@dd15738.kasserver.com> (raw)
In-Reply-To: <20220131151735.mfxzloeppny62ow2@pengutronix.de>
Hi Folks,
Embarrassing ...
There was a small build of 5. There was an hw change afterwarts regardging CS. Reworked 4/5. I got the one without rework but special "local" working test software.
I wonder why switching to master is not working ...
Sorry for your time lapse.
BR
Niels
Marc Kleine-Budde schrieb am 31.01.2022 15:17 (GMT +00:00):
> On 31.01.2022 15:15:03, petter@ka-long.de wrote:
>>
>> Hi Marc,
>>
>> CS = High (de-asserted, slave not selected)
>> CS = low (asserted, slave selected)
>>
>> I also did not like the 0/1 starting point, but it is defined here:
>>
>> aliases {
>> gpio0 = &gpio1;
>> gpio1 = &gpio2;
>> gpio2 = &gpio3;
>> ...
>>
>>
>>
>> &gpio1 3 = gpiochip0 = 0*32 + 3 = gpio3
>> &gpio5 1 = gpiochip4 = 4*32 + 1 = gpio129
>
> In your output of /sys/kernel/debug/gpio, gpiochip3 starts at 128:
>
>>> gpiochip3: GPIOs 128-159, parent: platform/30240000.gpio, 30240000.gpio:
>>> gpio-128 ( |cd ) in hi IRQ ACTIVE LOW
>>> gpio-129 ( |spi1 CS0 ) out hi ACTIVE LOW
>
> Here it looks like this:
>
> gpiochip4: GPIOs 128-159, parent: platform/20ac000.gpio, 20ac000.gpio:
> gpio-130 (EIM_A25 |user1 ) out lo ACTIVE LOW
> gpio-133 (GPIO5_05 )
> gpio-134 (GPIO5_06 |reset ) out lo
> gpio-135 (GPIO5_07 )
> gpio-136 (GPIO5_08 )
> gpio-137 (CSPI2_CS1 |spi1 CS1 ) out hi ACTIVE LOW
> gpio-138 (CSPI2_MOSI )
> gpio-139 (CSPI2_MISO )
> gpio-140 (CSPI2_CS0 |spi1 CS0 ) out hi ACTIVE LOW
> gpio-141 (CSPI2_CLK )
>
>> Interresting with ACTIVE HIGH / LOW. cat debug/gpio tells me "ACTIVE
>> LOW" but anyway I did not see CS toggle at all. Also tested "1" but
>> nothing changed.
>>
>> By the way, the old kernel is working with the new device tree.
>>
>> I did a make clean and make sure that I really use latest build
>> artefacts. Everything is okay. Still failure.
>>
>> Maybe there are problems when using "make imx_v7_defconfig" ...
>> possible conflicts between drivers because there are much changes
>> between 5.4 and 5.10 whats enabled and/or new by default ? Try to go
>> with a very small kernel.
>
> There shouldn't be any conflicts between drivers.
>
> regards,
> Marc
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Embedded Linux | https://www.pengutronix.de |
> Vertretung West/Dortmund | Phone: +49-231-2826-924 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
prev parent reply other threads:[~2022-02-01 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 8:33 MCP2518FD : Failed to detect MCP2518FD (osc=0x00000000) petter
2022-01-31 8:42 ` Marc Kleine-Budde
2022-01-31 9:35 ` petter
2022-01-31 9:58 ` Marc Kleine-Budde
2022-01-31 12:44 ` petter
2022-01-31 13:09 ` Marc Kleine-Budde
2022-01-31 14:15 ` petter
2022-01-31 15:17 ` Marc Kleine-Budde
2022-02-01 9:08 ` petter [this message]
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=20220201090808.ABBD45B0068C@dd15738.kasserver.com \
--to=petter@ka-long.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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