On Thu, Oct 22, 2015 at 09:51:30PM -0700, Florian Fainelli wrote:
> 2015-10-22 20:58 GMT-07:00 Tejun Heo <tj@xxxxxxxxxx>:
> I think we have a bit too many compatible strings defined, I need to
> lookup tomorrow when I am back in the office which BCM7xxx started
> featuring a SATA3 AHCI compliant core, it might be 7420, but I am not
> sure
I thought it was BCM7425, but you probably have the resources to check
better than I do.
There were also some small (probably mostly undocumented) bugfixes at
some point. I think the early cores actually had problems with the
upstream libahci. You might look at AHCI_HFLAG_DELAY_ENGINE for that, if
you care.
You might also notice that the "strict-ahci" stuff we were using got
dropped:
commit f1df8641e27b7edb978bdc7aaf50c235bc9e8be9
Author: Hans de Goede <hdegoede@xxxxxxxxxx>
Date: Sat Feb 22 17:22:53 2014 +0100
ahci_platform: Drop support for ahci-strict platform device type
But that's less relevant, now that there's a proper brcmstb driver.
Brian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
