[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1458297495.3499.29.camel@gmail.com>
Date: Fri, 18 Mar 2016 13:38:15 +0300
From: Sergei Ianovich <ynvich@...il.com>
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Rich Felker <dalias@...c.org>
Cc: linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"open list:REAL TIME CLOCK RTC SUBSYSTEM"
<rtc-linux@...glegroups.com>, linux-sh@...r.kernel.org
Subject: Re: [PATCH v7] rtc: rewrite DS1302 using SPI
On Tue, 2016-03-15 at 01:18 +0100, Alexandre Belloni wrote:
> I would like to have a solution for secureedge5410 even if it is
> untested. Else, we are breaking an existing platform without any
> solution.
>
> I've put the sh maintainers in copy, maybe they have an opinion. Else
> I'll let your patch sit in linux-next for the next cycle.
secureedge5410 will need an SPI host driver. The driver will be similar
to the one I did for lp8841. I can make a clone for secureedge5410, but
I cannot test it.
The only reason, I didn't file the patch for secureedge5410, is I
thought SPI people won't accept an untested patch.
Powered by blists - more mailing lists