Date: Tue, 19 May 2020 17:45:07 +0000 From: greg@unrelenting.technology To: "Marcin Wojtas" <mw@semihalf.com> Cc: "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <d502d4e13727bdde1e6e755a0ccea951@unrelenting.technology> In-Reply-To: <CAPv3WKdyOzegfK4NJjKzXQTp9jGV9VkDRWxY%2BhDudzWQKkRfEQ@mail.gmail.com> References: <CAPv3WKdyOzegfK4NJjKzXQTp9jGV9VkDRWxY%2BhDudzWQKkRfEQ@mail.gmail.com> <TLwmTbuqZXh21TMiFjCu96O2fOIoWgPXE-0amhQa7y66As1E39i0v-nC7j1saPpCy8KrT63uE_W92527rywGhtxTKVATtYBSLfrLRdZ3faA=@a9development.com> <cjE8j_Tehwtmk7Aw0hzP-EZxwfAQC4ywIrgcqrarkCiRI_X5kacVsJHpaX_SMO9QHVCqfEdJH45eC4AE2cwzfx9nmHzWbhE7M-h09hDe8MA=@a9development.com> <7F9D7164-2C04-4E27-85F9-A495EAC8FC84@unrelenting.technology> <63b4f78ff4ee07359a345bcbc03afeaa@unrelenting.technology> <2053cd2299b81860deecc638ef839d1f@unrelenting.technology> <0012917d629a48e9fcd8589f4f002e1b@unrelenting.technology> <947c2f9bfaad823a2b104b8741502b40@unrelenting.technology> <c88780825e96fe583b32adf86416706e@unrelenting.technology> <d709b1aae3d33f49fadcce9817cb102a@unrelenting.technology> <LqTdXCGMiTFwSobCq9LtV5QVLOZ42AiBDUTC9UrdM67cUlD_I8Y7no-8F7d_vs3VDJwIFJLgHTSZVrbkIXXeZ_-hcU0FxfWj0dr-GvhKXHA=@a9development.com> <b04385d558850dc1dfa60fc398c9ac6c@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
May 19, 2020 7:57 PM, "Marcin Wojtas" <mw@semihalf.com> wrote:=0A=0A> wt.= , 19 maj 2020 o 18:42 <greg@unrelenting.technology> napisa=C5=82(a):=0A> = =0A>> May 19, 2020 7:11 PM, "Dan Kotowski" <dan.kotowski@a9development.co= m> wrote:=0A>> =0A>> Getting closer...=0A>> dmesg.boot: https://gist.gith= ub.com/agrajag9/99d26385be0f49a8a4f046f15a2c0f08=0A>> =0A>> "iicbus0: <un= known card> at addr 0x77" nice!=0A>> Would be great if you could run `i2c= -s` also.=0A>> =0A>> Scanning I2C devices on /dev/iic0: 01 02 03 04 05 0= 6 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 [..]=0A>> =0A>> Hey look at t= hat! A bunch of numbers! Hopefully they mean more to you than they do to = me...=0A>> =0A>> hmm, it shouldn't report all numbers as present. oh well= .=0A>> =0A>> sdhci_acpi0-slot0 seems to have hung the boot process for al= most 5min waiting for various timeouts.=0A>> =0A>> oops, so they didn't r= eally make generic sdhci work :D=0A>> =0A>> Well turns out we do have a F= reescale ESDHC driver already.=0A>> It doesn't have DMA so performance wo= n't be great (but SD/MMC is bad stuff anyway lol).=0A>> (interesting dev = note: NetBSD gets away with just some quirks in the sdhci acpi driver:=0A= >> SDHC_FLAG_HAVE_DVS|SDHC_FLAG_NO_PWR0|SDHC_FLAG_32BIT_ACCESS|SDHC_FLAG_= ENHANCED)=0A>> =0A>> No worries - once I can get a reliable install, I ho= pe to never need to touch those again anyways.=0A>> I mostly am hoping to= get eMMC so I can flash updated firmware, assuming the errata list is co= rrect=0A>> and my silicon rev CAN boot from firmware on eMMC and it was a= layer 8 failure.=0A>> =0A>> Trying to add ACPI support to it:=0A>> =0A>>= https://send.firefox.com/download/926c72b043182c40/#49y3TaeL7_hif_YEHUFQ= 2g=0A>> =0A>> Latest dmesg.boot: https://gist.github.com/agrajag9/f4e8186= e4cea7da1e5d8887a8d74dd7a=0A>> =0A>> "mmcsd0: 32GB <SDHC SB32G 8.0 SN DD1= 242F8 MFG 09/2017 by 3 SD> at mmc0 43.7MHz/4bit/65535-block"=0A>> is bett= er than before, but controller timeouts are sad. Welp.=0A>> =0A>> If anyo= ne is interested in debugging this (with the device in hand), my ACPI att= achment patch is:=0A>> https://github.com/myfreeweb/freebsd/commit/4abb60= 611c53b6bf109e8854f60ecc697419cf1c=0A>> =0A>> Once again, maybe NetBSD's = way of supporting this (slight quirks in the generic ACPI SDHCI driver)= =0A>> would be better than fsl_sdhci.=0A> =0A> Do you have a knowledge if= LS2KX controller is common with the one=0A> found in LS1046? If that may= help, we are going to upstream it (need=0A> some rework after rebasing f= rom 11.x).=0A=0AFrom a quick look at Linux, should be very similar.=0ALX2= 160 uses just "fsl,esdhc" which is handled by the same driver as "fsl,ls1= 046a-esdhc"=0Abut w/o any specific clock data.=0A=0Ahttps://github.com/to= rvalds/linux/blob/master/drivers/mmc/host/sdhci-of-esdhc.c=0Ahttps://gith= ub.com/SolidRun/edk2-platforms/blob/eec706c2d693be0b3793d9180e7d1a4813a52= 6cf/Silicon/NXP/LX2160A/Include/DeviceTreeInclude/fsl-lx2160a.dtsi#L364-L= 387=0A=0AThe changes you're going to upstream, are they for fsl_sdhci or = generic sdhci?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d502d4e13727bdde1e6e755a0ccea951>