Re: [linux-sunxi] Re: [PATCH 6/7] regulator: AXP20x: Add support for regulators subsystem
On Sat, Mar 08, 2014 at 12:43:04PM +0100, Carlo Caione wrote: > On Fri, Mar 7, 2014 at 7:22 PM, Maxime Ripard > > On Sat, Mar 01, 2014 at 05:45:51PM +0100, Carlo Caione wrote: > >> + return platform_driver_register(&axp20x_regulator_driver); > > I thought the AXP was only connected through I2C? How is that a > > platform device then? > Not really. It is plain wrong. > I'll fix it in v2. Are you sure this is wrong? For MFDs the core MFD is a driver of whatever bus type is in use but the function drivers are platform devices which talk to the hardware via the core device. signature.asc Description: Digital signature
[linux-sunxi] A31 pmic (axp221) support
Hi Maxime, Yesterday I've been playing a bit with my Mele A1000G Quad, with the purpose of trying to get usb and mmc working there. I already have wens' gmac patches for the A31 in my tree, so for starters I tried to get that to work. Unfortunately the fex shows that the phy is powered by dldo1 from the pmic, and by default that is configured to off. So I got stuck there wrt getting the gmac to work on the A1000G Quad / M9. Do you know if anyone is working on pmic support for the A31, or for the new push-pull serial bus this uses? Is this bus similar enough to i2c that we can use the i2c subsys for this, maybe with an extra controller flag, or do we need to likely write a whole new subsys for this ? Also do you know of a datasheet for the AXP221 somewhere ? Regards, Hans -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Here is a link for what I did on the PengPod where we used the original
u-boot from Android.
http://pengpod.com/pengwiki/index.php?title=Install_Linaro_to_the_internal_flash
The only trick not listed was the u-boot environment had to be signed, I
can't remember the name of the tool but its in the u-boot repo.
I think the first logo was displayed by boot1, before u-boot runs.
Hi Timo,
Thanks for the detailed answer to my questions, really appreciate that.
I have done the same thing, still I am stuck at the logo screen, feels
like there is something else is missing in my case.
1> I don't see any serial output from NAND boot, did you see anything
on the serial console if you were using serial output?
2> anyone knows if the logo has been displayed, does it imply that
u-boot.bin got loaded at all?
I think in my case, the question is why u-boot.bin built from
sun5i_a13 with the CONFIG_BOOTCOMMAND modification doesn't print any
output at all? in the common/main.c:
|
205 static inline int abortboot(int bootdelay)
206 {
207 int abort = 0;
208
209 #ifdef CONFIG_MENUPROMPT
210 printf(CONFIG_MENUPROMPT);
211 #else
212 printf("Hit any key to stop autoboot: %2d ", bootdelay);
213 #endif
|
would always print "Hit any key to stop autoboot:", even if something
went wrong later? but I saw nothing from console, (UART1 that is I am
using and good with SD boot).
Still baffled, :-(
Regards,
-Hunter
On Saturday, March 8, 2014 1:07:44 PM UTC-6, Timo Schmiade wrote:
Hi Patrick,
> Looks to me like this is loading script.bin and uImage from nanda.
thanks for pointing this out, you're of course right! nandb contains
my root filesystem, nanda is the boot partition.
On Sat, Mar 8, 2014 at 3:24 PM, Patrick Wood > wrote:
>
> Looks to me like this is loading script.bin and uImage from nanda.
>
> --
> You received this message because you are subscribed to a topic
in the Google Groups "linux-sunxi" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe
.
> To unsubscribe from this group and all of its topics, send an
email to linux-sunxi...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout
.
--
You received this message because you are subscribed to the Google
Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to linux-sunxi+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Oh, I see it is uart1. Did you build uboot to use uart1 for console? -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Is your serial debug port on uart0? -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Hi Timo,
Thanks for the detailed answer to my questions, really appreciate that.
I have done the same thing, still I am stuck at the logo screen, feels like
there is something else is missing in my case.
1> I don't see any serial output from NAND boot, did you see anything on
the serial console if you were using serial output?
2> anyone knows if the logo has been displayed, does it imply that
u-boot.bin got loaded at all?
I think in my case, the question is why u-boot.bin built from sun5i_a13
with the CONFIG_BOOTCOMMAND modification doesn't print any output at all?
in the common/main.c:
205 static inline int abortboot(int bootdelay)
206 {
207 int abort = 0;
208
209 #ifdef CONFIG_MENUPROMPT
210 printf(CONFIG_MENUPROMPT);
211 #else
212 printf("Hit any key to stop autoboot: %2d ", bootdelay);
213 #endif
would always print "Hit any key to stop autoboot:", even if something went
wrong later? but I saw nothing from console, (UART1 that is I am using and
good with SD boot).
Still baffled, :-(
Regards,
-Hunter
On Saturday, March 8, 2014 1:07:44 PM UTC-6, Timo Schmiade wrote:
>
> Hi Patrick,
>
> > Looks to me like this is loading script.bin and uImage from nanda.
>
> thanks for pointing this out, you're of course right! nandb contains
> my root filesystem, nanda is the boot partition.
>
> On Sat, Mar 8, 2014 at 3:24 PM, Patrick Wood
> >
> wrote:
> >
> > Looks to me like this is loading script.bin and uImage from nanda.
> >
> > --
> > You received this message because you are subscribed to a topic in the
> Google Groups "linux-sunxi" group.
> > To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe.
> > To unsubscribe from this group and all of its topics, send an email to
> linux-sunxi...@googlegroups.com .
> > For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Hi Patrick, > Looks to me like this is loading script.bin and uImage from nanda. thanks for pointing this out, you're of course right! nandb contains my root filesystem, nanda is the boot partition. On Sat, Mar 8, 2014 at 3:24 PM, Patrick Wood wrote: > > Looks to me like this is loading script.bin and uImage from nanda. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "linux-sunxi" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe. > To unsubscribe from this group and all of its topics, send an email to > linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Mele a1000 hangs on boot using sunxi-devel, seems ehci-related
Actually, I take that back. It seems to be freezing at this point: http://pastebin.com/JXj1cHHD On Saturday, March 8, 2014 12:12:48 PM UTC-6, Matthew Schneider wrote: > > I just recompiled the ohci and ehci drivers as modules, and now it's > consistently freezing at random places. > > On Saturday, March 8, 2014 11:54:25 AM UTC-6, Matthew Schneider wrote: >> >> I had the problem as well where it wasn't able to locate the firmware and >> seemed to hang up on that. So I compiled the firmware into the kernel, but >> then it hung on the message "rtlwifi: wireless switch is on". So then I >> took the wireless device drivers out the kernel entirely (since I don't >> really need them), which leaves me with my original post. >> >> On Saturday, March 8, 2014 7:48:49 AM UTC-6, CodeKipper wrote: >>> >>> Hi, >>> I'm also currently battling suxi-devel on my Mele A2000. I'm getting a >>> little bit further than you but not by a great deal. Here is my .config >>> which I took from Hans. There are a couple of differences to get the >>> wireless bits compiled into the uImage. The rootfs I've been using is >>> Debian(which doesn't seem to locate the firmware) and in >>> http://pastebin.com/XNVxf03B which is the openwrt rootfs which does >>> load the firmware and then seems to hang. >>> Good luck with this, I can't play anymore today but let's us know if you >>> get any further. >>> CK >>> >>> >>> On 8 March 2014 08:56, Matthew Schneider wrote: >>> My mele a1000 hangs on boot using the sunxi-devel kernel tree. It seems like it'll sometimes hang at different places, but most of the time it'll hang at "usb 2-1: new high-speed USB device number 2 using ehci-platform". I've attached my kernel configuration. Here's the last screen my console showed: [0.857803] ehci-platform 1c1c000.usb: EHCI Host Controller [0.863428] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2 [0.871240] ehci-platform 1c1c000.usb: irq 22, io mem 0x01c1c000 [0.893010] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00 [0.899687] hub 2-0:1.0: USB hub found [0.903476] hub 2-0:1.0: 1 port detected [0.907701] ohci-platform 1c14400.usb: Generic Platform OHCI controller [0.914369] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3 [0.922149] ohci-platform 1c14400.usb: irq 20, io mem 0x01c14400 [0.953049] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [0.965526] ata1.00: ATA-8: ST1000LM024 HN-M101MBB, 2AR10002, max UDMA/133 [0.972396] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) [0.987092] ata1.00: configured for UDMA/133 [0.991950] hub 3-0:1.0: USB hub found [0.995759] hub 3-0:1.0: 1 port detected [1.15] ohci-platform 1c1c400.usb: Generic Platform OHCI controller [1.008000] scsi 0:0:0:0: Direct-Access ATA ST1000LM024 HN-M 2AR1 PQ: 0 ANSI: 5 [1.017164] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4 [1.025424] ohci-platform 1c1c400.usb: irq 23, io mem 0x01c1c400 [1.087535] hub 4-0:1.0: USB hub found [1.091308] hub 4-0:1.0: 1 port detected [1.095522] sunxi-rtc 1c20d00.rtc: setting system clock to 2010-01-01 00:01:57 UTC (1262304117) [1.104382] ALSA device list: [1.107366] No soundcards found. [1.111339] Waiting for root device /dev/mmcblk0p2... [1.123224] mmc0: host does not support reading read-only switch. assuming write-enable. [1.173033] usb 1-1: new high-speed USB device number 2 using ehci-platform [1.293012] mmc0: new high speed SDHC card at address e624 [1.298821] mmcblk0: mmc0:e624 SU16G 14.8 GiB [1.305399] mmcblk0: p1 p2 [1.335541] hub 1-1:1.0: USB hub found [1.339632] hub 1-1:1.0: 4 ports detected [1.347376] EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240) [1.357364] EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240) [1.463026] usb 2-1: new high-speed USB device number 2 using ehci-platform -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. >>> >>> -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Mele a1000 hangs on boot using sunxi-devel, seems ehci-related
I just recompiled the ohci and ehci drivers as modules, and now it's consistently freezing at random places. On Saturday, March 8, 2014 11:54:25 AM UTC-6, Matthew Schneider wrote: > > I had the problem as well where it wasn't able to locate the firmware and > seemed to hang up on that. So I compiled the firmware into the kernel, but > then it hung on the message "rtlwifi: wireless switch is on". So then I > took the wireless device drivers out the kernel entirely (since I don't > really need them), which leaves me with my original post. > > On Saturday, March 8, 2014 7:48:49 AM UTC-6, CodeKipper wrote: >> >> Hi, >> I'm also currently battling suxi-devel on my Mele A2000. I'm getting a >> little bit further than you but not by a great deal. Here is my .config >> which I took from Hans. There are a couple of differences to get the >> wireless bits compiled into the uImage. The rootfs I've been using is >> Debian(which doesn't seem to locate the firmware) and in >> http://pastebin.com/XNVxf03B which is the openwrt rootfs which does load >> the firmware and then seems to hang. >> Good luck with this, I can't play anymore today but let's us know if you >> get any further. >> CK >> >> >> On 8 March 2014 08:56, Matthew Schneider wrote: >> >>> My mele a1000 hangs on boot using the sunxi-devel kernel tree. >>> >>> It seems like it'll sometimes hang at different places, but most of the >>> time it'll hang at "usb 2-1: new high-speed USB device number 2 using >>> ehci-platform". >>> >>> I've attached my kernel configuration. >>> >>> Here's the last screen my console showed: >>> >>> >>> [0.857803] ehci-platform 1c1c000.usb: EHCI Host Controller >>> [0.863428] ehci-platform 1c1c000.usb: new USB bus registered, >>> assigned bus number 2 >>> [0.871240] ehci-platform 1c1c000.usb: irq 22, io mem 0x01c1c000 >>> [0.893010] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00 >>> [0.899687] hub 2-0:1.0: USB hub found >>> [0.903476] hub 2-0:1.0: 1 port detected >>> [0.907701] ohci-platform 1c14400.usb: Generic Platform OHCI >>> controller >>> [0.914369] ohci-platform 1c14400.usb: new USB bus registered, >>> assigned bus number 3 >>> [0.922149] ohci-platform 1c14400.usb: irq 20, io mem 0x01c14400 >>> [0.953049] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >>> [0.965526] ata1.00: ATA-8: ST1000LM024 HN-M101MBB, 2AR10002, max >>> UDMA/133 >>> [0.972396] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth >>> 31/32) >>> [0.987092] ata1.00: configured for UDMA/133 >>> [0.991950] hub 3-0:1.0: USB hub found >>> [0.995759] hub 3-0:1.0: 1 port detected >>> [1.15] ohci-platform 1c1c400.usb: Generic Platform OHCI >>> controller >>> [1.008000] scsi 0:0:0:0: Direct-Access ATA ST1000LM024 HN-M >>> 2AR1 PQ: 0 ANSI: 5 >>> [1.017164] ohci-platform 1c1c400.usb: new USB bus registered, >>> assigned bus number 4 >>> [1.025424] ohci-platform 1c1c400.usb: irq 23, io mem 0x01c1c400 >>> [1.087535] hub 4-0:1.0: USB hub found >>> [1.091308] hub 4-0:1.0: 1 port detected >>> [1.095522] sunxi-rtc 1c20d00.rtc: setting system clock to 2010-01-01 >>> 00:01:57 UTC (1262304117) >>> [1.104382] ALSA device list: >>> [1.107366] No soundcards found. >>> [1.111339] Waiting for root device /dev/mmcblk0p2... >>> [1.123224] mmc0: host does not support reading read-only switch. >>> assuming write-enable. >>> [1.173033] usb 1-1: new high-speed USB device number 2 using >>> ehci-platform >>> [1.293012] mmc0: new high speed SDHC card at address e624 >>> [1.298821] mmcblk0: mmc0:e624 SU16G 14.8 GiB >>> [1.305399] mmcblk0: p1 p2 >>> [1.335541] hub 1-1:1.0: USB hub found >>> [1.339632] hub 1-1:1.0: 4 ports detected >>> [1.347376] EXT3-fs (mmcblk0p2): error: couldn't mount because of >>> unsupported optional features (240) >>> [1.357364] EXT2-fs (mmcblk0p2): error: couldn't mount because of >>> unsupported optional features (240) >>> [1.463026] usb 2-1: new high-speed USB device number 2 using >>> ehci-platform >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "linux-sunxi" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to linux-sunxi...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Mele a1000 hangs on boot using sunxi-devel, seems ehci-related
I had the problem as well where it wasn't able to locate the firmware and seemed to hang up on that. So I compiled the firmware into the kernel, but then it hung on the message "rtlwifi: wireless switch is on". So then I took the wireless device drivers out the kernel entirely (since I don't really need them), which leaves me with my original post. On Saturday, March 8, 2014 7:48:49 AM UTC-6, CodeKipper wrote: > > Hi, > I'm also currently battling suxi-devel on my Mele A2000. I'm getting a > little bit further than you but not by a great deal. Here is my .config > which I took from Hans. There are a couple of differences to get the > wireless bits compiled into the uImage. The rootfs I've been using is > Debian(which doesn't seem to locate the firmware) and in > http://pastebin.com/XNVxf03B which is the openwrt rootfs which does load > the firmware and then seems to hang. > Good luck with this, I can't play anymore today but let's us know if you > get any further. > CK > > > On 8 March 2014 08:56, Matthew Schneider > > wrote: > >> My mele a1000 hangs on boot using the sunxi-devel kernel tree. >> >> It seems like it'll sometimes hang at different places, but most of the >> time it'll hang at "usb 2-1: new high-speed USB device number 2 using >> ehci-platform". >> >> I've attached my kernel configuration. >> >> Here's the last screen my console showed: >> >> >> [0.857803] ehci-platform 1c1c000.usb: EHCI Host Controller >> [0.863428] ehci-platform 1c1c000.usb: new USB bus registered, >> assigned bus number 2 >> [0.871240] ehci-platform 1c1c000.usb: irq 22, io mem 0x01c1c000 >> [0.893010] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00 >> [0.899687] hub 2-0:1.0: USB hub found >> [0.903476] hub 2-0:1.0: 1 port detected >> [0.907701] ohci-platform 1c14400.usb: Generic Platform OHCI controller >> [0.914369] ohci-platform 1c14400.usb: new USB bus registered, >> assigned bus number 3 >> [0.922149] ohci-platform 1c14400.usb: irq 20, io mem 0x01c14400 >> [0.953049] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> [0.965526] ata1.00: ATA-8: ST1000LM024 HN-M101MBB, 2AR10002, max >> UDMA/133 >> [0.972396] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth >> 31/32) >> [0.987092] ata1.00: configured for UDMA/133 >> [0.991950] hub 3-0:1.0: USB hub found >> [0.995759] hub 3-0:1.0: 1 port detected >> [1.15] ohci-platform 1c1c400.usb: Generic Platform OHCI controller >> [1.008000] scsi 0:0:0:0: Direct-Access ATA ST1000LM024 HN-M >> 2AR1 PQ: 0 ANSI: 5 >> [1.017164] ohci-platform 1c1c400.usb: new USB bus registered, >> assigned bus number 4 >> [1.025424] ohci-platform 1c1c400.usb: irq 23, io mem 0x01c1c400 >> [1.087535] hub 4-0:1.0: USB hub found >> [1.091308] hub 4-0:1.0: 1 port detected >> [1.095522] sunxi-rtc 1c20d00.rtc: setting system clock to 2010-01-01 >> 00:01:57 UTC (1262304117) >> [1.104382] ALSA device list: >> [1.107366] No soundcards found. >> [1.111339] Waiting for root device /dev/mmcblk0p2... >> [1.123224] mmc0: host does not support reading read-only switch. >> assuming write-enable. >> [1.173033] usb 1-1: new high-speed USB device number 2 using >> ehci-platform >> [1.293012] mmc0: new high speed SDHC card at address e624 >> [1.298821] mmcblk0: mmc0:e624 SU16G 14.8 GiB >> [1.305399] mmcblk0: p1 p2 >> [1.335541] hub 1-1:1.0: USB hub found >> [1.339632] hub 1-1:1.0: 4 ports detected >> [1.347376] EXT3-fs (mmcblk0p2): error: couldn't mount because of >> unsupported optional features (240) >> [1.357364] EXT2-fs (mmcblk0p2): error: couldn't mount because of >> unsupported optional features (240) >> [1.463026] usb 2-1: new high-speed USB device number 2 using >> ehci-platform >> >> -- >> You received this message because you are subscribed to the Google Groups >> "linux-sunxi" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to linux-sunxi...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Flight Gear
Hi, I came to know that there is Fedora distribution that works on sunxi devices. I just wanted to know has anyone played Flight Gear in any of the sunxi devices ? If yes, how was the performance and gaming experience ? Regards, RM -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Looks to me like this is loading script.bin and uImage from nanda. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: [PATCH 6/7] regulator: AXP20x: Add support for regulators subsystem
On Fri, Mar 7, 2014 at 7:22 PM, Maxime Ripard
wrote:
> On Sat, Mar 01, 2014 at 05:45:51PM +0100, Carlo Caione wrote:
>> +static struct platform_driver axp20x_regulator_driver = {
>> + .probe = axp20x_regulator_probe,
>> + .remove = axp20x_regulator_remove,
>> + .driver = {
>> + .name = "axp20x-regulator",
>> + .owner = THIS_MODULE,
>> + },
>> +};
>> +
>> +static int __init axp20x_regulator_init(void)
>> +{
>> + return platform_driver_register(&axp20x_regulator_driver);
>> +}
>> +
>> +subsys_initcall(axp20x_regulator_init);
>
> Hmmm, really?
>
> I thought the AXP was only connected through I2C? How is that a
> platform device then?
Not really. It is plain wrong.
I'll fix it in v2.
Thanks,
--
Carlo Caione
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: [PATCH 2/7] mfd: AXP20x: Add bindings documentation
On Fri, Mar 07, 2014 at 07:13:00PM +0100, Maxime Ripard wrote:
> On Sat, Mar 01, 2014 at 05:45:47PM +0100, Carlo Caione wrote:
> > Bindings documentation for the AXP20x driver. In this file also two
> > sub-nodes (PEK and regulators) are documented.
> >
> > Signed-off-by: Carlo Caione
> > ---
> > Documentation/devicetree/bindings/mfd/axp20x.txt | 93
> >
> > 1 file changed, 93 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/axp20x.txt
> > b/Documentation/devicetree/bindings/mfd/axp20x.txt
> > new file mode 100644
> > index 000..ae3e3c4
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mfd/axp20x.txt
> > @@ -0,0 +1,93 @@
> > +* axp20x device tree bindings
> > +
> > +The axp20x family current members :-
> > +axp202 (X-Powers)
> > +axp209 (X-Powers)
> > +
> > +Required properties:
> > +- compatible : Should be "x-powers,axp202" or
> > "x-powers,axp209"
> > +- interrupt-controller : axp20x has its own internal IRQs
> > +- #interrupt-cells : Should be set to 1
> > +- interrupt-parent : The parent interrupt controller
> > +- interrupts : Interrupt specifiers for interrupt
> > sources
> > +- reg : The I2C slave address for the AXP chip
> > +- axp,system-power-controller : Telling whether or not this pmic is
> > + controlling the system power
> > +
> > +Sub-nodes:
> > +* regulators : Contain the regulator nodes. The regulators are bound using
> > + their name as listed here: dcdc2, dcdc3, ldo1, ldo2, ldo3,
> > + ldo4, ldo5.
> > + The bindings details of individual regulator device can be found
> > in:
> > + Documentation/devicetree/bindings/regulator/regulator.txt with
> > the
> > + exception of:
> > +
> > + - dcdc-freq : defines the work frequency of DC-DC in KHz
> > + (range: 750-1875)
> > + - dcdc-workmode : 1 for PWM mode, 0 for AUTO mode
>
> You don't seem to always set this. You should mention that it is
> optional, and which default value it has.
Fix in v2.
> > +
> > +* axp20x-pek : Power Enable Key
> > + - compatible: should be "x-powers,axp20x-pek"
>
> Why is this needed for?
>
> Plus, please don't use any generic, or pattern matching compatibles,
> but rather precise ones, so that if it is needed, we can add any quirk
> we want.
It is not needed, in fact I deleted it from dts. It is a refuse from the
previous submission. I'll fix it.
> > +Example:
> > +
> > +axp: axp20x@34 {
> > + reg = <0x34>;
> > + interrupt-parent = <&nmi_intc>;
> > + interrupts = <0 8>;
> > +
> > + axp,system-power-controller;
> > +
> > + compatible = "x-powers,axp209";
> > + interrupt-controller;
> > + #interrupt-cells = <1>;
> > +
> > + axp20x-pek {
> > + compatible = "x-powers,axp20x-pek";
> > + };
> > +
> > + regulators {
> > + dcdc-freq = "8";
> > +
> > + axp_dcdc2: dcdc2 {
> > + regulator-min-microvolt = <70>;
> > + regulator-max-microvolt = <2275000>;
> > + dcdc-workmode = <0>;
> > + regulator-always-on;
> > + };
> > +
> > + axp_dcdc3: dcdc3 {
> > + regulator-min-microvolt = <70>;
> > + regulator-max-microvolt = <350>;
> > + dcdc-workmode = <0>;
> > + regulator-always-on;
> > + };
> > +
> > + axp_ldo1: ldo1 {
> > + regulator-min-microvolt = <130>;
> > + regulator-max-microvolt = <130>;
> > + };
> > +
> > + axp_ldo2: ldo2 {
> > + regulator-min-microvolt = <180>;
> > + regulator-max-microvolt = <330>;
> > + regulator-always-on;
> > + };
> > +
> > + axp_ldo3: ldo3 {
> > + regulator-min-microvolt = <70>;
> > + regulator-max-microvolt = <350>;
> > + };
> > +
> > + axp_ldo4: ldo4 {
> > + regulator-min-microvolt = <125>;
> > + regulator-max-microvolt = <330>;
> > + };
> > +
> > + axp_ldo5: ldo5 {
> > + regulator-min-microvolt = <180>;
> > + regulator-max-microvolt = <330>;
> > + };
> > + };
> > +};
> > +
> > --
> > 1.8.3.2
> >
--
Carlo Caione
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: [PATCH 1/7] mfd: AXP20x: Add mfd driver for AXP20x PMIC
On Fri, Mar 07, 2014 at 07:09:36PM +0100, Maxime Ripard wrote:
> Hi,
>
> On Sat, Mar 01, 2014 at 05:45:46PM +0100, Carlo Caione wrote:
> > This patch introduces the preliminary support for PMICs X-Powers AXP202
> > and AXP209. The AXP209 and AXP202 are the PMUs (Power Management Unit)
> > used by A10, A13 and A20 SoCs and developed by X-Powers, a sister company
> > of Allwinner.
> >
> > The core enables support for two subsystems:
> > - PEK (Power Enable Key)
> > - Regulators
> >
> > Signed-off-by: Carlo Caione
> > ---
> > arch/arm/configs/sunxi_defconfig | 1 +
> > drivers/mfd/Kconfig | 12 ++
> > drivers/mfd/Makefile | 1 +
> > drivers/mfd/axp20x.c | 250
> > +++
> > include/linux/mfd/axp20x.h | 180
> > 5 files changed, 444 insertions(+)
> > create mode 100644 drivers/mfd/axp20x.c
> > create mode 100644 include/linux/mfd/axp20x.h
> >
> > diff --git a/arch/arm/configs/sunxi_defconfig
> > b/arch/arm/configs/sunxi_defconfig
> > index 3e2259b..f8aa7e6 100644
> > --- a/arch/arm/configs/sunxi_defconfig
> > +++ b/arch/arm/configs/sunxi_defconfig
> > @@ -52,6 +52,7 @@ CONFIG_GPIO_SYSFS=y
> > # CONFIG_HWMON is not set
> > CONFIG_WATCHDOG=y
> > CONFIG_SUNXI_WATCHDOG=y
> > +CONFIG_MFD_AXP20X=y
> > # CONFIG_USB_SUPPORT is not set
> > CONFIG_NEW_LEDS=y
> > CONFIG_LEDS_CLASS=y
>
> Please provide a separate patch for both sunxi_defconfig and
> multi_v7_defconfig.
Ok
> > diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> > index dd67158..33d38c4 100644
> > --- a/drivers/mfd/Kconfig
> > +++ b/drivers/mfd/Kconfig
> > @@ -59,6 +59,18 @@ config MFD_AAT2870_CORE
> > additional drivers must be enabled in order to use the
> > functionality of the device.
> >
> > +config MFD_AXP20X
> > + bool "X-Powers AXP20X"
> > + select MFD_CORE
> > + select REGMAP_I2C
> > + select REGMAP_IRQ
> > + depends on I2C=y
> > + help
> > + If you say Y here you get support for the AXP20X.
> > + This driver provides common support for accessing the device,
> > + additional drivers must be enabled in order to use the
> > + functionality of the device.
> > +
> > config MFD_CROS_EC
> > tristate "ChromeOS Embedded Controller"
> > select MFD_CORE
> > diff --git a/drivers/mfd/Makefile b/drivers/mfd/Makefile
> > index 8a28dc9..371020e 100644
> > --- a/drivers/mfd/Makefile
> > +++ b/drivers/mfd/Makefile
> > @@ -101,6 +101,7 @@ obj-$(CONFIG_PMIC_DA9052) += da9052-irq.o
> > obj-$(CONFIG_PMIC_DA9052) += da9052-core.o
> > obj-$(CONFIG_MFD_DA9052_SPI) += da9052-spi.o
> > obj-$(CONFIG_MFD_DA9052_I2C) += da9052-i2c.o
> > +obj-$(CONFIG_MFD_AXP20X) += axp20x.o
> >
> > obj-$(CONFIG_MFD_LP8788) += lp8788.o lp8788-irq.o
> >
> > diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
> > new file mode 100644
> > index 000..92e5b0f
> > --- /dev/null
> > +++ b/drivers/mfd/axp20x.c
> > @@ -0,0 +1,250 @@
> > +/*
> > + * axp20x.c - mfd core driver for the X-Powers AXP202 and AXP209
> > + *
> > + * Author: Carlo Caione
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 as
> > + * published by the Free Software Foundation.
> > + */
> > +
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +
> > +#define AXP20X_OFF 0x80
> > +
> > +static const struct regmap_range axp20x_writeable_ranges[] = {
> > + regmap_reg_range(AXP20X_DATACACHE(0), AXP20X_IRQ5_STATE),
> > + regmap_reg_range(AXP20X_DCDC_MODE, AXP20X_FG_RES),
> > +};
> > +
> > +static const struct regmap_range axp20x_volatile_ranges[] = {
> > + regmap_reg_range(AXP20X_IRQ1_EN, AXP20X_IRQ5_STATE),
> > +};
> > +
> > +static const struct regmap_access_table axp20x_writeable_table = {
> > + .yes_ranges = axp20x_writeable_ranges,
> > + .n_yes_ranges = ARRAY_SIZE(axp20x_writeable_ranges),
> > +};
> > +
> > +static const struct regmap_access_table axp20x_volatile_table = {
> > + .yes_ranges = axp20x_volatile_ranges,
> > + .n_yes_ranges = ARRAY_SIZE(axp20x_volatile_ranges),
> > +};
> > +
> > +static struct resource axp20x_pek_resources[] = {
> > + {
> > + .name = "PEK_DBR",
> > + .start = AXP20X_IRQ_PEK_RIS_EDGE,
> > + .end= AXP20X_IRQ_PEK_RIS_EDGE,
> > + .flags = IORESOURCE_IRQ,
> > + },
> > + {
> > + .name = "PEK_DBF",
> > + .start = AXP20X_IRQ_PEK_FAL_EDGE,
> > + .end= AXP20X_IRQ_PEK_FAL_EDGE,
> > + .flags = IORESOURCE_IRQ,
> > + },
> > +};
> > +
> > +static const struct regmap_config axp20x_regmap_config = {
> > + .reg_bits = 8,
> > + .val_bits = 8,
> > + .wr_table = &axp20x_writeable_table,
> > + .volatile_
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Hi Hunter, > 1> which board did you build for your tablet? make CROSS_COMPILE=arm-linux-gnueabihf- sun4i > 2> what modifications have you made, you said with header modifications? In the file include/configs/sun4i.h, I modified the CONFIG_BOOTCOMMANDdefine: #define CONFIG_BOOTCOMMAND \ "setenv bootargs " \ "root=/dev/nandb " \ "console=ttyS0,115200 "\ "console=tty0 "\ "rootfstype=ext4 " \ "ro " \ "quiet; " \ "fatload nand 0 0x4300 script.bin; " \ "fatload nand 0 0x4800 uImage; " \ "bootm 0x4800\0" > 3> Anything regarding DRAM settings needed? we needed a dram file in our sunxi branch. I didn't make any other modifications to u-boot. Please be aware that this is a hobby project for me :) > 4> where in the code does it indicate to configure where we put uImage and script.bin? Should be answered by 2, i.e. root directory of /dev/nandb in my case. I think the approach of hard-coding the locations and devices into u-boot is a bad one, but at the time I was investigating, it seemed to be the only one that worked. Although I read there were efforts made to unify the lichee-dev branch with its master. Kind regards, Timo On Mon, Mar 3, 2014 at 6:11 AM, hunter hu wrote: > > Hi Timo, > I had the same issue I could not make the NAND boot work. With the u-boot.bin from lichee-dev branch, my tablet stuck at the logo screen: > 1> which board did you build for your tablet? > 2> what modifications have you made, you said with header modifications? > 3> Anything regarding DRAM settings needed? we needed a dram file in our sunxi branch. > 4> where in the code does it indicate to configure where we put uImage and script.bin? > Great thanks in advance, > -Hunter > > On Tuesday, September 24, 2013 4:34:55 PM UTC-5, timo.s...@gmail.comwrote: >> >> Finally made it! >> >> While looking at the modifications I made for u-boot, I realized that script.bin and uImage belong to the same folder, i.e. the root folder of the bootloader partition. Moving uImage, the system now boots perfectly fine. >> >> Thanks for all your input! >> >> Timo > > -- > You received this message because you are subscribed to a topic in the Google Groups "linux-sunxi" group. > To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe. > To unsubscribe from this group and all of its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
