From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Marvell Kirkwood newbie question GPIO functions
Date: Fri, 19 Jun 2009 11:46:51 +0200 [thread overview]
Message-ID: <200906191146.51311.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D8E629DF@SC-VEXCH1.marvell.com>
Prafulla,
(...deleted some stuff...)
> > > What patches are in the pipeline?
>
> Some other board supports (MV88F6281GTW_GE) and Kirkwood SPI driver support
> Kirkwood USB support (at this moment)
>
Also very interesting :)
(...deleted, too...)
> >
> > What I forgot to mention is the i2c driver inside u-boot.
> > I need this to read the mac address from an additional eeprom.
> > This makes mass production more ease and doesn't produce
> > hight costs :)
>
> Kirkwood has in-built i2c(TWSI) controller, well.. the plans are in place
> enable driver for it, but this is not blocking issue right now hence
> pending ;-)
>
> Just FYI: you can protect some flash sector and use it in place of eeprom,
> this will lower the board cost and complexity too.
>
> But if you are planning to use some different GPIOs for i2c and bit-banged
> driver on the top of it, then you will need gpio control, so you can do it
> by using simple readl/writel calls meanwhile driver to come in :-)
>
Yes, I thought about that, too. GPIO support will also be helpful for doing
this!
Do you have some snippets how to readl/writel by hand?
> The best way I will suggest you is:
> Put pre-programmed eeprom around Kirkwood TWSI interface and enable "TWSI
> serial ROM initialization" you don't need anything else for this. (I hope
> you are having enough kirkwood documentation) Ref: table 32:
> http://www.marvell.com/files/products/embedded_processors/kirkwood/HW_88F62
>81_OpenSource.pdf
>
Good idea - I will read about that.
I've got access to all documents - including an marvell web account for
internal documents.
Regards,
Dieter
> Regards..
> Prafulla . .
>
> > Dieter
> >
> > > > > I'm willing to contribute some code if someone guides me a bit?
> > > >
> > > > You are most welcomed....
> > > > Pls feel free to raise your queries...
> > >
> > > Here they are :)
> > > Thanks,
> > > Dieter
> > >
> > > > Regards..
> > > > Prafulla . .
> > > >
> > > > > Thanks in advance,
> > > > > Dieter
> > > > >
> > > > > _______________________________________________
> > > > > U-Boot mailing list
> > > > > U-Boot at lists.denx.de
> > > > > http://lists.denx.de/mailman/listinfo/u-boot
> > >
> > > _______________________________________________
> > > U-Boot mailing list
> > > U-Boot at lists.denx.de
> > > http://lists.denx.de/mailman/listinfo/u-boot
> >
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2009-06-19 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:05 [U-Boot] Marvell Kirkwood newbie question GPIO functions Dieter Kiermaier
2009-06-19 8:18 ` Prafulla Wadaskar
2009-06-19 8:47 ` Dieter Kiermaier
2009-06-19 8:53 ` Dieter Kiermaier
2009-06-19 9:20 ` Prafulla Wadaskar
2009-06-19 9:46 ` Dieter Kiermaier [this message]
2009-06-19 9:51 ` Prafulla Wadaskar
2009-06-19 10:00 ` Dieter Kiermaier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906191146.51311.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox