From: Dmitry Osipenko <digetx@gmail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Laxman Dewangan" <ldewangan@nvidia.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>
Cc: linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] i2c: tegra: allow VI support to be compiled out
Date: Tue, 18 Jan 2022 23:33:58 +0300 [thread overview]
Message-ID: <522fa061-4d4b-a135-51bd-e265b2476b93@gmail.com> (raw)
In-Reply-To: <fd14f1e81691f9655ea2ad58692df94dd2830230.1642535860.git.mirq-linux@rere.qmqm.pl>
18.01.2022 23:00, Michał Mirosław пишет:
> Save a bit of code for older Tegra platforms by compiling out
> VI's I2C mode support that's used only for Tegra210.
>
> $ size i2c-tegra.o
> text data bss dec hex filename
> 10385 240 8 10633 2989 i2c-tegra.o (full)
> 9617 240 8 9865 2689 i2c-tegra.o (no-dvc)
> 9389 240 8 9637 25a5 i2c-tegra.o (no-vi)
> 8617 240 8 8865 22a1 i2c-tegra.o (no-vi,no-dvc)
>
> ---
> v2: remove KConfig symbol as per Dmitry Osipenko's suggestion.
> (Assuming that for Tegra210 the VI part will be used anyway.)
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> ---
> drivers/i2c/busses/i2c-tegra.c | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
next prev parent reply other threads:[~2022-01-18 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 20:00 [PATCH v2 0/2] i2c: tegra: allow compiling out support for Tegra's special constrollers Michał Mirosław
2022-01-18 20:00 ` [PATCH v2 2/2] i2c: tegra: allow VI support to be compiled out Michał Mirosław
2022-01-18 20:33 ` Dmitry Osipenko [this message]
2022-01-18 20:00 ` [PATCH v2 1/2] i2c: tegra: allow DVC " Michał Mirosław
2022-01-18 20:33 ` Dmitry Osipenko
2022-01-27 21:31 ` Wolfram Sang
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=522fa061-4d4b-a135-51bd-e265b2476b93@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