Re: [linux-sunxi] Chipone icn85xx TS polling driver
Hi, Sorry for brief answer - built in did not work for me. As minimum in case of Chuwi Vi10 icn8528 you should load firmware with all related to this stuff + irq mode is still under development, under standard things irg/gpio was not getted automatically and there is no enough info at the moment to use irq mode. Regarding whether communication part are the same - I do not compare, from the 1st look - looks different, not sure, have no time at the moment to compare. Regards, Serge. On Wednesday, May 4, 2016 at 4:26:02 AM UTC, Priit Laes wrote: > > On Tue, 2016-05-03 at 14:30 -0700, sergk...@gmail.com > wrote: > > Hi all, > > ;-) At least I am releasing my icn85xx (tested on icn8528 on Chuvi > > Vi10, Baytrail) kernel space driver. > > It is unfortunately polling mode, but at the moment I am happy with > > it and have no enough time to dig in with irq mode. > > https://gitlab.com/SergK/icn85xx/tree/master > > > Are there any protocol differences between 8318 (already present in > mainline kernel) and 85xx? > > > My special thanks for their helpto: > > Gregor Riepl > > Mika Westerberg > > linux-input > > > > Kind regards, > >Serge Kolotylo. > > -- > > 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] Re: [PATCH 1/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
On Tue, 2016-05-03 at 17:52 +0200, Olliver Schinagl wrote: > Hey all, > > On 03-05-16 17:02, christo.ra...@gmail.com wrote: > > On Tuesday, May 3, 2016 at 4:14:41 PM UTC+3, Maxime Ripard wrote: > > > Hi, > > > > > > On Tue, May 03, 2016 at 4:12:06 PM UTC+3, Christo Radev wrote: > > > > Hi to All, > > > > > > > > I have already solved and tested this issue on Armbian build. > > > > Find > > > > patches for both legacy (3.4.111) and mainline (4.5.2) kernels > > > > on: > > > > http://forum.armbian.com/index.php/topic/853-armbian-customizat > > > > ion/page-2#entry7494 > > > > There it is also described how to do eMMC bootable and much > > > > more. > > > > > > > > About the board - Olimex already sold all 3 kinds after > > > > migration to > > > > their HW rev. E. One have to specify Lime2-eMMC as > > > > A20-Olinuxino-Lime2-eMMC instead of their old 2 options > > > > A20-Olinuxino-Lime2(-4GB). > > > Interesting, you have a link to that device? I guess, it is this one: https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-LIME2-eMMC/ open-source-hardware > > > > > > Thanks, > > > Maxime > > > > > > -- > > > Maxime Ripard, Free Electrons > > > Embedded Linux, Kernel and Android engineering > > > http://free-electrons.com > > I have really 2 boards delivered by their local distributor. > > > > Unfortunately, they do not update their site. Use the link for NAND > > option: > > https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4 > > GB/open-source-hardware > > There you can find Users Manual where it is described that eMMC > > option is available from HW rev. D. The schematic for HW rev. E is > > also available on their repository: > > https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuX > > ino-LIME2 > > > > On the board both 4GB NAND and eMMC Flash chips can be placed > > alternatively on the same place. There is difference in some other > > components as well. > > > > If one want to order it from the site probably has to order A20 > > -Olinuxino-Lime2-4GB with note that eMMC option is required. The > > price is the same. > Sorry for the late reply, but yeah the board exists, we asked Olimex > to > develop the eMMC variant for us. I currently have a dozen or so on my > desk :) > > I don't know when Olimex will update their webshop with the new > designs, > but they simply might not have enough eMMC chips available yet? > -- 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] Chipone icn85xx TS polling driver
On Tue, 2016-05-03 at 14:30 -0700, sergk.ad...@gmail.com wrote: > Hi all, > ;-) At least I am releasing my icn85xx (tested on icn8528 on Chuvi > Vi10, Baytrail) kernel space driver. > It is unfortunately polling mode, but at the moment I am happy with > it and have no enough time to dig in with irq mode. > https://gitlab.com/SergK/icn85xx/tree/master Are there any protocol differences between 8318 (already present in mainline kernel) and 85xx? > My special thanks for their helpto: > Gregor Riepl > Mika Westerberg > linux-input > > Kind regards, >Serge Kolotylo. > -- > 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] Chipone icn85xx TS polling driver
Hi all, ;-) At least I am releasing my icn85xx (tested on icn8528 on Chuvi Vi10, Baytrail) kernel space driver. It is unfortunately polling mode, but at the moment I am happy with it and have no enough time to dig in with irq mode. https://gitlab.com/SergK/icn85xx/tree/master My special thanks for their helpto: Gregor Riepl Mika Westerberglinux-input Kind regards, Serge Kolotylo. -- 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/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
Hi Oliver, Nice to hear it. Thanks to Olimex I also have 2 board and make series of tests and customization effort based on Armbian build scripts. I have passed through patching and customization of U-Boot, Kernel (both legacy 3.4.111 and mainline 4.5.2), Debian Jessie as FS, RPI Monitor etc. All my steps are described in a couple of posts on Armbian forum where the main one is: http://forum.armbian.com/index.php/topic/853-armbian-customization There one can find all patches I have used, step by step instruction on how to install and boot from eMMC, SD/MMC, SATA, some measurements and tests. One of the useful things in my opinion is U-Boot script to boot from available boot devices in given order and usage of user button for emergency boot from eMMC or SD/MMC. Of course, my customization effort is not finished so some help in USB OTG activation and read-only rootfs preparation will be welcome. Any help or notes on how the things can be done in a better way will be appreciated as well. Regards Chris On Tuesday, May 3, 2016 at 6:52:15 PM UTC+3, Olliver Schinagl wrote: > > Hey all, > > On 03-05-16 17:02, christ...@gmail.com wrote: > > On Tuesday, May 3, 2016 at 4:14:41 PM UTC+3, Maxime Ripard wrote: > >> Hi, > >> > >> On Tue, May 03, 2016 at 4:12:06 PM UTC+3, Christo Radev wrote: > >>> Hi to All, > >>> > >>> I have already solved and tested this issue on Armbian build. Find > >>> patches for both legacy (3.4.111) and mainline (4.5.2) kernels on: > >>> > http://forum.armbian.com/index.php/topic/853-armbian-customization/page-2#entry7494 > > >>> There it is also described how to do eMMC bootable and much more. > >>> > >>> About the board - Olimex already sold all 3 kinds after migration to > >>> their HW rev. E. One have to specify Lime2-eMMC as > >>> A20-Olinuxino-Lime2-eMMC instead of their old 2 options > >>> A20-Olinuxino-Lime2(-4GB). > >> Interesting, you have a link to that device? > >> > >> Thanks, > >> Maxime > >> > >> -- > >> Maxime Ripard, Free Electrons > >> Embedded Linux, Kernel and Android engineering > >> http://free-electrons.com > > I have really 2 boards delivered by their local distributor. > > > > Unfortunately, they do not update their site. Use the link for NAND > option: > > > https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4GB/open-source-hardware > > > There you can find Users Manual where it is described that eMMC option > is available from HW rev. D. The schematic for HW rev. E is also available > on their repository: > > > https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 > > > > On the board both 4GB NAND and eMMC Flash chips can be placed > alternatively on the same place. There is difference in some other > components as well. > > > > If one want to order it from the site probably has to order > A20-Olinuxino-Lime2-4GB with note that eMMC option is required. The price > is the same. > Sorry for the late reply, but yeah the board exists, we asked Olimex to > develop the eMMC variant for us. I currently have a dozen or so on my > desk :) > > I don't know when Olimex will update their webshop with the new designs, > but they simply might not have enough eMMC chips available yet? > > -- 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] [PATCH 2/2] ARM: sun7i: dt: Add pll3 and pll7 clocks
Enable pll3 and pll7 clocks that are needed by display clocks.
---
arch/arm/boot/dts/sun7i-a20.dtsi | 41
1 file changed, 41 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi b/arch/arm/boot/dts/sun7i-a20.dtsi
index bf5d056..2688512 100644
--- a/arch/arm/boot/dts/sun7i-a20.dtsi
+++ b/arch/arm/boot/dts/sun7i-a20.dtsi
@@ -187,6 +187,15 @@
clock-output-names = "osc24M";
};
+ osc3M: osc3M_clk {
+ #clock-cells = <0>;
+ compatible = "fixed-factor-clock";
+ clock-div = <8>;
+ clock-mult = <1>;
+ clocks = <&osc24M>;
+ clock-output-names = "osc3M";
+ };
+
osc32k: clk@0 {
#clock-cells = <0>;
compatible = "fixed-clock";
@@ -211,6 +220,22 @@
"pll2-4x", "pll2-8x";
};
+ pll3: clk@01c20010 {
+ #clock-cells = <0>;
+ compatible = "allwinner,sun4i-a10-pll3-clk";
+ reg = <0x01c20010 0x4>;
+ clock = <&osc3M>;
+ clock-output-names = "pll3";
+};
+
+ pll3x2: pll3x2_clk {
+ #clock-cells = <0>;
+ compatible = "fixed-factor-clock";
+ clock-div = <1>;
+ clock-mult = <2>;
+ clock-output-names = "pll3-2x";
+ };
+
pll4: clk@01c20018 {
#clock-cells = <0>;
compatible = "allwinner,sun7i-a20-pll4-clk";
@@ -236,6 +261,22 @@
"pll6_div_4";
};
+ pll7: clk@01c20030 {
+ #clock-cells = <0>;
+ compatible = "allwinner,sun4i-a10-pll3-clk";
+ reg = <0x01c20030 0x4>;
+ clock = <&osc3M>;
+ clock-output-names = "pll7";
+};
+
+ pll7x2: pll7x2_clk {
+ #clock-cells = <0>;
+ compatible = "fixed-factor-clock";
+ clock-div = <1>;
+ clock-mult = <2>;
+ clock-output-names = "pll7-2x";
+ };
+
pll8: clk@01c20040 {
#clock-cells = <0>;
compatible = "allwinner,sun7i-a20-pll4-clk";
--
2.8.1
--
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] [PATCH 1/2] ARM: sun4i: dt: Add pll3 and pll7 clocks
Enable pll3 and pll7 clocks that are needed to drive display clocks.
Signed-off-by: Priit Laes
---
arch/arm/boot/dts/sun4i-a10.dtsi | 44
1 file changed, 44 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi b/arch/arm/boot/dts/sun4i-a10.dtsi
index 268a150..c893744 100644
--- a/arch/arm/boot/dts/sun4i-a10.dtsi
+++ b/arch/arm/boot/dts/sun4i-a10.dtsi
@@ -184,6 +184,15 @@
clock-output-names = "osc24M";
};
+ osc3M: osc3M_clk {
+ compatible = "fixed-factor-clock";
+ #clock-cells = <0>;
+ clock-div = <8>;
+ clock-mult = <1>;
+ clocks = <&osc24M>;
+ clock-output-names = "osc3M";
+ };
+
osc32k: clk@0 {
#clock-cells = <0>;
compatible = "fixed-clock";
@@ -208,6 +217,24 @@
"pll2-4x", "pll2-8x";
};
+ pll3: clk@01c20010 {
+ #clock-cells = <0>;
+ compatible = "allwinner,sun4i-a10-pll3-clk";
+ reg = <0x01c20010 0x4>;
+ clocks = <&osc3M>;
+ clock-output-names = "pll3";
+ };
+
+ pll3x2: pll3x2_clk {
+ compatible = "fixed-factor-clock";
+ #clock-cells = <0>;
+ clock-div = <1>;
+ clock-mult = <2>;
+ clocks = <&pll3>;
+ clock-output-names = "pll3-x2";
+ };
+
+
pll4: clk@01c20018 {
#clock-cells = <0>;
compatible = "allwinner,sun4i-a10-pll1-clk";
@@ -232,6 +259,23 @@
clock-output-names = "pll6_sata", "pll6_other", "pll6";
};
+ pll7: clk@01c20030 {
+ #clock-cells = <0>;
+ compatible = "allwinner,sun4i-a10-pll3-clk";
+ reg = <0x01c20030 0x4>;
+ clocks = <&osc3M>;
+ clock-output-names = "pll7";
+ };
+
+ pll7x2: pll7x2_clk {
+ compatible = "fixed-factor-clock";
+ #clock-cells = <0>;
+ clock-div = <1>;
+ clock-mult = <2>;
+ clocks = <&pll7>;
+ clock-output-names = "pll7-2x";
+ };
+
/* dummy is 200M */
cpu: cpu@01c20054 {
#clock-cells = <0>;
--
2.8.1
--
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] [PATCH 0/2] ARM: dts: sunxi: Add pll3 and pll7 clock to sun[47]i.dtsi
Enable the pll3 and pll7 clocks in the DT that are used to drive the display-related clocks. Priit Laes (2): ARM: sun4i: dt: Add pll3 and pll7 clocks ARM: sun7i: dt: Add pll3 and pll7 clocks arch/arm/boot/dts/sun4i-a10.dtsi | 44 arch/arm/boot/dts/sun7i-a20.dtsi | 41 + 2 files changed, 85 insertions(+) -- 2.8.1 -- 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/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
Hey all, On 03-05-16 17:02, christo.ra...@gmail.com wrote: On Tuesday, May 3, 2016 at 4:14:41 PM UTC+3, Maxime Ripard wrote: Hi, On Tue, May 03, 2016 at 4:12:06 PM UTC+3, Christo Radev wrote: Hi to All, I have already solved and tested this issue on Armbian build. Find patches for both legacy (3.4.111) and mainline (4.5.2) kernels on: http://forum.armbian.com/index.php/topic/853-armbian-customization/page-2#entry7494 There it is also described how to do eMMC bootable and much more. About the board - Olimex already sold all 3 kinds after migration to their HW rev. E. One have to specify Lime2-eMMC as A20-Olinuxino-Lime2-eMMC instead of their old 2 options A20-Olinuxino-Lime2(-4GB). Interesting, you have a link to that device? Thanks, Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com I have really 2 boards delivered by their local distributor. Unfortunately, they do not update their site. Use the link for NAND option: https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4GB/open-source-hardware There you can find Users Manual where it is described that eMMC option is available from HW rev. D. The schematic for HW rev. E is also available on their repository: https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 On the board both 4GB NAND and eMMC Flash chips can be placed alternatively on the same place. There is difference in some other components as well. If one want to order it from the site probably has to order A20-Olinuxino-Lime2-4GB with note that eMMC option is required. The price is the same. Sorry for the late reply, but yeah the board exists, we asked Olimex to develop the eMMC variant for us. I currently have a dozen or so on my desk :) I don't know when Olimex will update their webshop with the new designs, but they simply might not have enough eMMC chips available yet? -- 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/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
On Tuesday, May 3, 2016 at 4:14:41 PM UTC+3, Maxime Ripard wrote: > Hi, > > On Tue, May 03, 2016 at 4:12:06 PM UTC+3, Christo Radev wrote: > > Hi to All, > > > > I have already solved and tested this issue on Armbian build. Find > > patches for both legacy (3.4.111) and mainline (4.5.2) kernels on: > > http://forum.armbian.com/index.php/topic/853-armbian-customization/page-2#entry7494 > > There it is also described how to do eMMC bootable and much more. > > > > About the board - Olimex already sold all 3 kinds after migration to > > their HW rev. E. One have to specify Lime2-eMMC as > > A20-Olinuxino-Lime2-eMMC instead of their old 2 options > > A20-Olinuxino-Lime2(-4GB). > > Interesting, you have a link to that device? > > Thanks, > Maxime > > -- > Maxime Ripard, Free Electrons > Embedded Linux, Kernel and Android engineering > http://free-electrons.com I have really 2 boards delivered by their local distributor. Unfortunately, they do not update their site. Use the link for NAND option: https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4GB/open-source-hardware There you can find Users Manual where it is described that eMMC option is available from HW rev. D. The schematic for HW rev. E is also available on their repository: https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 On the board both 4GB NAND and eMMC Flash chips can be placed alternatively on the same place. There is difference in some other components as well. If one want to order it from the site probably has to order A20-Olinuxino-Lime2-4GB with note that eMMC option is required. The price is the same. -- 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: [U-Boot] Porting Linux's MTD/NAND changes into U-Boot
On Mon, 2016-04-25 at 22:53 +0200, Boris Brezillon wrote: > On Mon, 25 Apr 2016 13:36:46 -0400 > Tom Rini wrote: > > > On Mon, Apr 25, 2016 at 04:43:14PM +0200, Boris Brezillon wrote: > > > > > Hi Scott, > > > > > > I've recently contributed a lot of MTD/NAND related patches (and intend > > > to continue doing so). Some of them are transversal changes touching the > > > MTD and NAND framework internals, which implies patching all NAND > > > drivers along with the core changes. > > > > > > All those changes are required to properly handle modern NANDs (MLC/TLC > > > NANDs), and I need them to add proper NAND support to the sunxi > > > platform (and more particularly to the C.H.I.P from NextThing Co.). > > > > > > So my question is, how should I port those changes to U-Boot? I see > > > that your doing "synchronization commits", but in my case this mean > > > including a bunch of driver specific changes into this "sync commit". > > > > > > I think it's also worth mentioning that I plan to heavily rework the > > > Linux NAND framework to improve NAND performances on modern NAND > > > controllers and clarify the NAND chip / NAND controller concepts, and > > > other people are also working on merging the BBT code of the NAND and > > > OneNAND framework. Which unfortunately means that we're not done porting > > > invasive changes to U-Boot :-/. > > > > > > Any advice is welcome. > > > > I suppose my first suggestion would be to sync the kernel back into > > U-Boot more frequently. With our bi-monthly release cycle it shouldn't > > be too hard to pick a window to grab the current kernel release and > > bring it over. I think the more stuff we let build up prior to syncing > > the harder it will be. > > > > Okay, so this means I should be the one back-porting Linux changes into > U-Boot? I was planning on porting my current work on the sunxi NAND > driver (including all the core dependencies) and submitting it to > U-Boot, but honestly, I don't see how I can keep things in sync in the > long run. From my experience, porting things to U-Boot is never as > easy at it seems, and I don't think I'll have the time to maintain that > by myself. Scott, what's your policy regarding Linux -> U-Boot syncs? > Can I expect some help from your side? I usually do syncs when someone complains about needing a sync. Every release seems a bit much. I'll try to do one soon. -Scott -- 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/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
Hi to All, I have already solved and tested this issue on Armbian build. Find patches for both legacy (3.4.111) and mainline (4.5.2) kernels on: http://forum.armbian.com/index.php/topic/853-armbian-customization/page-2#entry7494 There it is also described how to do eMMC bootable and much more. About the board - Olimex already sold all 3 kinds after migration to their HW rev. E. One have to specify Lime2-eMMC as A20-Olinuxino-Lime2-eMMC instead of their old 2 options A20-Olinuxino-Lime2(-4GB). Regards Chris -- 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/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
Hi, On Tue, May 03, 2016 at 12:12:06AM -0700, christo.ra...@gmail.com wrote: > Hi to All, > > I have already solved and tested this issue on Armbian build. Find > patches for both legacy (3.4.111) and mainline (4.5.2) kernels on: > http://forum.armbian.com/index.php/topic/853-armbian-customization/page-2#entry7494 > There it is also described how to do eMMC bootable and much more. > > About the board - Olimex already sold all 3 kinds after migration to > their HW rev. E. One have to specify Lime2-eMMC as > A20-Olinuxino-Lime2-eMMC instead of their old 2 options > A20-Olinuxino-Lime2(-4GB). Interesting, you have a link to that device? Thanks, Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- 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. signature.asc Description: PGP signature
[linux-sunxi] [PATCHv2] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
There are 3 kinds of OLinuXino Lime2 boards.
One without any on board storage, one with NAND storage and one with
eMMC storage. This patch adds the eMMC variant of boards.
eMMC storage is different from a regular SD card in that it is soldered
on the board and cannot be changed. Additionally, it shares pins with
the NAND module and with the second SPI port.
Signed-off-by: Olliver Schinagl
---
.../boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts| 64 ++
1 file changed, 64 insertions(+)
create mode 100644 arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
new file mode 100644
index 000..b49aafe
--- /dev/null
+++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
@@ -0,0 +1,64 @@
+ /*
+ * Copyright 2015 - Ultimaker B.V.
+ * Author Olliver Schinagl
+ *
+ * This file is dual-licensed: you can use it either under the terms
+ * of the GPL or the X11 license, at your option. Note that this dual
+ * licensing only applies to this file, and not this project as a
+ * whole.
+ *
+ * a) This file is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of the
+ * License, or (at your option) any later version.
+ *
+ * This file is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * Or, alternatively,
+ *
+ * b) Permission is hereby granted, free of charge, to any person
+ * obtaining a copy of this software and associated documentation
+ * files (the "Software"), to deal in the Software without
+ * restriction, including without limitation the rights to use,
+ * copy, modify, merge, publish, distribute, sublicense, and/or
+ * sell copies of the Software, and to permit persons to whom the
+ * Software is furnished to do so, subject to the following
+ * conditions:
+ *
+ * The above copyright notice and this permission notice shall be
+ * included in all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+ * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+ * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+ * OTHER DEALINGS IN THE SOFTWARE.
+ */
+
+#include "sun7i-a20-olinuxino-lime2.dts"
+
+/ {
+ model = "Olimex A20-OLinuXino-LIME2-eMMC";
+};
+
+&mmc2 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&mmc2_pins_a>;
+ vmmc-supply = <®_vcc3v3>;
+ vqmmc-supply = <®_vcc3v3>;
+ bus-width = <4>;
+ non-removable;
+ status = "okay";
+
+ emmc: emmc@0 {
+ reg = <0>;
+ compatible = "mmc-card";
+ broken-hpi;
+ };
+};
--
2.8.1
--
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] A64 LCD RGB interface
Hi Did someone try to use RGB LCD with A64? For the laptop we work on the LCD is eDP and we found RGB to eDP convertor IC, but seems there are no drivers for A64 with parallel RGB interface. We have few A64-OLinuXino boards and we can wire RGB LCD to them and send to who is willing to help with the RGB LCD on A63:) Best regards Tsvetan -- 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: [U-Boot] Porting Linux's MTD/NAND changes into U-Boot
Hi Scott, On Tue, 03 May 2016 00:06:45 -0500 Scott Wood wrote: > On Mon, 2016-04-25 at 22:53 +0200, Boris Brezillon wrote: > > On Mon, 25 Apr 2016 13:36:46 -0400 > > Tom Rini wrote: > > > > > On Mon, Apr 25, 2016 at 04:43:14PM +0200, Boris Brezillon wrote: > > > > > > > Hi Scott, > > > > > > > > I've recently contributed a lot of MTD/NAND related patches (and intend > > > > to continue doing so). Some of them are transversal changes touching the > > > > MTD and NAND framework internals, which implies patching all NAND > > > > drivers along with the core changes. > > > > > > > > All those changes are required to properly handle modern NANDs (MLC/TLC > > > > NANDs), and I need them to add proper NAND support to the sunxi > > > > platform (and more particularly to the C.H.I.P from NextThing Co.). > > > > > > > > So my question is, how should I port those changes to U-Boot? I see > > > > that your doing "synchronization commits", but in my case this mean > > > > including a bunch of driver specific changes into this "sync commit". > > > > > > > > I think it's also worth mentioning that I plan to heavily rework the > > > > Linux NAND framework to improve NAND performances on modern NAND > > > > controllers and clarify the NAND chip / NAND controller concepts, and > > > > other people are also working on merging the BBT code of the NAND and > > > > OneNAND framework. Which unfortunately means that we're not done porting > > > > invasive changes to U-Boot :-/. > > > > > > > > Any advice is welcome. > > > > > > I suppose my first suggestion would be to sync the kernel back into > > > U-Boot more frequently. With our bi-monthly release cycle it shouldn't > > > be too hard to pick a window to grab the current kernel release and > > > bring it over. I think the more stuff we let build up prior to syncing > > > the harder it will be. > > > > > > > Okay, so this means I should be the one back-porting Linux changes into > > U-Boot? I was planning on porting my current work on the sunxi NAND > > driver (including all the core dependencies) and submitting it to > > U-Boot, but honestly, I don't see how I can keep things in sync in the > > long run. From my experience, porting things to U-Boot is never as > > easy at it seems, and I don't think I'll have the time to maintain that > > by myself. Scott, what's your policy regarding Linux -> U-Boot syncs? > > Can I expect some help from your side? > > I usually do syncs when someone complains about needing a sync. Every release > seems a bit much. I'll try to do one soon. Great! Let me know if you need some help. Thanks, Boris -- Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com -- 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/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
On Tue, May 3, 2016 at 3:21 PM, Olliver Schinagl wrote:
> Hey Chen,
ChenYu :)
>
>
> On 03-05-16 05:33, Chen-Yu Tsai wrote:
>>
>> Hi,
>>
>> On Thu, Apr 28, 2016 at 3:19 PM, Olliver Schinagl
>> wrote:
>>>
>>> There are 3 kinds of OLinuXino Lime2 boards.
>>> One without any on board storage, one with NAND storage and one with
>>> eMMC storage. This patch adds the eMMC variant of boards.
>>>
>>> eMMC storage is different from a regular SD card in that it is soldered
>>> on the board and cannot be changed. Additionally, it shares pins with
>>> the NAND module and with the second SPI port.
>>>
>>> Signed-off-by: Olliver Schinagl
>>> ---
>>> .../boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts| 64
>>> ++
>>> 1 file changed, 64 insertions(+)
>>> create mode 100644 arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
>>>
>>> diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
>>> b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
>>> new file mode 100644
>>> index 000..689da36
>>> --- /dev/null
>>> +++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
>>> @@ -0,0 +1,64 @@
>>> + /*
>>> + * Copyright 2015 - Ultimaker B.V.
>>> + * Author Olliver Schinagl
>>> + *
>>> + * This file is dual-licensed: you can use it either under the terms
>>> + * of the GPL or the X11 license, at your option. Note that this dual
>>> + * licensing only applies to this file, and not this project as a
>>> + * whole.
>>> + *
>>> + * a) This file is free software; you can redistribute it and/or
>>> + * modify it under the terms of the GNU General Public License as
>>> + * published by the Free Software Foundation; either version 2 of
>>> the
>>> + * License, or (at your option) any later version.
>>> + *
>>> + * This file is distributed in the hope that it will be useful,
>>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
>>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>>> + * GNU General Public License for more details.
>>> + *
>>> + * Or, alternatively,
>>> + *
>>> + * b) Permission is hereby granted, free of charge, to any person
>>> + * obtaining a copy of this software and associated documentation
>>> + * files (the "Software"), to deal in the Software without
>>> + * restriction, including without limitation the rights to use,
>>> + * copy, modify, merge, publish, distribute, sublicense, and/or
>>> + * sell copies of the Software, and to permit persons to whom the
>>> + * Software is furnished to do so, subject to the following
>>> + * conditions:
>>> + *
>>> + * The above copyright notice and this permission notice shall be
>>> + * included in all copies or substantial portions of the Software.
>>> + *
>>> + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
>>> + * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
>>> + * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
>>> + * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
>>> + * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
>>> + * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
>>> + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
>>> + * OTHER DEALINGS IN THE SOFTWARE.
>>> + */
>>> +
>>> +#include "sun7i-a20-olinuxino-lime2.dts"
>>> +
>>> +/ {
>>> + model = "Olimex A20-OLinuXino-LIME2-eMMC";
>>> +};
>>> +
>>> +&mmc2 {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&mmc2_pins_a>;
>>> + vmmc-supply = <®_vcc3v3>;
>>> + bus-width = <4>;
>>
>> Only 4 bits? We normally see eMMC with 8 bits. 4 bits are some kind of
>> embedded SD card.
>
> On A20 as well? Our investigations so far have concluded that the A10 and
> A20 have those pins not mapped out to pads. The IP does support it however
> we assume.
You're right. My bad. First time A10/A20 sees eMMC support.
>>
>>
>>> + non-removable;
>>> + no-1-8-v;
>>
>> This flag is not supported on sunxi.
>>
>> Instead, use the vqmmc-supply with the correct regulator and constraints.
>
> That was not supposed to be there, i'll fix it! Sorry.
Thanks
ChenYu
>
>>
>> ChenYu
>>
>>> + status = "okay";
>>> +
>>> + emmc: emmc@0 {
>>> + reg = <0>;
>>> + compatible = "mmc-card";
>>> + broken-hpi;
>>> + };
>>> +};
>>> --
>>> 2.8.0.rc3
>>>
>
--
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/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
Hey Chen,
On 03-05-16 05:33, Chen-Yu Tsai wrote:
Hi,
On Thu, Apr 28, 2016 at 3:19 PM, Olliver Schinagl wrote:
There are 3 kinds of OLinuXino Lime2 boards.
One without any on board storage, one with NAND storage and one with
eMMC storage. This patch adds the eMMC variant of boards.
eMMC storage is different from a regular SD card in that it is soldered
on the board and cannot be changed. Additionally, it shares pins with
the NAND module and with the second SPI port.
Signed-off-by: Olliver Schinagl
---
.../boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts| 64 ++
1 file changed, 64 insertions(+)
create mode 100644 arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
new file mode 100644
index 000..689da36
--- /dev/null
+++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts
@@ -0,0 +1,64 @@
+ /*
+ * Copyright 2015 - Ultimaker B.V.
+ * Author Olliver Schinagl
+ *
+ * This file is dual-licensed: you can use it either under the terms
+ * of the GPL or the X11 license, at your option. Note that this dual
+ * licensing only applies to this file, and not this project as a
+ * whole.
+ *
+ * a) This file is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of the
+ * License, or (at your option) any later version.
+ *
+ * This file is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * Or, alternatively,
+ *
+ * b) Permission is hereby granted, free of charge, to any person
+ * obtaining a copy of this software and associated documentation
+ * files (the "Software"), to deal in the Software without
+ * restriction, including without limitation the rights to use,
+ * copy, modify, merge, publish, distribute, sublicense, and/or
+ * sell copies of the Software, and to permit persons to whom the
+ * Software is furnished to do so, subject to the following
+ * conditions:
+ *
+ * The above copyright notice and this permission notice shall be
+ * included in all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+ * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+ * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+ * OTHER DEALINGS IN THE SOFTWARE.
+ */
+
+#include "sun7i-a20-olinuxino-lime2.dts"
+
+/ {
+ model = "Olimex A20-OLinuXino-LIME2-eMMC";
+};
+
+&mmc2 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&mmc2_pins_a>;
+ vmmc-supply = <®_vcc3v3>;
+ bus-width = <4>;
Only 4 bits? We normally see eMMC with 8 bits. 4 bits are some kind of
embedded SD card.
On A20 as well? Our investigations so far have concluded that the A10
and A20 have those pins not mapped out to pads. The IP does support it
however we assume.
+ non-removable;
+ no-1-8-v;
This flag is not supported on sunxi.
Instead, use the vqmmc-supply with the correct regulator and constraints.
That was not supposed to be there, i'll fix it! Sorry.
ChenYu
+ status = "okay";
+
+ emmc: emmc@0 {
+ reg = <0>;
+ compatible = "mmc-card";
+ broken-hpi;
+ };
+};
--
2.8.0.rc3
--
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.
