From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-i2c@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH v1 1/2] i2c: designware: Make master module optional
Date: Wed, 25 Mar 2020 13:45:29 +0200 [thread overview]
Message-ID: <20200325114529.GU1922688@smile.fi.intel.com> (raw)
In-Reply-To: <c3d2d5ff-605a-bdb7-275b-872fdfd10ccd@linux.intel.com>
On Wed, Mar 25, 2020 at 09:47:47AM +0200, Jarkko Nikula wrote:
> On 3/23/20 12:04 PM, Andy Shevchenko wrote:
> > In some cases we know that the controller will be always used in slave mode and
> > master is just a bulk. In order to drop that, introduce a separate configuration
> > parameter for master mode. Default it to core to avoid regressions.
> I think we should go to a opposite direction - reduce the number of
> I2C_DESIGNWARE_ config options rather than add new ones. We already have 5
> config options for it.
>
> Size of i2c-designware-core.ko is around 12 kB with all master, slave and
> Baytrail semaphore code built in so I don't think it justifies the added
> config complexity. I think distributions will have anyway all of those
> options set.
I would rather go with conditional based on I²C generic options, like I2C_SLAVE.
Do we have something similar for master?
> Having those code in separate modules and load only when needed might make
> sense as that would save a few kB of RAM.
...which makes sense for embedded systems where exactly the device represents
I²C slave.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-03-25 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 10:04 [PATCH v1 1/2] i2c: designware: Make master module optional Andy Shevchenko
2020-03-23 10:04 ` [PATCH v1 2/2] i2c: designware: Move configuration routines to respective modules Andy Shevchenko
2020-03-23 12:26 ` [PATCH v1 1/2] i2c: designware: Make master module optional Andy Shevchenko
2020-03-25 7:47 ` Jarkko Nikula
2020-03-25 11:45 ` Andy Shevchenko [this message]
2020-04-15 11:37 ` 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=20200325114529.GU1922688@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa+renesas@sang-engineering.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).