Re: PCAP work for linux2.6-arm

2008-06-16 Thread Stefan Schmidt
Hello.

On Sat, 2008-06-14 at 17:47, Stefan Schmidt wrote:
 
 1) Copy ezx-pcap.patch, a780-pcap.patch, e680-pcap.patch,
pcap-ts.patch, a780-ts.patch and e680-ts.patch over to the
linux-2.6-arm branch. Add it to the series file.

Done for *-pcap.patch. Also merged e680 and a780 into one patch as the only
difference was SD or TF power up and we have both phones in one file now anyway.

*-ts.patch is still missing. I'm looking into this now.

 2) Move the pcap driver over to drivers/mfd/

Done. Header file lifes in include/linux/mfd/ now.

 3) Refresh patches (mostly Kconfig and Makefile)

Done

 4) Start to covert it to the generic SPI driver again and fix all API
changes on the way.

If the move over of the TS patches gives me no problem I'll start to study the
driver a bit deeper. Not sure if I'll come to real coding on it today.

regards
Stefan Schmidt


signature.asc
Description: Digital signature


Re: PCAP work for linux2.6-arm

2008-06-16 Thread Stefan Schmidt
Hello.

On Mon, 2008-06-16 at 19:57, Stefan Schmidt wrote:
 
 *-ts.patch is still missing. I'm looking into this now.

Also in now.

regards
Stefan Schmidt


signature.asc
Description: Digital signature


Re: PCAP work for linux2.6-arm

2008-06-15 Thread Antonio Ospite
On Sat, 14 Jun 2008 20:52:50 -0300
Daniel Ribeiro [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Antonio Ospite escreveu:
  I may test the MCI part on A910.
 
   You will have to write the MCI part for a910, not just test it. ;)


Busted! ;)

   PCAP business regarding MCI is just to power-on the card, its pretty
 easy. On the other EZX phones, we use pxamci driver to do the hard work,
 on A910 you will have to configure/use the mmc_spi driver, see
 drivers/mmc/host/mmc_spi.c.


I'll start looking at it, thanks.

Regards,
   Antonio

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

  Web site: http://www.studenti.unina.it/~ospite
Public key: http://www.studenti.unina.it/~ospite/aopubkey.asc


pgpPCrIbHRgR0.pgp
Description: PGP signature


Re: PCAP work for linux2.6-arm

2008-06-14 Thread Stefan Schmidt
Hello.

On Sat, 2008-06-14 at 10:07, Daniel Ribeiro wrote:
 
   Just to summarize what I think that needs to be done for PCAP to get in
 good shape:
 
   1) Convert it to the generic SPI driver.
   2) API changes on newer kernels.

OK

   3) Look at other interrupt controllers/expanders, and review the irq
 demultiplexer.

Review in what regard? Kernel coding style or functionality?

   4) Review locking.

Newer kernel have some debug features for loocking. Need to
investigate this.

   I suggest that we work on PCAP at the sime time as UDC, MCI and TS.
 This will help with testing.

I'm thinking about concentrate on one or two. But if you think you
meet the two weeks deadline with all three, fine with me. ;)

   The TS Driver is the best code to test at 3) and 4) as it floods PCAP
 with interrupts.

OK, having at least one other driver that uses the PCAP heavily is
indeed good for testing.

I'm also thinking about moving the driver over to drivers/mfd/. It's
more a multi-function-device then anything else.

The next steps how I see them:

1) Copy ezx-pcap.patch, a780-pcap.patch, e680-pcap.patch,
   pcap-ts.patch, a780-ts.patch and e680-ts.patch over to the
   linux-2.6-arm branch. Add it to the series file.

2) Move the pcap driver over to drivers/mfd/

3) Refresh patches (mostly Kconfig and Makefile)

4) Start to covert it to the generic SPI driver again and fix all API
   changes on the way.

Once we have this done and were able to test it one the phone we can
start to work on your 3 +4.

I'll do the easy steps (1-3) tomorrow if nobody beats me with this.
Hopefully I'll also will have some more time then to start reading the
code more carefull and begin to work on 4.

regards
Stefan Schmidt


signature.asc
Description: Digital signature


Re: PCAP work for linux2.6-arm

2008-06-14 Thread Antonio Ospite
On Sat, 14 Jun 2008 10:07:57 -0300
Daniel Ribeiro [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi,
 
   Just to summarize what I think that needs to be done for PCAP to get in
 good shape:
 
   1) Convert it to the generic SPI driver.

Lurking on the Net for pxa+SPI references, I found some recent
messages to LAK that could be useful to us too:
http://marc.info/?l=linux-arm-kernelm=121311158424208w=2
http://marc.info/?l=linux-arm-kernelm=121321470512149w=2

   2) API changes on newer kernels.
   3) Look at other interrupt controllers/expanders, and review the irq
 demultiplexer.
   4) Review locking.
 
   I suggest that we work on PCAP at the sime time as UDC, MCI and TS.
 This will help with testing.

I may test the MCI part on A910.

Regards,
   Antonio

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

  Web site: http://www.studenti.unina.it/~ospite
Public key: http://www.studenti.unina.it/~ospite/aopubkey.asc


pgpGmuNZuFiHG.pgp
Description: PGP signature


Re: PCAP work for linux2.6-arm

2008-06-14 Thread Daniel Ribeiro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Antonio Ospite escreveu:
 I may test the MCI part on A910.

You will have to write the MCI part for a910, not just test it. ;)

PCAP business regarding MCI is just to power-on the card, its pretty
easy. On the other EZX phones, we use pxamci driver to do the hard work,
on A910 you will have to configure/use the mmc_spi driver, see
drivers/mmc/host/mmc_spi.c.

- --
Daniel Ribeiro
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIVFnSw3OYl0G0liQRAuTtAKCFDLInXRHRgTJaVPBl+Kv0UX4zbwCdHwy7
L5pH8+AzCrPsiLowK30F0OE=
=ip2E
-END PGP SIGNATURE-