linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/2] i2c: tegra: allow compiling out support for Tegra's special constrollers
Date: Sun, 16 Jan 2022 21:34:42 +0300	[thread overview]
Message-ID: <e7a9a48b-e924-9e14-a4ff-b13853c5033e@gmail.com> (raw)
In-Reply-To: <YeRd90gLqtsz2zVV@qmqm.qmqm.pl>

16.01.2022 21:03, Michał Mirosław пишет:
> On Sun, Jan 16, 2022 at 08:54:08PM +0300, Dmitry Osipenko wrote:
>> 16.01.2022 19:02, Michał Mirosław пишет:
>>> To patches that, combined, reduce I2C driver's code by ~2kB and a bit
>>> from runtime overhead for non-Tegra20 or non-Tegra210 builds.
>>>
>>> Michał Mirosław (2):
>>>   i2c: tegra: allow DVC support to be compiled out
>>>   i2c: tegra: allow VI support to be compiled out
>>>
>>>  drivers/i2c/busses/Kconfig     | 16 ++++++++++++++++
>>>  drivers/i2c/busses/i2c-tegra.c | 35 +++++++++++++++++++++-------------
>>>  2 files changed, 38 insertions(+), 13 deletions(-)
>>>
>>
>> 2KB is a too small difference to justify the ifdefs and Kconfig entries,
>> IMO.
> 
> Maybe I should have mentioned that it's ~20%? With my "embedded" hat on:
> I think it might be small, but sometimes it is the difference between
> bootable kernel or one too big.

10KB is a small size too. I'm very doubtful that such changes make any
real difference in practice.

Much more practical should be to modularize more kernel code. You should
be able to squeeze zImage down to 3MB without any code changes by
toggling more kernel config options to =m. Try to use grate_defconfig
[1] for the base, that is what postmarketOS kernel build uses.

[1]
https://github.com/grate-driver/linux/blob/master/arch/arm/configs/grate_defconfig

  reply	other threads:[~2022-01-16 18:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 16:02 [PATCH 0/2] i2c: tegra: allow compiling out support for Tegra's special constrollers Michał Mirosław
2022-01-16 16:02 ` [PATCH 2/2] i2c: tegra: allow VI support to be compiled out Michał Mirosław
2022-01-16 16:02 ` [PATCH 1/2] i2c: tegra: allow DVC " Michał Mirosław
2022-01-18  9:46   ` Dmitry Osipenko
2022-01-18 19:48     ` Michał Mirosław
2022-01-16 17:54 ` [PATCH 0/2] i2c: tegra: allow compiling out support for Tegra's special constrollers Dmitry Osipenko
2022-01-16 18:03   ` Michał Mirosław
2022-01-16 18:34     ` Dmitry Osipenko [this message]
2022-01-16 21:39       ` Michał Mirosław
2022-01-17 15:37         ` Dmitry Osipenko
2022-01-17 16:10           ` Michał Mirosław

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=e7a9a48b-e924-9e14-a4ff-b13853c5033e@gmail.com \
    --to=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=thierry.reding@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).