Re: [linux-sunxi] I2C driver on Linux 3.14 or above for A20
On Thu, 2014-11-06 at 11:28 -0800, Prajosh Premdas wrote: > Hi > > I am trying to interface Atmel AT24cxx on i2c bus for A20. I could > not find i2c drivers at https://github.com/linux-sunxi/linux-sunxi > on any of the 3.14 branches provided. > > Is there any drivers for the same? Just posted the question here to > not reinvent the wheel i2c driver for A20 is available in mainline kernel since version 3.13. There are plenty of examples in the arch/arm/boot/dts directory on how to add dts node for at24xx including one a10s device. > > Regards > Prajosh Premdas > > -- > 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.
[linux-sunxi] Re: Problem with ov7670 csi interface in kernel
[ 276.693761] [CSI]Welcome to CSI driver [220/1256] [ 276.696035] [CSI]csi_init [ 276.719384] [CSI_DEBUG]csi_probe [ 276.723024] [CSI_DEBUG]dev->ccm_cfg[0] = bf1b6f40 [ 276.726855] [CSI_DEBUG]dev->ccm_cfg[0]->ccm = ov7670 [ 276.730383] [CSI_DEBUG]dev->ccm_cfg[0]->twi_id = 1 [ 276.734155] [CSI_DEBUG]dev->ccm_cfg[0]->i2c_addr = 42 [ 276.738635] [CSI_DEBUG]dev->ccm_cfg[0]->interface = 0 [ 276.742091] [CSI_DEBUG]dev->ccm_cfg[0]->vflip = 1 [ 276.745528] [CSI_DEBUG]dev->ccm_cfg[0]->hflip = 0 [ 276.750541] [CSI_DEBUG]dev->ccm_cfg[0]->iovdd_str = axp20_pll [ 276.754144] [CSI_DEBUG]dev->ccm_cfg[0]->avdd_str = [ 276.760647] [CSI_DEBUG]dev->ccm_cfg[0]->dvdd_str = [ 276.764425] [CSI_DEBUG]dev->ccm_cfg[0]->flash_pol = 1 [ 276.796332] [CSI]registered sub device,input_num = 0 [ 276.804659] [CSI_DEBUG][OV7670]CSI_SUBDEV_CMD_GET_INFO [ 276.809236] [CSI_DEBUG][OV7670]ccm_info.mclk=19bfcc0 [ 276.809260] [ 276.816397] [CSI_DEBUG][OV7670]ccm_info.vref=0 [ 276.816413] [ 276.819913] [CSI_DEBUG][OV7670]ccm_info.href=1 [ 276.819924] [ 276.837306] [CSI_DEBUG][OV7670]ccm_info.clock=1 [ 276.837327] [ 276.840914] [CSI_DEBUG][OV7670]ccm_info.iocfg=1 [ 276.840926] [ 276.845028] [CSI_DEBUG][OV7670]CSI_SUBDEV_CMD_SET_INFO [ 276.849680] [CSI_DEBUG][OV7670]ccm_info.mclk=19bfcc0 [ 276.849696] [ 276.853196] [CSI_DEBUG][OV7670]ccm_info.vref=0 [ 276.853207] [ 276.857098] [CSI_DEBUG][OV7670]ccm_info.href=1 [ 276.857113] [ 276.860695] [CSI_DEBUG][OV7670]ccm_info.clock=1 [ 276.860707] [ 276.864286] [CSI_DEBUG][OV7670]ccm_info.iocfg=0 [ 276.864297] [ 276.869470] axp20_ldo3: Failed to create debugfs directory [ 276.873253] [CSI_DEBUG]dev->ccm_cfg[0]->sd = eebdcc00 [ 276.877921] [CSI_DEBUG]dev->ccm_cfg[0]->ccm_info = bf1b6fdc [ 276.883421] [CSI_DEBUG]dev->ccm_cfg[0]->ccm_info.iocfg = 0 [ 276.888294] [CSI_DEBUG]dev->ccm_cfg[0]->ccm_info.vref = 0 [ 276.892989] [CSI_DEBUG]dev->ccm_cfg[0]->ccm_info.href = 1 [ 276.897566] [CSI_DEBUG]dev->ccm_cfg[0]->ccm_info.clock = 1 [177/1256] [ 276.902558] [CSI_DEBUG]dev->ccm_cfg[0]->ccm_info.mclk = 2700 [ 276.906934] [CSI_DEBUG]dev->ccm_cfg[0]->iovdd = e3a72380 [ 276.910892] [CSI_DEBUG]dev->ccm_cfg[0]->avdd = (null) [ 276.914826] [CSI_DEBUG]dev->ccm_cfg[0]->dvdd = (null) [ 276.919331] [CSI_DEBUG][OV7670]CSI_SUBDEV_CMD_SET_INFO [ 276.923356] [CSI_DEBUG][OV7670]ccm_info.mclk=19bfcc0 [ 276.923368] [ 276.927151] [CSI_DEBUG][OV7670]ccm_info.vref=0 [ 276.927163] [ 276.930674] [CSI_DEBUG][OV7670]ccm_info.href=1 [ 276.930686] [ 276.934264] [CSI_DEBUG][OV7670]ccm_info.clock=1 [ 276.934275] [ 276.938297] [CSI_DEBUG][OV7670]ccm_info.iocfg=0 [ 276.938310] [ 276.946101] [CSI]V4L2 device registered as video0 [ 276.953544] [CSI_DEBUG]csi_open [ 276.957822] [ccu-err] clk_enable: invalid handle [ 276.961944] [CSI_DEBUG][OV7670]CSI_SUBDEV_CMD_SET_INFO [ 276.967603] [CSI_DEBUG][OV7670]ccm_info.mclk=19bfcc0 [ 276.967619] [ 276.971865] [CSI_DEBUG][OV7670]ccm_info.vref=0 [ 276.971880] [ 276.975427] [CSI_DEBUG][OV7670]ccm_info.href=1 [ 276.975438] [ 276.980193] [CSI_DEBUG][OV7670]ccm_info.clock=1 [ 276.980208] [ 276.983843] [CSI_DEBUG][OV7670]ccm_info.iocfg=0 [ 276.983856] [ 276.988274] [CSI_DEBUG][OV7670]CSI_SUBDEV_PWR_ON [ 277.306225] [CSI_DEBUG][OV7670]CSI_SUBDEV_STBY_ON [ 277.786294] [CSI_DEBUG][OV7670]CSI_SUBDEV_STBY_OFF [ 277.955631] [CSI_DEBUG][OV7670]ov7670_init [ 278.017792] [CSI]sensor initial success when csi open! [ 278.055025] [CSI_DEBUG]csi_close [ 278.058694] [ccu-err] clk_disable: invalid handle [ 278.062364] [CSI_DEBUG][OV7670]CSI_SUBDEV_STBY_ON [ 298.074192] [CSI_DEBUG]csi_open [ 298.077853] [ccu-err] clk_enable: invalid handle [ 298.082197] [CSI_DEBUG][OV7670]CSI_SUBDEV_CMD_SET_INFO [ 298.086208] [CSI_DEBUG][OV7670]ccm_info.mclk=19bfcc0 [ 298.086212] [ 298.089738] [CSI_DEBUG][OV7670]ccm_info.vref=0 [134/1256] [ 298.089742] [ 298.093225] [CSI_DEBUG][OV7670]ccm_info.href=1 [ 298.093229] [ 298.096818] [CSI_DEBUG][OV7670]ccm_info.clock=1 [ 298.096822] [ 298.100391] [CSI_DEBUG][OV7670]ccm_info.iocfg=0 [ 298.100395] [ 298.103977] [CSI_DEBUG][OV7670]CSI_SUBDEV_PWR_ON [ 298.426208] [CSI_DEBUG][OV7670]CSI_SUBDEV_STBY_ON [ 298.906289] [CSI_DEBUG][OV7670]CSI_SUBDEV_STBY_OFF [ 299.075592] [CSI_DEBUG][OV7670]ov7670_init [ 299.139665] [CSI]sensor initial success when csi open! [ 299.194242] [CSI_ERR]v4l2 sub device queryctrl error! [ 299.200236] [CSI_ERR]v4l2 sub device queryctrl error! [ 299.204595] [CSI_ERR]v4l2 sub device queryctrl error! [ 299.208886] [CSI_ERR]v4l2 sub device queryctrl error! [ 299.213039] [CSI_ERR]v4l2 sub device queryctrl error! [ 299.217199] [CSI_ERR]v4l2 sub device queryctrl error
[linux-sunxi] Problem with ov7670 csi interface in kernel
I clone a kernel source code from[url] https://github.com/linux-sunxi/linux-sunxi/tree/sunxi-3.4/[/url] Everything worked fine except CSI. I connect a OV7670 camera to CSI1 and make sure my fex config is right ( because i tested it on Android ). I2C communication with OV7670 is working and test application can get device id and other information from the hardware. When I try to capture a image from OV7670 using "fswebcam", it only got a image which is full of green pixel. I have found many test application to capture a image, but no one make sense on it. The strange thing is, when I flash a Android image to cubieboard2, the camera works perfectly. Anyone have a advice on it? Sorry for my poor english... -- 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: Kurio 7S and boot linux (Debian...) sdcard... how??
Hello Piotr, I see this tablet has a Focaltech touchscreen IC, and it's supported in the kernel 3.4, have you successfully loaded the driver for it? Thanks. On Thursday, November 6, 2014 9:39:44 PM UTC-3, Piotr Kopeć wrote: > > > ok I have run Debian (Kali linux) and Tizen just do not know how to solve > this USB0 is can someone have an idea > -- 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] A20 Booting without uboot
Hi John
There was solved this problem
void (*kernel_entry)(int zero, int arch, uint params);
In this function sun7i arch number is 3893 and sun4i is 3495.
So I used sun7i arch number in the kernel_entry function.
__inf("jump to kernel\n");
wBoot_jump_to_linux(0, 3893, para_addr, kernal_addr);
Thanks for your help again.
Best Regards,
Ryang
--
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: Regarding the Allwinner tablets
Hi Rodolfo, linux-sunxi cc'd. On Fri, Nov 7, 2014 at 12:46 PM, Rodolfo Bonnin wrote: > Hello Julian, Firstly, please do _not_ contact me off list. I do _not_ do private consulting, and if I can help you, it'd be better for everyone if the answer is publicly available, i.e. in the list's archives / on the wiki. > I've seen some posts by you on the allwinner mailing list, just wanted to > know, if you have information about the touch screen IC of the tablets > you've reviewed, is there any information available? You'll be much better off searching the wiki / looking at the code. This page might help: http://linux-sunxi.org/Touchscreen I'm yet to get the touch screen working on the one tablet I have that I can run custom Linux on, however there appears to be an upstream driver for it. Thanks, -- Julian Calaby Email: julian.cal...@gmail.com Profile: http://www.google.com/profiles/julian.calaby/ -- 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] A20 Booting without uboot
Hi, Jhon Thanks for your help. Of course you are right. "address = 0x4a00" is my fault. I used bImage and original bImage address is 0x40008000. I have changed address for testing. [segment] img_name = c:\linux\bImage img_size = 0x200 img_base = 0x40008000 But result is the same. [ 0.420] load kernel start [ 0.612] load kernel successed [ 0.612] start address = 0x40008000 [ 0.614] ERR: display driver not open yet [ 0.618] jump to kernel -- 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] Tablets with supported touchscreen IC
Thanks John, it's a good start, I think it would also be useful to have first hand reports from current users of devices not listed there, or IC related info, any help will be appreciated. Thanks again. On Thursday, November 6, 2014 9:50:24 PM UTC-3, Jhon Yi wrote: > > May here is what you are looking for? -> > http://linux-sunxi.org/Category:Devices > > 2014-11-07 8:08 GMT+08:00 >: > > Hello All, > > > > I've working in a project using allwinner based tablets, but the > problematic > > point has been to get the touchscreen drivers loading and working, and > the > > lack of documentation about which touchscreen IC they include. > > I'd like to know if you have any recomendation of a tablet brand and > model > > with a dual core or greater allwinner soc, and a touchscreen driver not > > requiring any firmware extraction from the android kernel, or any > additional > > device specific steps, compiling the kernel driver and some simple > > configuration is ok. > > Many thanks in advance. > > > > -- > > 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] Tablets with supported touchscreen IC
May here is what you are looking for? ->http://linux-sunxi.org/Category:Devices 2014-11-07 8:08 GMT+08:00 : > Hello All, > > I've working in a project using allwinner based tablets, but the problematic > point has been to get the touchscreen drivers loading and working, and the > lack of documentation about which touchscreen IC they include. > I'd like to know if you have any recomendation of a tablet brand and model > with a dual core or greater allwinner soc, and a touchscreen driver not > requiring any firmware extraction from the android kernel, or any additional > device specific steps, compiling the kernel driver and some simple > configuration is ok. > Many thanks in advance. > > -- > 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] A20 Booting without uboot
Hi, Ryang, In order to boot the kernel, you should also make sure your kernel is compiled to start at the address you given(0x40008000) and find the script.bin at the address you given(0x4300). These addresses are all defined in the kernel config file. Since boot.axf is not designed to boot uImage, you should compile zImage or bzimage kernel instead. Your debug output showed that the boot.axf trying to start kernel at "address = 0x4a00", make sure your kernel is compiled right. Regards Jhon 2014-11-06 18:15 GMT+08:00 Ryang HaeDong : > Hi, Jhon > > I think you mean following config. > Boot options -> Kernel command line type -> Always use the default kernel > command string > Of course I tested this option but result is the same. > > sunxi linux normal boot order is following: > boot0-> boot1 -> boot.axf -> uboot -> linux kernel > But I just want to booting below order without uboot. > boot0-> boot1 -> boot.axf -> kernel > > Please take again > Kind Regards > > -- > 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] Re: Kurio 7S and boot linux (Debian...) sdcard... how??
ok I have run Debian (Kali linux) and Tizen just do not know how to solve this USB0 is can someone have an idea -- 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] Tablets with supported touchscreen IC
Hello All, I've working in a project using allwinner based tablets, but the problematic point has been to get the touchscreen drivers loading and working, and the lack of documentation about which touchscreen IC they include. I'd like to know if you have any recomendation of a tablet brand and model with a dual core or greater allwinner soc, and a touchscreen driver not requiring any firmware extraction from the android kernel, or any additional device specific steps, compiling the kernel driver and some simple configuration is ok. Many thanks in advance. -- 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] I2C driver on Linux 3.14 or above for A20
Hi I am trying to interface Atmel AT24cxx on i2c bus for A20. I could not find i2c drivers at https://github.com/linux-sunxi/linux-sunxi on any of the 3.14 branches provided. Is there any drivers for the same? Just posted the question here to not reinvent the wheel Regards Prajosh Premdas -- 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 v4 0/5] simplefb: add clock handling code
Hi, On 11/06/2014 03:18 PM, Tomi Valkeinen wrote: > On 31/10/14 10:15, Tomi Valkeinen wrote: >> Hi Hans, >> >> On 22/10/14 19:45, Hans de Goede wrote: >> >>> -We will add a clocks property to the simplefb devicetree bindings, so >>> that u-boot setup framebuffers passed to the kernel (for early console >>> support) can properly list the clocks used, and simplefb can claim them to >>> avoid them getting turned off, thereby breaking the early console >> >> Perhaps this has been discussed earlier, but I started to wonder if >> managing clocks is enough. >> >> What about regulators (to power the LCD), gpios (to keep the LCD >> enabled) and pinctrl (for video signals)? I guess any those could be >> reset by the kernel if no driver uses them. > > Hans, ping. Have these been already discussed? Yes, and I already responded to your original mail on this on Oct. 31th, for some reason my mail client drops you from the CC, when I do a reply-to-all to one of your mails (I've added you manually this time). My replies did go to simple...@vger.kernel.org .I'll forward my 2 mails on this to you. 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.
[linux-sunxi] Re: [PATCH v5 4/4] crypto: Add Allwinner Security System crypto accelerator
On Thu, Nov 06, 2014 at 03:26:33PM +0100, Maxime Ripard wrote: > > But you still haven't explain why the driver, while it doesn't handle > the user space buffer at any time, should be worried that the data the > framework has given him are actually mapped. Encryption is used by IPsec and SKBs can be allocated in highmem. algif also exposes all ciphers to user-space memory which can also be in highmem. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- 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 v5 4/4] crypto: Add Allwinner Security System crypto accelerator
On Mon, Nov 03, 2014 at 06:35:28PM +0800, Herbert Xu wrote: > On Mon, Nov 03, 2014 at 10:34:46AM +0100, Maxime Ripard wrote: > > What I mean is that since you are saying that drivers should do the > > kmap themselves, then *all* of the drivers are broken if they are not > > using it. And all of them are missing this kmap. > > kmap is used by the software implementations to map the input/output > into virtual address space. Drivers typically use DMA and operate > on physical addresses so they don't need kmap. Yes, plus all memory allocated with GFP_KERNEL is in lowmem. But you still haven't explain why the driver, while it doesn't handle the user space buffer at any time, should be worried that the data the framework has given him are actually mapped. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com signature.asc Description: Digital signature
[linux-sunxi] Re: [PATCH v4 0/5] simplefb: add clock handling code
On 31/10/14 10:15, Tomi Valkeinen wrote: > Hi Hans, > > On 22/10/14 19:45, Hans de Goede wrote: > >> -We will add a clocks property to the simplefb devicetree bindings, so >> that u-boot setup framebuffers passed to the kernel (for early console >> support) can properly list the clocks used, and simplefb can claim them to >> avoid them getting turned off, thereby breaking the early console > > Perhaps this has been discussed earlier, but I started to wonder if > managing clocks is enough. > > What about regulators (to power the LCD), gpios (to keep the LCD > enabled) and pinctrl (for video signals)? I guess any those could be > reset by the kernel if no driver uses them. Hans, ping. Have these been already discussed? Tomi signature.asc Description: OpenPGP digital signature
[linux-sunxi] Re: [PATCH v5 4/4] crypto: Add Allwinner Security System crypto accelerator
On Sun, Oct 19, 2014 at 04:16:22PM +0200, LABBE Corentin wrote:
> Add support for the Security System included in Allwinner SoC A20.
> The Security System is a hardware cryptographic accelerator that support
> AES/MD5/SHA1/DES/3DES/PRNG algorithms.
>
> Signed-off-by: LABBE Corentin
OK this is much better. However it seems that export/import
is still missing?
> + src_addr = kmap_atomic(sg_page(in_sg)) + in_sg->offset;
> + if (src_addr == NULL) {
> + dev_err(ss->dev, "kmap_atomic error for src SG\n");
> + writel(0, ss->base + SS_CTL);
> + mutex_unlock(&ss->lock);
I overlooked this the last time around. You cannot use mutexes
here as you can be called from softirq context so you need spin
locks.
Cheers,
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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][RFC] Add standalone driver for the A20 Soc TP embedded temperature sensor
Christian Ege wrote: > Am 05.11.2014 12:44 schrieb : >> Does anyone have a clue how the A20's CHOP_TEMP_EN register (according to >> the A20's >> user manual: "Chop temperature calibration enable: 0: Disable, 1: Enable") >> can be read/set? > > For read write access from user space you can try to use devmem2 with the > address given > in the user manual. > > http://manpages.ubuntu.com/manpages/natty/man1/devmem2.1.html Thx, will give it a try this evening. In the meantime I realized that it's bit 7 of the touchpanel's TP_CTRL1 register so when sunxi-dbgreg.ko is loaded I should succeed with echo 'f1c25004' > /sys/devices/virtual/misc/sunxi-dbgreg/rw/read; Corentin's code in this module as well as the sunxi-dbgreg-workaround I use set bit 4 to 1 but leave bit 7 untouched. With CHOP_TEMP_EN enabled I get a whopping 25°C lower reported by the TP controller inside the A20 with an attached heatsink compared to the very same A20 without a heatsink a few minutes before. I'll report back what can be read when CHOP_TEMP_EN is disabled. -- 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] A20 Booting without uboot
Hi, Jhon I think you mean following config. Boot options -> Kernel command line type -> Always use the default kernel command string Of course I tested this option but result is the same. sunxi linux normal boot order is following: boot0-> boot1 -> boot.axf -> uboot -> linux kernel But I just want to booting below order without uboot. boot0-> boot1 -> boot.axf -> kernel Please take again Kind Regards -- 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/6] clk: sunxi: Add support for sun9i a80 usb clocks and resets
On Thu, Nov 6, 2014 at 4:54 PM, Maxime Ripard
wrote:
> On Thu, Nov 06, 2014 at 10:09:27AM +0800, Chen-Yu Tsai wrote:
>> >> >> +static void __init sun9i_a80_usb_mod_setup(struct device_node *node)
>> >> >> +{
>> >> >> + /* AHB1 gate must be enabled to access registers */
>> >> >> + struct clk *ahb = of_clk_get(node, 0);
>> >> >> +
>> >> >> + WARN_ON(IS_ERR(ahb));
>> >> >> + clk_prepare_enable(ahb);
>> >> >
>> >> > H. That look off.
>> >> >
>> >> > Why do you need the clock to be enabled all the time? Isn't the CCF
>> >> > already taking care of enabling the parent clock whenever it needs to
>> >> > access any register?
>> >>
>> >> There are also resets in the same block. That and I couldn't get it
>> >> working without enabling the clock beforehand.
>> >
>> > Ah, right.
>> >
>> > What happens if you just enable and disable the clocks in the
>> > reset_assert and reset_deassert right before and after accessing the
>> > registers?
>>
>> That doesn't work either. I forgot to mention that most of the clock
>> gates have the peripheral pll as their parent, not the ahb clock gate.
>
> Why it doesn't work? The clock needs more time to stabilize? The reset
> line is set back in reset if the clocks are disabled?
Let me clarify, what you proposed will work for the resets.
However the clock gates won't work if we use the generic clk-gate driver.
The problem is most of the gates don't have the ahb gate as their parent,
but pll4 (peripheral pll). When we enable the clock, the ahb gate isn't
its parent, and doesn't get enabled as a result. This is especially true
for the usb phy clocks: all of them use pll4 as their parent.
I think this is a better representation of the hardware, but without
documents this is really just a guess.
As a whole, I think enabling the clock gate at the beginning is simpler.
ChenYu
--
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/6] clk: sunxi: Add support for sun9i a80 usb clocks and resets
On Thu, Nov 06, 2014 at 10:09:27AM +0800, Chen-Yu Tsai wrote:
> >> >> +static void __init sun9i_a80_usb_mod_setup(struct device_node *node)
> >> >> +{
> >> >> + /* AHB1 gate must be enabled to access registers */
> >> >> + struct clk *ahb = of_clk_get(node, 0);
> >> >> +
> >> >> + WARN_ON(IS_ERR(ahb));
> >> >> + clk_prepare_enable(ahb);
> >> >
> >> > H. That look off.
> >> >
> >> > Why do you need the clock to be enabled all the time? Isn't the CCF
> >> > already taking care of enabling the parent clock whenever it needs to
> >> > access any register?
> >>
> >> There are also resets in the same block. That and I couldn't get it
> >> working without enabling the clock beforehand.
> >
> > Ah, right.
> >
> > What happens if you just enable and disable the clocks in the
> > reset_assert and reset_deassert right before and after accessing the
> > registers?
>
> That doesn't work either. I forgot to mention that most of the clock
> gates have the peripheral pll as their parent, not the ahb clock gate.
Why it doesn't work? The clock needs more time to stabilize? The reset
line is set back in reset if the clocks are disabled?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
signature.asc
Description: Digital signature
[linux-sunxi] Re: [PATCH v2 0/3] ARM: sun8i: Add DMA controller support
On Thu, Nov 06, 2014 at 03:54:35PM +0800, Chen-Yu Tsai wrote: > > The patches look fine to me so I tried applying them but they fail to apply, > > can you please rebase these two and resend > > Hi Vinod, > > Could you publish an updated slave-dma/next branch? Currently I see it at > v3.18-rc1. And the series rebases cleanly onto it with no differences. > > I'm guessing some of Maxime's cleanup work is the source of conflict. Its pushed now.. -- ~Vinod -- 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.
