Re: m68knommu: CONFIG_I2C_COLDFIRE and CONFIG_RTC_DRV_M5441x

[Yannick GICQUEL <yannick.gicquel@open.eurogiciel.org>]

Hi Greg,

Le 22/05/2014 03:04, Greg Ungerer a écrit :
> 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 Kit hardware and JTag, and just about to prepare a full integration of this device on recent kernel release.
>> As a part of the open-source department, we have also planned to deliver this work to the community and propose some patches to refresh this 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 
rework needed but after yesterday investigations, we confirm it's 
functional state is Ok.
Please, just forget initial rework mentioned :-)
>> Also :
>>   - This chip contains a MMU and can be unlink from the !MMU dependency
> 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.
>   
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 
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 receipt, 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 
here are receptive to this, we will go on.

>
> Regards
> Greg
>
>
>> Regards,
>>
>> Le 20/05/2014 22:50, Steven King a écrit :
>>> 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 <pebolle@tiscali.nl> wrote:
>>>>> 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 platform
>>>>> (in m525x.c and in m5441x.c respectively). Neither of these macros 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 2012.
>>>> 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 to submit a patch removing them, they would not get any objections from me.
>>> -- 
>>> 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
>> -- 
>> 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
>>