[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4950bb1e-302f-947e-1924-452a8169b504@linux.intel.com>
Date: Wed, 20 May 2020 15:46:11 +0300
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Serge Semin <Sergey.Semin@...kalelectronics.ru>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Serge Semin <fancer.lancer@...il.com>,
Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Paul Burton <paulburton@...nel.org>,
Ralf Baechle <ralf@...ux-mips.org>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
linux-mips@...r.kernel.org, devicetree@...r.kernel.org,
Wolfram Sang <wsa@...-dreams.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Hanjun Guo <guohanjun@...wei.com>,
Hans de Goede <hdegoede@...hat.com>,
linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org
Subject: Re: [PATCH v2 08/12] i2c: designware: Introduce platform drivers glue
layer interface
Hi
On 5/10/20 12:50 PM, Serge Semin wrote:
> Seeing the DW I2C platform driver is getting overcomplicated with a lot of
> vendor-specific configs let's introduce a glue-layer interface so new
> platforms which equipped with Synopsys Designware APB I2C IP-core would
> be able to handle their peculiarities in the dedicated objects.
>
Comment to this patch and patches 9/12 and 12/12:
Currently i2c-designware-platdrv.c is about 500 lines of code so I don't
think it's too overcomplicated. But I feel we have already too many
Kconfig options and source modules for i2c-designware and obviously
would like to push back a little from adding more.
I don't think i2c-designware-platdrv.c becomes yet too complicated if
Baikal related code is added there, perhaps under #ifdef CONFIG_OF like
MSCC Ocelot code is currently.
--
Jarkko
Powered by blists - more mailing lists