dt-bindings: synopsys-dw-mshc-common: add "fifo-access-32bit" property
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Sergey Lisov
Quoted 6 lines
Anyway, I said last time this looks compatible-specific, so I don't think we need another property.
Best regards,
KrzysztofI agree, but I'm afraid of introducing regressions by enabling this workaround on systems that don't actually need it.
I don't understand why would you enable it for systems which do not need it?
Best regards,
Krzysztof
Quoted 5 lines · Sergey Lisov
Quoted 4 lines
Quoted 4 lines
Anyway, I said last time this looks compatible-specific, so I don't think we need another property.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Best regards,
KrzysztofI agree, but I'm afraid of introducing regressions by enabling this workaround on systems that don't actually need it.
I don't understand why would you enable it for systems which do not need it?
OK, then how do I find out which boards have the bug? My only idea is "search for samsung,exynos7-dw-mshc through all devicetrees, find vendor kernels for each of those boards, and check if they have the workaround". Is it really that better than enabling it selectively only for known-affected boards?
Quoted 5 lines · Sergey Lisov
Quoted 4 lines
Quoted 4 lines
Anyway, I said last time this looks compatible-specific, so I don't think we need another property.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Best regards,
KrzysztofI agree, but I'm afraid of introducing regressions by enabling this workaround on systems that don't actually need it.
I don't understand why would you enable it for systems which do not need it?
OK, then how do I find out which boards have the bug? My only idea is "search for samsung,exynos7-dw-mshc through all devicetrees, find vendor kernels for each of those boards, and check if they have the workaround". Is it really that better than enabling it selectively only for known-affected boards?
Quoted 5 lines · Sergey Lisov
Quoted 4 lines
Quoted 4 lines
Anyway, I said last time this looks compatible-specific, so I don't think we need another property.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Best regards,
KrzysztofI agree, but I'm afraid of introducing regressions by enabling this workaround on systems that don't actually need it.
I don't understand why would you enable it for systems which do not need it?
OK, then how do I find out which boards have the bug? My only idea is "search for samsung,exynos7-dw-mshc through all devicetrees, find vendor kernels for each of those boards, and check if they have the workaround". Is it really that better than enabling it selectively only for known-affected boards?