From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yannick GICQUEL Subject: Re: m68knommu: CONFIG_I2C_COLDFIRE and CONFIG_RTC_DRV_M5441x Date: Fri, 23 May 2014 08:44:56 +0200 Message-ID: <537EEE68.5030506@open.eurogiciel.org> References: <1400614121.4912.58.camel@x220> <201405201350.35661.sfking@fdwdc.com> <537CCA66.1050502@open.eurogiciel.org> <537D4D1A.2070108@westnet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <537D4D1A.2070108@westnet.com.au> Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Greg Ungerer Cc: Steven King , Geert Uytterhoeven , Paul Bolle , linux-m68k , Gilles DOFFE , Baptiste Durand , Yannick GICQUEL Hi Greg, Le 22/05/2014 03:04, Greg Ungerer a =C3=A9crit : > Hi Yannick, > > On 22/05/14 01:46, Yannick GICQUEL wrote: >> The MCF5441x support is quite a hot topic today for our company. >> This Soc family is seducing some of our customers, especially for it= 's long term support from Freescale. >> >> We have worked on this target since past few weeks, using a Tower Ki= t hardware and JTag, and just about to prepare a full integration of th= is device on recent kernel release. >> As a part of the open-source department, we have also planned to del= iver this work to the community and propose some patches to refresh thi= s target support. >> >> Some informations we observe on this target to be refreshed: >> - NAND controller needs to be integrated again, >> - UART controller as well, > What needs to be done to the mcf UART driver? > It seems all other ColdFire parts have used pretty much the same > module. You're right. After initials investigations, we thought there was a=20 rework needed but after yesterday investigations, we confirm it's=20 functional state is Ok. Please, just forget initial rework mentioned :-) >> Also : >> - This chip contains a MMU and can be unlink from the !MMU depende= ncy > The ColdFire v4e MMU has been supported for quite a while in main > line kernels (from linux-3.3 onwards). I believe it will need some > tweaks for the mcf5441x, but the heavy lifting is done. > > Also keep in mind that for ColdFire that have an MMU we support them > both with the MMU enabled and disabled. > =20 Ok, we will keep it in mind. We had a look on this MMU activation and functional state is ko. To state this, we had to unlink MMU activation to FPU activation, but=20 this is not as simple and it need a deeper investigation. >> This is for the big lines, if the community is ok for a patch receip= t, some other feature can be also pushed. >> BTW, what about this patches proposal ? Is there some time slot for = patch proposal ? > Early and often :-) > Post them here. If you are really unsure about some specific feature > then you can discuss it here first. But if you have code already why > not just send patches. Our patches are not clean enough to be posted right now, but as people=20 here are receptive to this, we will go on. > > Regards > Greg > > >> Regards, >> >> Le 20/05/2014 22:50, Steven King a =C3=A9crit : >>> On Tuesday 20 May 2014 1:19:26 pm Geert Uytterhoeven wrote: >>>> Hi Paul, >>>> >>>> On Tue, May 20, 2014 at 9:28 PM, Paul Bolle w= rote: >>>>> In v3.6 both a check for CONFIG_I2C_COLDFIRE and two checks for >>>>> CONFIG_RTC_DRV_M5441x were added to the code for the coldfire pla= tform >>>>> (in m525x.c and in m5441x.c respectively). Neither of these macro= s can >>>>> be matched to a Kconfig symbol. >>>>> >>>>> Is a series that adds these Kconfig symbols pending? >>>> For the former, Steven King (cc) submitted patches in 2010 and 201= 2. >>>> For the latter, he submitted patches in 2012. >>>> >>>> Seems like they were never integrated... >>> Indeed. >>> >>> At this point, they're pretty much superfluous so if someone were t= o submit a patch removing them, they would not get any objections from = me. >>> --=20 >>> To unsubscribe from this list: send the line "unsubscribe linux-m68= k" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >> --=20 >> To unsubscribe from this list: send the line "unsubscribe linux-m68k= " in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >>