From: Andre Przywara <andre.przywara@arm.com>
To: project-tvbox project-tvbox <project-tvbox@prp.uespi.br>
Cc: u-boot@lists.denx.de, linux-sunxi <linux-sunxi@lists.linux.dev>
Subject: Re: error on h616 ID axp806 legacy kernel
Date: Sat, 21 Oct 2023 01:02:21 +0100 [thread overview]
Message-ID: <20231021010221.3ac96652@slackpad.lan> (raw)
In-Reply-To: <CAC15VHSqtbfP-4YZYJ71CDXryJT2s-vXF9Kj=kNT4yCEAHmC=A@mail.gmail.com>
On Thu, 5 Oct 2023 17:37:48 -0300
project-tvbox project-tvbox <project-tvbox@prp.uespi.br> wrote:
Hi,
> In the legacy kernel, when starting, the error appears:
> the chip id is 0x5d00
> ic cant match axp, please check...
Please keep in mind that the BSP code contains a lot of nonsense, the
PMIC setup seems to be particularly problematic, with dramatic error
messages even when everything is fine. So is there any actual problem
with your box?
And I don't know what "chip id" here refers to, but it's surely not the
AXP ID from I2C register 0x3, since that is only 8 bits wide.
That number looks more like from the first part of the SID, which is
also used in the DVFS code to discern certain dies or SoC revisions.
In any case, are you sure that your device actually has a PMIC? It is
not unheard of for TV boxes to drop that chip (many H6 TV boxes did), as
fine grained power management might not be too useful in a TV box.
Cheers,
Andre
P.S. Please try to add some Allwinner specific lists (see the CC: here),
or the #linux-sunxi IRC channel to get quicker responses.
> well, in the axp.h code the id is defined as 0x40, I tried changing it
> to 0x5d00, but it does not accept the u-boot compilation error, does
> anyone know how to change it, it seems to be an error in the number of
> registers available in the .h
prev parent reply other threads:[~2023-10-21 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 20:37 error on h616 ID axp806 legacy kernel project-tvbox project-tvbox
2023-10-21 0:02 ` Andre Przywara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231021010221.3ac96652@slackpad.lan \
--to=andre.przywara@arm.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=project-tvbox@prp.uespi.br \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox