Hi,
On Tue, May 3, 2022 at 7:14 PM Sai Prakash Ranjan
<quic_saipraka@xxxxxxxxxxx> wrote:
Hi,That's super weird. Any idea why my strongbad reports 407 then? Is it
On 5/3/2022 6:03 AM, Douglas Anderson wrote:
It appears the some sc7180 devices, like the one in myHmm, this ID maps to SM6250 which is a mobile variant. Not sure we should
sc7180-trogdor-homestar, report an ID of 407 instead of 425. Add
another ID into the list.
Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
---
drivers/soc/qcom/socinfo.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
index cee579a267a6..2ef1dc2a1dd3 100644
--- a/drivers/soc/qcom/socinfo.c
+++ b/drivers/soc/qcom/socinfo.c
@@ -318,6 +318,7 @@ static const struct soc_id soc_id[] = {
{ 396, "IPQ8071A" },
{ 402, "IPQ6018" },
{ 403, "IPQ6028" },
+ { 407, "SC7180" },
{ 421, "IPQ6000" },
{ 422, "IPQ6010" },
{ 425, "SC7180" },
use it for SC7180 which already has 425 ID assigned, perks of marketing :)
a firmware bug, or someone misprogrammed something? What can we do to
make the CPU recognized in strongbad?
...and just for extra info, I believe strongbad actually has the
slightly faster version of sc7180. It has a higher GPU/CPU speed. In
some places I've heard it called sc7185, but in other places I've
heard it called just sc7180 with a faster clock speed...