Re: [PATCHv9 00/12] PCI: Recode Mobiveil driver and add PCIe Gen4 driver for NXP Layerscape SoCs
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Date: 2020-02-10 17:21:14
Also in:
linux-devicetree, linux-pci, lkml
On Mon, Feb 10, 2020 at 04:15:53PM +0000, Russell King - ARM Linux admin wrote:
On Mon, Feb 10, 2020 at 04:28:23PM +0100, Olof Johansson wrote:quoted
On Mon, Feb 10, 2020 at 4:23 PM Russell King - ARM Linux admin [off-list ref] wrote:quoted
On Mon, Feb 10, 2020 at 04:12:30PM +0100, Olof Johansson wrote:quoted
On Thu, Feb 6, 2020 at 11:57 AM Z.q. Hou [off-list ref] wrote:quoted
Hi Olof, Thanks a lot for your comments! And sorry for my delay respond!Actually, they apply with only minor conflicts on top of current -next. Bjorn, any chance we can get you to pick these up pretty soon? They enable full use of a promising ARM developer system, the SolidRun HoneyComb, and would be quite valuable for me and others to be able to use with mainline or -next without any additional patches applied -- which this patchset achieves. I know there are pending revisions based on feedback. I'll leave it up to you and others to determine if that can be done with incremental patches on top, or if it should be fixed before the initial patchset is applied. But all in all, it's holding up adaption by me and surely others of a very interesting platform -- I'm looking to replace my aging MacchiatoBin with one of these and would need PCIe/NVMe to work before I do.If you're going to be using NVMe, make sure you use a power-fail safe version; I've already had one instance where ext4 failed to mount because of a corrupted journal using an XPG SX8200 after the Honeycomb Serror'd, and then I powered it down after a few hours before later booting it back up. EXT4-fs (nvme0n1p2): INFO: recovery required on readonly filesystem EXT4-fs (nvme0n1p2): write access will be enabled during recovery JBD2: journal transaction 80849 on nvme0n1p2-8 is corrupt. EXT4-fs (nvme0n1p2): error loading journalHmm, using btrfs on mine, not sure if the exposure is similar or not.As I understand the problem, it isn't a filesystem issue. It's a data integrity issue with the NVMe over power fail, how they cache the data, and ultimately write it to the nand flash. Have a read of: https://www.kingston.com/en/solutions/servers-data-centers/ssd-power-loss-protection
This was the link I was actually looking for: http://industrial.adata.com/en/technology/92 but there's also: http://industrial.adata.com/en/technology/26 ADATA make the XPG SX8200: NVME Identify Controller: vid : 0x1cc1 ssvid : 0x1cc1 mn : ADATA SX8200PNP fr : R0906I -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel