[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYrFhTCa9rJ4savOcqRxcnyqoojCnwaCk6cnJv=aWxo4A@mail.gmail.com>
Date: Mon, 9 Oct 2023 23:02:39 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Doug Anderson <dianders@...gle.com>
Cc: Cong Yang <yangcong5@...qin.corp-partner.google.com>,
sam@...nborg.org, neil.armstrong@...aro.org, daniel@...ll.ch,
hsinyi@...gle.com, swboyd@...omium.org, airlied@...il.com,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [v1 0/2] Break out as separate driver from boe-tv101wum-nl6 panel driver
On Mon, Oct 9, 2023 at 10:53 PM Doug Anderson <dianders@...gle.com> wrote:
> Also: just as a heads up, Hsin-Yi measured the impact of removing the
> "command table" for init and replacing it with a whole pile of direct
> function calls. She found that it added over 100K to the driver (!!!).
> I believe it went from a 45K driver to a 152K driver. Something to
> keep in mind. ;-)
Sounds like Aarch64 code. I would love a comparison of the same
driver compiled to ARMv7t thumb code. Just for the academic
interest. Because I have heard about people running ARM32
kernels on Aarch64 hardware for this exact reason: so they can
have thumb, which is compact.
OK OK we definitely need command sequence tables in the core,
what we have now is each driver rolling its own which is looking bad.
Yours,
Linus Walleij
Powered by blists - more mailing lists