Hi,
We probably need someone to look after the few drivers/mfd patches coming
every now and then. As agreed with Andrew, I'm ok to do so and my employer
is fine with me spending a few working hours on it, if needed.
Ben, Philipp, feel free to add your names there too if you wish.
Signed-off-by: Samuel Ortiz <[email protected]>
--
MAINTAINERS | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index cd587ee..f45938b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2814,6 +2814,12 @@ W: https://tango.0pointer.de/mailman/listinfo/s270-linux
W: http://0pointer.de/lennart/tchibo.html
S: Maintained
+MULTIFUNCTION DEVICES (MFD)
+P: Samuel Ortiz
+M: [email protected]
+L: [email protected]
+S: Supported
+
MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND SDIO SUBSYSTEM
P: Pierre Ossman
M: [email protected]
Added Ian, Dmitry and Russell to Cc.
On Wed, Jun 18, 2008 at 11:42 PM, Samuel Ortiz <[email protected]> wrote:
> Hi,
>
> We probably need someone to look after the few drivers/mfd patches coming
> every now and then. As agreed with Andrew, I'm ok to do so and my employer
> is fine with me spending a few working hours on it, if needed.
Right now quite some of the MFD patches go through arm-kernel, but I
guess once that initial rush of ARM machine patches depending on MFD
patches submitted at the same time is over, it's a very good idea to
have a proper path into the kernel.
regards
Philipp
> Signed-off-by: Samuel Ortiz <[email protected]>
> --
>
> MAINTAINERS | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index cd587ee..f45938b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2814,6 +2814,12 @@ W: https://tango.0pointer.de/mailman/listinfo/s270-linux
> W: http://0pointer.de/lennart/tchibo.html
> S: Maintained
>
> +MULTIFUNCTION DEVICES (MFD)
> +P: Samuel Ortiz
> +M: [email protected]
> +L: [email protected]
> +S: Supported
> +
> MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND SDIO SUBSYSTEM
> P: Pierre Ossman
> M: [email protected]
>
Hi guys!
Good timing! I just sat down with the e-series code last night!
I'd like to see the MFD core make it into mainline, and then we can
start pushing the TMIO drivers too.
These drivers are in a LOT of handhelds and I'd really like to see the
code move to mainline now.
The code is maturing well - I just bumped all the eseries stuff, which
includes the core MFD code and all the TMIO drivers from 2.6.24 to
2.6.26-git and the only issue was some minor #include breakage.
I'll tidy up the code and pop a branch on my git server for people to
review, if thats what people want.
Dmitry - if you have any pending patches now is the time to send them on
over ;-)
-Ian
On Thu, 2008-06-19 at 11:59 +0200, pHilipp Zabel wrote:
> Added Ian, Dmitry and Russell to Cc.
>
> On Wed, Jun 18, 2008 at 11:42 PM, Samuel Ortiz <[email protected]> wrote:
> > Hi,
> >
> > We probably need someone to look after the few drivers/mfd patches coming
> > every now and then. As agreed with Andrew, I'm ok to do so and my employer
> > is fine with me spending a few working hours on it, if needed.
>
> Right now quite some of the MFD patches go through arm-kernel, but I
> guess once that initial rush of ARM machine patches depending on MFD
> patches submitted at the same time is over, it's a very good idea to
> have a proper path into the kernel.
Hi,
2008/6/19 ian <[email protected]>:
> Hi guys!
>
> Good timing! I just sat down with the e-series code last night!
>
> I'd like to see the MFD core make it into mainline, and then we can
> start pushing the TMIO drivers too.
>
> These drivers are in a LOT of handhelds and I'd really like to see the
> code move to mainline now.
>
> The code is maturing well - I just bumped all the eseries stuff, which
> includes the core MFD code and all the TMIO drivers from 2.6.24 to
> 2.6.26-git and the only issue was some minor #include breakage.
>
> I'll tidy up the code and pop a branch on my git server for people to
> review, if thats what people want.
It's better to send patches to some ML.
>
> Dmitry - if you have any pending patches now is the time to send them on
> over ;-)
Actually the code I'm using has diverged a bit from the last code I've
sent before this merging pulse.
As you have seen, I've tried to submit parts of the core and tmio-nand
driver as a start. Then I'd suggest
to merge other tmio core bits (support for tc6387xb and t7l66xb). The
MMC, usb and fb cell drivers could
benefit from clocklib patches I'm trying to get in. I'll submit the
updated version of mfd-core patch this evening,
however some other bits will require more time from my side.
>
> -Ian
>
> On Thu, 2008-06-19 at 11:59 +0200, pHilipp Zabel wrote:
>> Added Ian, Dmitry and Russell to Cc.
>>
>> On Wed, Jun 18, 2008 at 11:42 PM, Samuel Ortiz <[email protected]> wrote:
>> > Hi,
>> >
>> > We probably need someone to look after the few drivers/mfd patches coming
>> > every now and then. As agreed with Andrew, I'm ok to do so and my employer
>> > is fine with me spending a few working hours on it, if needed.
>>
>> Right now quite some of the MFD patches go through arm-kernel, but I
>> guess once that initial rush of ARM machine patches depending on MFD
>> patches submitted at the same time is over, it's a very good idea to
>> have a proper path into the kernel.
Yeah!
--
With best wishes
Dmitry
On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
> > I'll tidy up the code and pop a branch on my git server for people to
> > review, if thats what people want.
>
> It's better to send patches to some ML.
Well, the code I had is updated to match linus -git branch
eseries_release7 if anyones curious. (no real changes since last time
though)
> > Dmitry - if you have any pending patches now is the time to send them on
> > over ;-)
>
> Actually the code I'm using has diverged a bit from the last code I've
> sent before this merging pulse.
All progress is good :)
> As you have seen, I've tried to submit parts of the core and tmio-nand
> driver as a start.
Has any of that got merged yet? If so, I'll adapt my strategy to match
that, otherwise I'll try to keep all the drivers in parallel.
> Then I'd suggest to merge other tmio core bits (support for tc6387xb
> and t7l66xb). The MMC, usb and fb cell drivers could benefit from
> clocklib patches I'm trying to get in.
I'd like to see those. I'll get MMC and USB updated ASAP.
have you solved the clock-api-tied-to-platform-architecture problem ?
> I'll submit the updated version of mfd-core patch this evening,
Looking forward to it.
> however some other bits will require more time from my side.
Lets rock :-)
Hi,
2008/6/19 ian <[email protected]>:
> On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
>
>> > I'll tidy up the code and pop a branch on my git server for people to
>> > review, if thats what people want.
>>
>> It's better to send patches to some ML.
>
> Well, the code I had is updated to match linus -git branch
> eseries_release7 if anyones curious. (no real changes since last time
> though)
>
>> > Dmitry - if you have any pending patches now is the time to send them on
>> > over ;-)
>>
>> Actually the code I'm using has diverged a bit from the last code I've
>> sent before this merging pulse.
>
> All progress is good :)
>
>> As you have seen, I've tried to submit parts of the core and tmio-nand
>> driver as a start.
>
> Has any of that got merged yet? If so, I'll adapt my strategy to match
> that, otherwise I'll try to keep all the drivers in parallel.
>
>> Then I'd suggest to merge other tmio core bits (support for tc6387xb
>> and t7l66xb). The MMC, usb and fb cell drivers could benefit from
>> clocklib patches I'm trying to get in.
>
> I'd like to see those. I'll get MMC and USB updated ASAP.
>
> have you solved the clock-api-tied-to-platform-architecture problem ?
There were plenty of tries to merge clocklib. Check lkml archives.
>
>> I'll submit the updated version of mfd-core patch this evening,
>
> Looking forward to it.
you should have received it.
>> however some other bits will require more time from my side.
>
> Lets rock :-)
--
With best wishes
Dmitry
On Thu, Jun 19, 2008 at 5:32 PM, Dmitry <[email protected]> wrote:
> Hi,
>
> 2008/6/19 ian <[email protected]>:
>> On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
>>
>>> > I'll tidy up the code and pop a branch on my git server for people to
>>> > review, if thats what people want.
>>>
>>> It's better to send patches to some ML.
>>
>> Well, the code I had is updated to match linus -git branch
>> eseries_release7 if anyones curious. (no real changes since last time
>> though)
>>
>>> > Dmitry - if you have any pending patches now is the time to send them on
>>> > over ;-)
>>>
>>> Actually the code I'm using has diverged a bit from the last code I've
>>> sent before this merging pulse.
>>
>> All progress is good :)
>>
>>> As you have seen, I've tried to submit parts of the core and tmio-nand
>>> driver as a start.
>>
>> Has any of that got merged yet? If so, I'll adapt my strategy to match
>> that, otherwise I'll try to keep all the drivers in parallel.
>>
>>> Then I'd suggest to merge other tmio core bits (support for tc6387xb
>>> and t7l66xb). The MMC, usb and fb cell drivers could benefit from
>>> clocklib patches I'm trying to get in.
>>
>> I'd like to see those. I'll get MMC and USB updated ASAP.
>>
>> have you solved the clock-api-tied-to-platform-architecture problem ?
>
> There were plenty of tries to merge clocklib. Check lkml archives.
How could we stir up some interest in those patches again? The last
round didn't receive any comments.
regards
Philipp
On Thu, Jun 19, 2008 at 5:09 PM, ian <[email protected]> wrote:
> On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
>
>> > I'll tidy up the code and pop a branch on my git server for people to
>> > review, if thats what people want.
>>
>> It's better to send patches to some ML.
>
> Well, the code I had is updated to match linus -git branch
> eseries_release7 if anyones curious. (no real changes since last time
> though)
>
>> > Dmitry - if you have any pending patches now is the time to send them on
>> > over ;-)
>>
>> Actually the code I'm using has diverged a bit from the last code I've
>> sent before this merging pulse.
>
> All progress is good :)
>
>> As you have seen, I've tried to submit parts of the core and tmio-nand
>> driver as a start.
>
> Has any of that got merged yet? If so, I'll adapt my strategy to match
> that, otherwise I'll try to keep all the drivers in parallel.
>
>> Then I'd suggest to merge other tmio core bits (support for tc6387xb
>> and t7l66xb). The MMC, usb and fb cell drivers could benefit from
>> clocklib patches I'm trying to get in.
>
> I'd like to see those. I'll get MMC and USB updated ASAP.
That is interesting. I just asked Samuel about the ASIC3 MMC code
which Aric copied from tc6393xb. It seems we should try to reuse the
tmio driver itself for ASIC3?
> have you solved the clock-api-tied-to-platform-architecture problem ?
>
>> I'll submit the updated version of mfd-core patch this evening,
>
> Looking forward to it.
>
>> however some other bits will require more time from my side.
>
> Lets rock :-)
regards
Philipp
Hi,
2008/6/19 pHilipp Zabel <[email protected]>:
> On Thu, Jun 19, 2008 at 5:09 PM, ian <[email protected]> wrote:
>> On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
>>
>>> > I'll tidy up the code and pop a branch on my git server for people to
>>> > review, if thats what people want.
>>>
>>> It's better to send patches to some ML.
>>
>> Well, the code I had is updated to match linus -git branch
>> eseries_release7 if anyones curious. (no real changes since last time
>> though)
>>
>>> > Dmitry - if you have any pending patches now is the time to send them on
>>> > over ;-)
>>>
>>> Actually the code I'm using has diverged a bit from the last code I've
>>> sent before this merging pulse.
>>
>> All progress is good :)
>>
>>> As you have seen, I've tried to submit parts of the core and tmio-nand
>>> driver as a start.
>>
>> Has any of that got merged yet? If so, I'll adapt my strategy to match
>> that, otherwise I'll try to keep all the drivers in parallel.
>>
>>> Then I'd suggest to merge other tmio core bits (support for tc6387xb
>>> and t7l66xb). The MMC, usb and fb cell drivers could benefit from
>>> clocklib patches I'm trying to get in.
>>
>> I'd like to see those. I'll get MMC and USB updated ASAP.
>
> That is interesting. I just asked Samuel about the ASIC3 MMC code
> which Aric copied from tc6393xb. It seems we should try to reuse the
> tmio driver itself for ASIC3?
That was also one of the goals for the tmio cell drivers. However merging
ASIC3 support will require some hacking around address shifts for the cell.
>
>> have you solved the clock-api-tied-to-platform-architecture problem ?
>>
>>> I'll submit the updated version of mfd-core patch this evening,
>>
>> Looking forward to it.
>>
>>> however some other bits will require more time from my side.
>>
>> Lets rock :-)
>
> regards
> Philipp
>
--
With best wishes
Dmitry
2008/6/19 pHilipp Zabel <[email protected]>:
> On Thu, Jun 19, 2008 at 5:32 PM, Dmitry <[email protected]> wrote:
>> Hi,
>>
>> 2008/6/19 ian <[email protected]>:
>>> On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
>>>
>>>> > I'll tidy up the code and pop a branch on my git server for people to
>>>> > review, if thats what people want.
>>>>
>>>> It's better to send patches to some ML.
>>>
>>> Well, the code I had is updated to match linus -git branch
>>> eseries_release7 if anyones curious. (no real changes since last time
>>> though)
>>>
>>>> > Dmitry - if you have any pending patches now is the time to send them on
>>>> > over ;-)
>>>>
>>>> Actually the code I'm using has diverged a bit from the last code I've
>>>> sent before this merging pulse.
>>>
>>> All progress is good :)
>>>
>>>> As you have seen, I've tried to submit parts of the core and tmio-nand
>>>> driver as a start.
>>>
>>> Has any of that got merged yet? If so, I'll adapt my strategy to match
>>> that, otherwise I'll try to keep all the drivers in parallel.
>>>
>>>> Then I'd suggest to merge other tmio core bits (support for tc6387xb
>>>> and t7l66xb). The MMC, usb and fb cell drivers could benefit from
>>>> clocklib patches I'm trying to get in.
>>>
>>> I'd like to see those. I'll get MMC and USB updated ASAP.
>>>
>>> have you solved the clock-api-tied-to-platform-architecture problem ?
>>
>> There were plenty of tries to merge clocklib. Check lkml archives.
>
> How could we stir up some interest in those patches again? The last
> round didn't receive any comments.
>
I don't know :( Maybe I shoud give up the idea of using kobjects, switch back
to kref and do a partial merge of those two patchset branches. I'll think about
it this weekend.
--
With best wishes
Dmitry
On Thu, 2008-06-19 at 18:06 +0200, pHilipp Zabel wrote:
> > There were plenty of tries to merge clocklib. Check lkml archives.
>
> How could we stir up some interest in those patches again? The last
> round didn't receive any comments.
I dont know how either.
I really like this approach though and think we should persevere...