[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vehwi8xzSBn_9Qa_SHF3ZCVGTBnsDmv6vix49vGt1wQhQ@mail.gmail.com>
Date: Mon, 16 Nov 2020 19:58:40 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: Andy Shevchenko <andriy.shevchenko@...el.com>,
Claudius Heine <ch@...x.de>,
Alessandro Zummo <a.zummo@...ertech.it>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Henning Schild <henning.schild@...mens.com>,
Johannes Hahn <johannes-hahn@...mens.com>
Subject: Re: [PATCH v2 1/3] rtc: rx6110: add i2c support
On Mon, Nov 16, 2020 at 7:38 PM Alexandre Belloni
<alexandre.belloni@...tlin.com> wrote:
> On 16/11/2020 16:43:43+0200, Andy Shevchenko wrote:
> > On Thu, Nov 12, 2020 at 02:07:32PM +0100, Claudius Heine wrote:
> > > The RX6110 also supports I2C, so this patch adds support for it to the
> > > driver.
> > >
> > > This also renames the SPI specific functions and variables to include
> > > `_spi_` in their names.
> >
> > As practice shows this is not the best approach. Can you ratqer split it to
> > three modules: core, spi, i2c like it's done in many other cases (esp. IIO)?
> >
>
> Actually, I'm fine with having everytihn in the same file because
> separating everything out means having 3 more files per rtc supporting
> both busses in an already very crowded folder. And I don't think being
> able to remove support for one or the other holds any actual value.
Good to know your opinion!
Since you are one who is looking after RTC stuff I'm not insisting on
my proposal.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists