[PATCH] ASoC: davinvi-mcasp: Balance pm_runtime_enable() on probe failure
If probe fails then we need to call pm_runtime_disable() to balance
out the previous pm_runtime_enable() call.
Signed-off-by: Anil Kumar
---
:100644 100644 0eed9b1... 99c747d... M sound/soc/davinci/davinci-mcasp.c
sound/soc/davinci/davinci-mcasp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/davinci/davinci-mcasp.c
b/sound/soc/davinci/davinci-mcasp.c
index 0eed9b1..99c747d 100644
--- a/sound/soc/davinci/davinci-mcasp.c
+++ b/sound/soc/davinci/davinci-mcasp.c
@@ -1235,6 +1235,7 @@ static int davinci_mcasp_probe(struct platform_device
*pdev)
ret = pm_runtime_get_sync(>dev);
if (IS_ERR_VALUE(ret)) {
dev_err(>dev, "pm_runtime_get_sync() failed\n");
+ pm_runtime_disable(>dev);
return ret;
}
--
1.9.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] ASoC: davinvi-mcasp: Balance pm_runtime_enable() on probe failure
If probe fails then we need to call pm_runtime_disable() to balance
out the previous pm_runtime_enable() call.
Signed-off-by: Anil Kumar anilk...@gmail.com
---
:100644 100644 0eed9b1... 99c747d... M sound/soc/davinci/davinci-mcasp.c
sound/soc/davinci/davinci-mcasp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/davinci/davinci-mcasp.c
b/sound/soc/davinci/davinci-mcasp.c
index 0eed9b1..99c747d 100644
--- a/sound/soc/davinci/davinci-mcasp.c
+++ b/sound/soc/davinci/davinci-mcasp.c
@@ -1235,6 +1235,7 @@ static int davinci_mcasp_probe(struct platform_device
*pdev)
ret = pm_runtime_get_sync(pdev-dev);
if (IS_ERR_VALUE(ret)) {
dev_err(pdev-dev, pm_runtime_get_sync() failed\n);
+ pm_runtime_disable(pdev-dev);
return ret;
}
--
1.9.2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Build error in torvalds kernel 3.11 for omap2plus
Hi All, I am getting below build error in torvalds kernel 3.11 for omap2plus. scripts/kconfig/conf --silentoldconfig Kconfig CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CALLscripts/checksyscalls.sh CHK include/generated/compile.h AS arch/arm/mm/cache-v7.o arch/arm/mm/cache-v7.S: Assembler messages: arch/arm/mm/cache-v7.S:285: Error: garbage following instruction -- `dsb ishst' arch/arm/mm/cache-v7.S:297: Error: garbage following instruction -- `dsb ishst' make[1]: *** [arch/arm/mm/cache-v7.o] Error 1 make: *** [arch/arm/mm] Error 2 Thanks Anil -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Build error in torvalds kernel 3.11 for omap2plus
Hi All, I am getting below build error in torvalds kernel 3.11 for omap2plus. scripts/kconfig/conf --silentoldconfig Kconfig CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CALLscripts/checksyscalls.sh CHK include/generated/compile.h AS arch/arm/mm/cache-v7.o arch/arm/mm/cache-v7.S: Assembler messages: arch/arm/mm/cache-v7.S:285: Error: garbage following instruction -- `dsb ishst' arch/arm/mm/cache-v7.S:297: Error: garbage following instruction -- `dsb ishst' make[1]: *** [arch/arm/mm/cache-v7.o] Error 1 make: *** [arch/arm/mm] Error 2 Thanks Anil -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V4] ARM: dts: add minimal DT support for DevKit8000.
Hi Benoit, On Thu, Mar 7, 2013 at 12:21 PM, Benoit Cousson wrote: > Hi, > > On 03/06/2013 06:53 PM, Tony Lindgren wrote: >> * Anil Kumar [130305 18:40]: >>> Hi Tony, >>> >>>>> From: linux-arm-kernel [mailto:linux-arm-kernel- >>>>> boun...@lists.infradead.org] On Behalf Of Anil Kumar >>>>> Sent: Wednesday, February 27, 2013 8:03 AM >>>>> To: devicetree-disc...@lists.ozlabs.org; linux-o...@vger.kernel.org; >>>>> linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org >>>>> Cc: li...@arm.linux.org.uk; Cousson, Benoit; Tony Lindgren; Grant >>>>> Likely; Anil Kumar; tho...@tomweber.eu >>>>> Subject: Re: FW: [PATCH V4] ARM: dts: add minimal DT support for >>>>> DevKit8000. >>>>> >>>>> Hi, >>>>>> >>>>>> DevKit8000 is a beagle board clone from Timll, sold by >>>>>> armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D, >>>>>> S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and >>>>>> JTAG interface. >>>>>> >>>>>> This patch adds the basic DT support for devkit8000. At this time, >>>>> Information >>>>>> of twl4030 (PMIC), MMC1, I2C1 and leds are added. >>>>>> >>>>>> Signed-off-by: Anil Kumar >>>>>> Tested-by: Thomas Weber >>>>> >>>>> Gentle Ping. As there are no review comments on this patch, >>>>> Could you please pull this patch ? >>> >>> Gentle Ping. >>> >>> This patch also got Reviewed-by: Manish Badarkhe >>> and as patch "ARM: dts: omap3-devkit8000: Enable audio support" has >>> already got >>> "Acked-by: Peter Ujfalusi " but it is on the >>> top of this patch. >>> So, Could you please pull this patch in one of your omap branch? or >>> you want me to >>> do rebase this patch on top of v3.9-rc1 ? >> >> Let's wait for Benoit to queue it as he has a bunch of .dts changes already >> applied. Too bad we missed v3.9 merge window for those, but hopefully >> we can get them queued early for v3.10. > > Yep, sorry for having missed 3.9, I was a little bit sick at the wrong > moment :-( > > I'm starting queuing the pending patches, and should have enough to push > to you just after Linaro Connect. I think you missed below patch which is needed for gpmc nand to work fine. Jon Hunter:- ARM: OMAP2+: Fix-up gpmc merge error I have re based my changes on top of your repository to make pull easier for you. I hope you will pull these changes for 3.10. The following changes since Commit a7f7881de9c0b58de3b3aea8f01a8aef906d4ade are available in the git repository at: git://gitorious.org/devkit8000-for_3-10/devkit8000-for_3-10.git branch for_3.10/dts for you to fetch changes up to Commit 975abc8b2e7ec4ff7324d726c9775958945ccc5e Anil Kumar: ARM: dts: add minimal DT support for DevKit8000 ARM: dts: omap3-devkit8000: Enable audio support ARM: dts: omap3-devkit8000: add nand dt node Thanks, Anil -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Getting kernel uImage build issue on omap2+
Hi Javier, On Sat, Mar 16, 2013 at 2:53 PM, Javier Martinez Canillas wrote: > On Sat, Mar 16, 2013 at 5:44 AM, Anil Kumar wrote: >> Hi, >> >> I am getting kernel uImage build issue on omap2+ log[1] >> >> Taken kernel branch "for_3.10/dts" from >> https://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git >> >> Taking reference from >> https://kernel.googlesource.com/pub/scm/linux/kernel/git/tmlind/linux-omap/+/omap-for-v3.9/multiplatform-enable-signed-v2 >> >> Am I missing some thing ? >> >> [1] >> anil@anil-laptop:~/Anil/omap3/bcousson$ mkimage -A arm -O linux -T >> kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d >> zImage-omap2plus uImage-omap2plus >> mkimage: Can't open zImage-omap2plus: No such file or directory >> anil@anil-laptop:~/Anil/omap3/bcousson$ >> >> Thanks, >> Anil >> > > Hi Anil, > > It seems that Tony's email assumed that you generated a bunch of > zImages for different platforms and then naming them zImage-$platform. > > e.g: > > $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig > $ make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage modules > zImage-omap2plus > $ cp cp arch/arm/boot/zImage zImage-omap2plus > > and then you can use the command in [1]: > > $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e > 0x80008000 -n "Linux" -d zImage-omap2plus uImage-omap2plus > > anyways, the problem is that zImage-omap2plus does not exist and you > have to use the zImage generated by "make zImage". What I usually do > is just: > > $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e > 0x80008000 -n "Linux" -d arch/arm/boot/zImage uImage-omap2plus > > and then copy uImage-omap2plus as uImage on either my board MMC/SD or > Flash memory. Thanks, It solved the issue Anil -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Getting kernel uImage build issue on omap2+
Hi Javier, On Sat, Mar 16, 2013 at 2:53 PM, Javier Martinez Canillas jav...@dowhile0.org wrote: On Sat, Mar 16, 2013 at 5:44 AM, Anil Kumar anilk...@gmail.com wrote: Hi, I am getting kernel uImage build issue on omap2+ log[1] Taken kernel branch for_3.10/dts from https://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git Taking reference from https://kernel.googlesource.com/pub/scm/linux/kernel/git/tmlind/linux-omap/+/omap-for-v3.9/multiplatform-enable-signed-v2 Am I missing some thing ? [1] anil@anil-laptop:~/Anil/omap3/bcousson$ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n Linux -d zImage-omap2plus uImage-omap2plus mkimage: Can't open zImage-omap2plus: No such file or directory anil@anil-laptop:~/Anil/omap3/bcousson$ Thanks, Anil Hi Anil, It seems that Tony's email assumed that you generated a bunch of zImages for different platforms and then naming them zImage-$platform. e.g: $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig $ make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage modules zImage-omap2plus $ cp cp arch/arm/boot/zImage zImage-omap2plus and then you can use the command in [1]: $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n Linux -d zImage-omap2plus uImage-omap2plus anyways, the problem is that zImage-omap2plus does not exist and you have to use the zImage generated by make zImage. What I usually do is just: $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n Linux -d arch/arm/boot/zImage uImage-omap2plus and then copy uImage-omap2plus as uImage on either my board MMC/SD or Flash memory. Thanks, It solved the issue Anil -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V4] ARM: dts: add minimal DT support for DevKit8000.
Hi Benoit, On Thu, Mar 7, 2013 at 12:21 PM, Benoit Cousson b-cous...@ti.com wrote: Hi, On 03/06/2013 06:53 PM, Tony Lindgren wrote: * Anil Kumar anilk...@gmail.com [130305 18:40]: Hi Tony, From: linux-arm-kernel [mailto:linux-arm-kernel- boun...@lists.infradead.org] On Behalf Of Anil Kumar Sent: Wednesday, February 27, 2013 8:03 AM To: devicetree-disc...@lists.ozlabs.org; linux-o...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org Cc: li...@arm.linux.org.uk; Cousson, Benoit; Tony Lindgren; Grant Likely; Anil Kumar; tho...@tomweber.eu Subject: Re: FW: [PATCH V4] ARM: dts: add minimal DT support for DevKit8000. Hi, DevKit8000 is a beagle board clone from Timll, sold by armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D, S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and JTAG interface. This patch adds the basic DT support for devkit8000. At this time, Information of twl4030 (PMIC), MMC1, I2C1 and leds are added. Signed-off-by: Anil Kumar anilk...@gmail.com Tested-by: Thomas Weber tho...@tomweber.eu Gentle Ping. As there are no review comments on this patch, Could you please pull this patch ? Gentle Ping. This patch also got Reviewed-by: Manish Badarkhe badarkhe.man...@gmail.com and as patch ARM: dts: omap3-devkit8000: Enable audio support has already got Acked-by: Peter Ujfalusi peter.ujfal...@ti.com but it is on the top of this patch. So, Could you please pull this patch in one of your omap branch? or you want me to do rebase this patch on top of v3.9-rc1 ? Let's wait for Benoit to queue it as he has a bunch of .dts changes already applied. Too bad we missed v3.9 merge window for those, but hopefully we can get them queued early for v3.10. Yep, sorry for having missed 3.9, I was a little bit sick at the wrong moment :-( I'm starting queuing the pending patches, and should have enough to push to you just after Linaro Connect. I think you missed below patch which is needed for gpmc nand to work fine. Jon Hunter:- ARM: OMAP2+: Fix-up gpmc merge error I have re based my changes on top of your repository to make pull easier for you. I hope you will pull these changes for 3.10. The following changes since Commit a7f7881de9c0b58de3b3aea8f01a8aef906d4ade are available in the git repository at: git://gitorious.org/devkit8000-for_3-10/devkit8000-for_3-10.git branch for_3.10/dts for you to fetch changes up to Commit 975abc8b2e7ec4ff7324d726c9775958945ccc5e Anil Kumar: ARM: dts: add minimal DT support for DevKit8000 ARM: dts: omap3-devkit8000: Enable audio support ARM: dts: omap3-devkit8000: add nand dt node Thanks, Anil -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V4] ARM: dts: add minimal DT support for DevKit8000.
Hi Tony,
>> From: linux-arm-kernel [mailto:linux-arm-kernel-
>> boun...@lists.infradead.org] On Behalf Of Anil Kumar
>> Sent: Wednesday, February 27, 2013 8:03 AM
>> To: devicetree-disc...@lists.ozlabs.org; linux-o...@vger.kernel.org;
>> linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org
>> Cc: li...@arm.linux.org.uk; Cousson, Benoit; Tony Lindgren; Grant
>> Likely; Anil Kumar; tho...@tomweber.eu
>> Subject: Re: FW: [PATCH V4] ARM: dts: add minimal DT support for
>> DevKit8000.
>>
>> Hi,
>> >
>> > DevKit8000 is a beagle board clone from Timll, sold by
>> > armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
>> > S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
>> > JTAG interface.
>> >
>> > This patch adds the basic DT support for devkit8000. At this time,
>> Information
>> > of twl4030 (PMIC), MMC1, I2C1 and leds are added.
>> >
>> > Signed-off-by: Anil Kumar
>> > Tested-by: Thomas Weber
>>
>> Gentle Ping. As there are no review comments on this patch,
>> Could you please pull this patch ?
Gentle Ping.
This patch also got Reviewed-by: Manish Badarkhe
and as patch "ARM: dts: omap3-devkit8000: Enable audio support" has already got
"Acked-by: Peter Ujfalusi " but it is on the
top of this patch.
So, Could you please pull this patch in one of your omap branch? or
you want me to
do rebase this patch on top of v3.9-rc1 ?
Thanks,
Anil
>>
>> > ---
>> > -This patch is based on top of kernel 3.8-rc5.
>> >
>> > -Tested on Devkit8000.
>> >
>> > For V4:
>> > -Tiny nitpick.
>> >
>> > For V3:
>> > - Remove pin mux as done at device boot time by default.
>> >
>> > For V2:
>> > - Change model name as "TimLL OMAP3 Devkit8000"
>> > - Change compatible as "timll,omap3-devkit8000"
>> > - Doing i2c1 pinmux default with pinctrl-single driver instead of
>> i2c1
>> >driver probe time.
>> >
>> > :100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
>> > :00 100644 000... 2e1463a... A arch/arm/boot/dts/omap3-
>> devkit8000.dts
>> > :100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-
>> generic.c
>> > arch/arm/boot/dts/Makefile |1 +
>> > arch/arm/boot/dts/omap3-devkit8000.dts | 102
>>
>> > arch/arm/mach-omap2/board-generic.c|1 +
>> > 3 files changed, 104 insertions(+), 0 deletions(-)
>> >
>> > diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
>> > index 5ebb44f..22ebc76 100644
>> > --- a/arch/arm/boot/dts/Makefile
>> > +++ b/arch/arm/boot/dts/Makefile
>> > @@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
>> > imx28-tx28.dtb
>> > dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
>> > omap3-beagle.dtb \
>> > + omap3-devkit8000.dtb \
>> > omap3-beagle-xm.dtb \
>> > omap3-evm.dtb \
>> > omap3-tobi.dtb \
>> > diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
>> b/arch/arm/boot/dts/omap3-devkit8000.dts
>> > new file mode 100644
>> > index 000..2e1463a
>> > --- /dev/null
>> > +++ b/arch/arm/boot/dts/omap3-devkit8000.dts
>> > @@ -0,0 +1,102 @@
>> > +/*
>> > + * Author: Anil Kumar
>> > + *
>> > + * 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.
>> > + */
>> > +/dts-v1/;
>> > +
>> > +/include/ "omap3.dtsi"
>> > +/ {
>> > + model = "TimLL OMAP3 Devkit8000";
>> > + compatible = "timll,omap3-devkit8000", "ti,omap3";
>> > +
>> > + memory {
>> > + device_type = "memory";
>> > + reg = <0x8000 0x1000>; /* 256 MB */
>> > + };
>> > +
>> > + leds {
>> > + compatible = "gpio-leds";
>> > +
>> > + heartbeat {
>> > + label = "devkit8000::led1";
>> > + gpios = < 26 0>; /* 186 -> LED1 */
>> > + default-state = "on";
>> > +
Re: [PATCH V4] ARM: dts: add minimal DT support for DevKit8000.
Hi Tony,
From: linux-arm-kernel [mailto:linux-arm-kernel-
boun...@lists.infradead.org] On Behalf Of Anil Kumar
Sent: Wednesday, February 27, 2013 8:03 AM
To: devicetree-disc...@lists.ozlabs.org; linux-o...@vger.kernel.org;
linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Cc: li...@arm.linux.org.uk; Cousson, Benoit; Tony Lindgren; Grant
Likely; Anil Kumar; tho...@tomweber.eu
Subject: Re: FW: [PATCH V4] ARM: dts: add minimal DT support for
DevKit8000.
Hi,
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time,
Information
of twl4030 (PMIC), MMC1, I2C1 and leds are added.
Signed-off-by: Anil Kumar anilk...@gmail.com
Tested-by: Thomas Weber tho...@tomweber.eu
Gentle Ping. As there are no review comments on this patch,
Could you please pull this patch ?
Gentle Ping.
This patch also got Reviewed-by: Manish Badarkhe badarkhe.man...@gmail.com
and as patch ARM: dts: omap3-devkit8000: Enable audio support has already got
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com but it is on the
top of this patch.
So, Could you please pull this patch in one of your omap branch? or
you want me to
do rebase this patch on top of v3.9-rc1 ?
Thanks,
Anil
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V4:
-Tiny nitpick.
For V3:
- Remove pin mux as done at device boot time by default.
For V2:
- Change model name as TimLL OMAP3 Devkit8000
- Change compatible as timll,omap3-devkit8000
- Doing i2c1 pinmux default with pinctrl-single driver instead of
i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 2e1463a... A arch/arm/boot/dts/omap3-
devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-
generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 102
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 104 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..2e1463a
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,102 @@
+/*
+ * Author: Anil Kumar anilk...@gmail.com
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ omap3.dtsi
+/ {
+ model = TimLL OMAP3 Devkit8000;
+ compatible = timll,omap3-devkit8000, ti,omap3;
+
+ memory {
+ device_type = memory;
+ reg = 0x8000 0x1000; /* 256 MB */
+ };
+
+ leds {
+ compatible = gpio-leds;
+
+ heartbeat {
+ label = devkit8000::led1;
+ gpios = gpio6 26 0; /* 186 - LED1 */
+ default-state = on;
+ linux,default-trigger = heartbeat;
+ };
+
+ mmc {
+ label = devkit8000::led2;
+ gpios = gpio6 3 0; /* 163 - LED2 */
+ default-state = on;
+ linux,default-trigger = none;
+ };
+
+ usr {
+ label = devkit8000::led3;
+ gpios = gpio6 4 0; /* 164 - LED3 */
+ default-state = on;
+ linux,default-trigger = usr;
+};
+ };
+};
+
+i2c1 {
+ clock-frequency = 260;
+
+ twl: twl@48 {
+ reg = 0x48;
+ interrupts = 7; /* SYS_NIRQ cascaded to intc
*/
+ interrupt-parent = intc;
+ };
+};
+
+i2c2 {
+ status = disabled;
+};
+
+i2c3 {
+ status = disabled;
+};
+
+/include/ twl4030.dtsi
+
+mmc1 {
+ vmmc-supply = vmmc1;
+ vmmc_aux-supply = vsim;
+ bus-width = 8;
+};
+
+mmc2 {
+ status = disabled;
+};
+
+mmc3 {
+ status = disabled
Re: [PATCH V2] ARM: dts: omap3-devkit8000: Enable audio support
Hi,
On Mon, Feb 18, 2013 at 4:50 PM, Peter Ujfalusi wrote:
> On 02/16/2013 08:33 AM, Anil Kumar wrote:
>> Add the needed sections to enable audio support on
>> Devkit8000 when booted with DT blob.
>>
>> Signed-off-by: Anil Kumar
>
> Looks good:
> Acked-by: Peter Ujfalusi
Gentle Ping. As there are no review comments on this patch,
Could you please pull this patch ?
Thanks,
Anil
>
>> ---
>> This patch is based on top of kernel 3.8-rc5 and
>> the following patches.
>>
>> Peter Ujfalusi:-
>> ASoC: twl4030: Correct the support for Voice port
>> ASoC: twl4030: Convert MICBIAS to SUPPLY widget
>> ASoC: omap-twl4030: Add support for routing, voice port and jack detect
>>
>> Anil Kumar:-
>> ARM: dts: add minimal DT support for DevKit8000
>> https://patchwork.kernel.org/patch/2122461/
>>
>> -Tested for playback and capture on Devkit8000.
>>
>> Test process:-
>>
>> #amixer set 'PredriveR Mixer AudioR2' on
>> #amixer set 'PredriveL Mixer AudioL2' on
>> #amixer set PreDriv 100 unmute
>> #amixer set 'DAC2 Digital Fine' 100
>> #amixer cset numid=27 1
>> #arecord | aplay
>>
>> For V2:
>> - Remove pin mux as done at device boot time by default.
>>
>> :100644 100644 6338993... c70116f... M
>> arch/arm/boot/dts/omap3-devkit8000.dts
>> arch/arm/boot/dts/omap3-devkit8000.dts | 23 +++
>> 1 files changed, 19 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
>> b/arch/arm/boot/dts/omap3-devkit8000.dts
>> index 6338993..c70116f 100644
>> --- a/arch/arm/boot/dts/omap3-devkit8000.dts
>> +++ b/arch/arm/boot/dts/omap3-devkit8000.dts
>> @@ -42,6 +42,19 @@
>> };
>>
>> };
>> +
>> + sound {
>> + compatible = "ti,omap-twl4030";
>> + ti,model = "devkit8000";
>> +
>> + ti,mcbsp = <>;
>> + ti,codec = <_audio>;
>> + ti,audio-routing =
>> + "Ext Spk", "PREDRIVEL",
>> + "Ext Spk", "PREDRIVER",
>> + "MAINMIC", "Main Mic",
>> + "Main Mic", "Mic Bias 1";
>> + };
>> };
>>
>> {
>> @@ -51,6 +64,12 @@
>> reg = <0x48>;
>> interrupts = <7>; /* SYS_NIRQ cascaded to intc */
>> interrupt-parent = <>;
>> +
>> + twl_audio: audio {
>> + compatible = "ti,twl4030-audio";
>> + codec {
>> + };
>> + };
>> };
>> };
>>
>> @@ -86,10 +105,6 @@
>> status = "disabled";
>> };
>>
>> - {
>> - status = "disabled";
>> -};
>> -
>> {
>> status = "disabled";
>> };
>>
>
>
> --
> Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: FW: [PATCH V4] ARM: dts: add minimal DT support for DevKit8000.
Hi,
>
> DevKit8000 is a beagle board clone from Timll, sold by
> armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
> S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
> JTAG interface.
>
> This patch adds the basic DT support for devkit8000. At this time, Information
> of twl4030 (PMIC), MMC1, I2C1 and leds are added.
>
> Signed-off-by: Anil Kumar
> Tested-by: Thomas Weber
Gentle Ping. As there are no review comments on this patch,
Could you please pull this patch ?
Thanks,
Anil
> ---
> -This patch is based on top of kernel 3.8-rc5.
>
> -Tested on Devkit8000.
>
> For V4:
> -Tiny nitpick.
>
> For V3:
> - Remove pin mux as done at device boot time by default.
>
> For V2:
> - Change model name as "TimLL OMAP3 Devkit8000"
> - Change compatible as "timll,omap3-devkit8000"
> - Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
>driver probe time.
>
> :100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
> :00 100644 000... 2e1463a... A arch/arm/boot/dts/omap3-devkit8000.dts
> :100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
> arch/arm/boot/dts/Makefile |1 +
> arch/arm/boot/dts/omap3-devkit8000.dts | 102
>
> arch/arm/mach-omap2/board-generic.c|1 +
> 3 files changed, 104 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index 5ebb44f..22ebc76 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
> imx28-tx28.dtb
> dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
> omap3-beagle.dtb \
> + omap3-devkit8000.dtb \
> omap3-beagle-xm.dtb \
> omap3-evm.dtb \
> omap3-tobi.dtb \
> diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
> b/arch/arm/boot/dts/omap3-devkit8000.dts
> new file mode 100644
> index 000..2e1463a
> --- /dev/null
> +++ b/arch/arm/boot/dts/omap3-devkit8000.dts
> @@ -0,0 +1,102 @@
> +/*
> + * Author: Anil Kumar
> + *
> + * 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.
> + */
> +/dts-v1/;
> +
> +/include/ "omap3.dtsi"
> +/ {
> + model = "TimLL OMAP3 Devkit8000";
> + compatible = "timll,omap3-devkit8000", "ti,omap3";
> +
> + memory {
> + device_type = "memory";
> + reg = <0x8000 0x1000>; /* 256 MB */
> + };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + heartbeat {
> + label = "devkit8000::led1";
> + gpios = < 26 0>; /* 186 -> LED1 */
> + default-state = "on";
> + linux,default-trigger = "heartbeat";
> + };
> +
> + mmc {
> + label = "devkit8000::led2";
> + gpios = < 3 0>; /* 163 -> LED2 */
> + default-state = "on";
> + linux,default-trigger = "none";
> + };
> +
> + usr {
> + label = "devkit8000::led3";
> + gpios = < 4 0>; /* 164 -> LED3 */
> + default-state = "on";
> + linux,default-trigger = "usr";
> +};
> + };
> +};
> +
> + {
> + clock-frequency = <260>;
> +
> + twl: twl@48 {
> + reg = <0x48>;
> + interrupts = <7>; /* SYS_NIRQ cascaded to intc */
> + interrupt-parent = <>;
> + };
> +};
> +
> + {
> + status = "disabled";
> +};
> +
> + {
> + status = "disabled";
> +};
> +
> +/include/ "twl4030.dtsi"
> +
> + {
> + vmmc-supply = <>;
> + vmmc_aux-supply = <>;
> + bus-width = <8>;
> +};
> +
> + {
> + status = "disabled";
> +};
> +
> + {
> + status = "disabled";
> +};
> +
> + {
> + status = "disabled";
> +};
> +
> + {
> + status = "disabled";
> +};
> +
> + {
> + status = "disabled";
> +};
&g
Re: FW: [PATCH V4] ARM: dts: add minimal DT support for DevKit8000.
Hi,
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030 (PMIC), MMC1, I2C1 and leds are added.
Signed-off-by: Anil Kumar anilk...@gmail.com
Tested-by: Thomas Weber tho...@tomweber.eu
Gentle Ping. As there are no review comments on this patch,
Could you please pull this patch ?
Thanks,
Anil
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V4:
-Tiny nitpick.
For V3:
- Remove pin mux as done at device boot time by default.
For V2:
- Change model name as TimLL OMAP3 Devkit8000
- Change compatible as timll,omap3-devkit8000
- Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 2e1463a... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 102
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 104 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..2e1463a
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,102 @@
+/*
+ * Author: Anil Kumar anilk...@gmail.com
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ omap3.dtsi
+/ {
+ model = TimLL OMAP3 Devkit8000;
+ compatible = timll,omap3-devkit8000, ti,omap3;
+
+ memory {
+ device_type = memory;
+ reg = 0x8000 0x1000; /* 256 MB */
+ };
+
+ leds {
+ compatible = gpio-leds;
+
+ heartbeat {
+ label = devkit8000::led1;
+ gpios = gpio6 26 0; /* 186 - LED1 */
+ default-state = on;
+ linux,default-trigger = heartbeat;
+ };
+
+ mmc {
+ label = devkit8000::led2;
+ gpios = gpio6 3 0; /* 163 - LED2 */
+ default-state = on;
+ linux,default-trigger = none;
+ };
+
+ usr {
+ label = devkit8000::led3;
+ gpios = gpio6 4 0; /* 164 - LED3 */
+ default-state = on;
+ linux,default-trigger = usr;
+};
+ };
+};
+
+i2c1 {
+ clock-frequency = 260;
+
+ twl: twl@48 {
+ reg = 0x48;
+ interrupts = 7; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = intc;
+ };
+};
+
+i2c2 {
+ status = disabled;
+};
+
+i2c3 {
+ status = disabled;
+};
+
+/include/ twl4030.dtsi
+
+mmc1 {
+ vmmc-supply = vmmc1;
+ vmmc_aux-supply = vsim;
+ bus-width = 8;
+};
+
+mmc2 {
+ status = disabled;
+};
+
+mmc3 {
+ status = disabled;
+};
+
+wdt2 {
+ status = disabled;
+};
+
+mcbsp1 {
+ status = disabled;
+};
+
+mcbsp2 {
+ status = disabled;
+};
+
+mcbsp3 {
+ status = disabled;
+};
+
+mcbsp4 {
+ status = disabled;
+};
+
+mcbsp5 {
+ status = disabled;
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..ccecb76 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
ti,omap3-beagle,
+ timll,omap3-devkit8000,
NULL,
};
--
1.7.0.4
___
linux-arm-kernel mailing list
linux-arm-ker...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info
Re: [PATCH V2] ARM: dts: omap3-devkit8000: Enable audio support
Hi,
On Mon, Feb 18, 2013 at 4:50 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
On 02/16/2013 08:33 AM, Anil Kumar wrote:
Add the needed sections to enable audio support on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar anilk...@gmail.com
Looks good:
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com
Gentle Ping. As there are no review comments on this patch,
Could you please pull this patch ?
Thanks,
Anil
---
This patch is based on top of kernel 3.8-rc5 and
the following patches.
Peter Ujfalusi:-
ASoC: twl4030: Correct the support for Voice port
ASoC: twl4030: Convert MICBIAS to SUPPLY widget
ASoC: omap-twl4030: Add support for routing, voice port and jack detect
Anil Kumar:-
ARM: dts: add minimal DT support for DevKit8000
https://patchwork.kernel.org/patch/2122461/
-Tested for playback and capture on Devkit8000.
Test process:-
#amixer set 'PredriveR Mixer AudioR2' on
#amixer set 'PredriveL Mixer AudioL2' on
#amixer set PreDriv 100 unmute
#amixer set 'DAC2 Digital Fine' 100
#amixer cset numid=27 1
#arecord | aplay
For V2:
- Remove pin mux as done at device boot time by default.
:100644 100644 6338993... c70116f... M
arch/arm/boot/dts/omap3-devkit8000.dts
arch/arm/boot/dts/omap3-devkit8000.dts | 23 +++
1 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
index 6338993..c70116f 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -42,6 +42,19 @@
};
};
+
+ sound {
+ compatible = ti,omap-twl4030;
+ ti,model = devkit8000;
+
+ ti,mcbsp = mcbsp2;
+ ti,codec = twl_audio;
+ ti,audio-routing =
+ Ext Spk, PREDRIVEL,
+ Ext Spk, PREDRIVER,
+ MAINMIC, Main Mic,
+ Main Mic, Mic Bias 1;
+ };
};
i2c1 {
@@ -51,6 +64,12 @@
reg = 0x48;
interrupts = 7; /* SYS_NIRQ cascaded to intc */
interrupt-parent = intc;
+
+ twl_audio: audio {
+ compatible = ti,twl4030-audio;
+ codec {
+ };
+ };
};
};
@@ -86,10 +105,6 @@
status = disabled;
};
-mcbsp2 {
- status = disabled;
-};
-
mcbsp3 {
status = disabled;
};
--
Péter
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH V4] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030 (PMIC), MMC1, I2C1 and leds are added.
Signed-off-by: Anil Kumar
Tested-by: Thomas Weber
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V4:
-Tiny nitpick.
For V3:
- Remove pin mux as done at device boot time by default.
For V2:
- Change model name as "TimLL OMAP3 Devkit8000"
- Change compatible as "timll,omap3-devkit8000"
- Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 2e1463a... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 102
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 104 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..2e1463a
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,102 @@
+/*
+ * Author: Anil Kumar
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ "omap3.dtsi"
+/ {
+ model = "TimLL OMAP3 Devkit8000";
+ compatible = "timll,omap3-devkit8000", "ti,omap3";
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x1000>; /* 256 MB */
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ heartbeat {
+ label = "devkit8000::led1";
+ gpios = < 26 0>; /* 186 -> LED1 */
+ default-state = "on";
+ linux,default-trigger = "heartbeat";
+ };
+
+ mmc {
+ label = "devkit8000::led2";
+ gpios = < 3 0>; /* 163 -> LED2 */
+ default-state = "on";
+ linux,default-trigger = "none";
+ };
+
+ usr {
+ label = "devkit8000::led3";
+ gpios = < 4 0>; /* 164 -> LED3 */
+ default-state = "on";
+ linux,default-trigger = "usr";
+};
+ };
+};
+
+ {
+ clock-frequency = <260>;
+
+ twl: twl@48 {
+ reg = <0x48>;
+ interrupts = <7>; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = <>;
+ };
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+/include/ "twl4030.dtsi"
+
+ {
+ vmmc-supply = <>;
+ vmmc_aux-supply = <>;
+ bus-width = <8>;
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..ccecb76 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
"ti,omap3-beagle",
+ "timll,omap3-devkit8000",
NULL,
};
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V3] ARM: dts: add minimal DT support for DevKit8000
Hi Manish,
On Wed, Feb 20, 2013 at 5:28 PM, Manish Badarkhe
wrote:
> On Sat, Feb 16, 2013 at 12:49 PM, Anil Kumar wrote:
>> DevKit8000 is a beagle board clone from Timll, sold by
>> armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
>> S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
>> JTAG interface.
>>
>> This patch adds the basic DT support for devkit8000. At this time,
>> Information
>> of twl4030 (PMIC), MMC1, I2C1 and leds are added.
>>
>> Signed-off-by: Anil Kumar
>> Tested-by: Thomas Weber
>> ---
>> -This patch is based on top of kernel 3.8-rc5.
>>
>> -Tested on Devkit8000.
>>
>> For V3:
>> - Remove pin mux as done at device boot time by default.
>>
>> For V2:
>> - Change model name as "TimLL OMAP3 Devkit8000"
>> - Change compatible as "timll,omap3-devkit8000"
>> - Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
>>driver probe time.
>>
>> :100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
>> :00 100644 000... 6338993... A
>> arch/arm/boot/dts/omap3-devkit8000.dts
>> :100644 100644 53cb380b.. ccecb76... M
>> arch/arm/mach-omap2/board-generic.c
>> arch/arm/boot/dts/Makefile |1 +
>> arch/arm/boot/dts/omap3-devkit8000.dts | 103
>>
>> arch/arm/mach-omap2/board-generic.c|1 +
>> 3 files changed, 105 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
>> index 5ebb44f..22ebc76 100644
>> --- a/arch/arm/boot/dts/Makefile
>> +++ b/arch/arm/boot/dts/Makefile
>> @@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
>> imx28-tx28.dtb
>> dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
>> omap3-beagle.dtb \
>> + omap3-devkit8000.dtb \
>> omap3-beagle-xm.dtb \
>> omap3-evm.dtb \
>> omap3-tobi.dtb \
>> diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
>> b/arch/arm/boot/dts/omap3-devkit8000.dts
>> new file mode 100644
>> index 000..6338993
>> --- /dev/null
>> +++ b/arch/arm/boot/dts/omap3-devkit8000.dts
>> @@ -0,0 +1,103 @@
>> +/*
>> + * Author: Anil Kumar
>> + *
>> + * 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.
>> + */
>> +/dts-v1/;
>> +
>> +/include/ "omap3.dtsi"
>> +/ {
>> + model = "TimLL OMAP3 Devkit8000";
>> + compatible = "timll,omap3-devkit8000", "ti,omap3";
>> +
>> + memory {
>> + device_type = "memory";
>> + reg = <0x8000 0x1000>; /* 256 MB */
>> + };
>> +
>> + leds {
>> + compatible = "gpio-leds";
>> +
>> + heartbeat {
>> + label = "devkit8000::led1";
>> + gpios = < 26 0>; /* 186 -> LED1 */
>> + default-state = "on";
>> + linux,default-trigger = "heartbeat";
>> + };
>> +
>> + mmc {
>> + label = "devkit8000::led2";
>> + gpios = < 3 0>; /* 163 -> LED2 */
>> + default-state = "on";
>> + linux,default-trigger = "none";
>> + };
>> +
>> + usr {
>> + label = "devkit8000::led3";
>> + gpios = < 4 0>; /* 164 -> LED3 */
>> + default-state = "on";
>> + linux,default-trigger = "usr";
>> +};
>> +
>
> No need of extra line over here.
ok,
Thanks,
Anil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V3] ARM: dts: add minimal DT support for DevKit8000
Hi Manish,
On Wed, Feb 20, 2013 at 5:28 PM, Manish Badarkhe
badarkhe.man...@gmail.com wrote:
On Sat, Feb 16, 2013 at 12:49 PM, Anil Kumar anilk...@gmail.com wrote:
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time,
Information
of twl4030 (PMIC), MMC1, I2C1 and leds are added.
Signed-off-by: Anil Kumar anilk...@gmail.com
Tested-by: Thomas Weber tho...@tomweber.eu
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V3:
- Remove pin mux as done at device boot time by default.
For V2:
- Change model name as TimLL OMAP3 Devkit8000
- Change compatible as timll,omap3-devkit8000
- Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 6338993... A
arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M
arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 103
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 105 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..6338993
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,103 @@
+/*
+ * Author: Anil Kumar anilk...@gmail.com
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ omap3.dtsi
+/ {
+ model = TimLL OMAP3 Devkit8000;
+ compatible = timll,omap3-devkit8000, ti,omap3;
+
+ memory {
+ device_type = memory;
+ reg = 0x8000 0x1000; /* 256 MB */
+ };
+
+ leds {
+ compatible = gpio-leds;
+
+ heartbeat {
+ label = devkit8000::led1;
+ gpios = gpio6 26 0; /* 186 - LED1 */
+ default-state = on;
+ linux,default-trigger = heartbeat;
+ };
+
+ mmc {
+ label = devkit8000::led2;
+ gpios = gpio6 3 0; /* 163 - LED2 */
+ default-state = on;
+ linux,default-trigger = none;
+ };
+
+ usr {
+ label = devkit8000::led3;
+ gpios = gpio6 4 0; /* 164 - LED3 */
+ default-state = on;
+ linux,default-trigger = usr;
+};
+
No need of extra line over here.
ok,
Thanks,
Anil
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH V4] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030 (PMIC), MMC1, I2C1 and leds are added.
Signed-off-by: Anil Kumar anilk...@gmail.com
Tested-by: Thomas Weber tho...@tomweber.eu
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V4:
-Tiny nitpick.
For V3:
- Remove pin mux as done at device boot time by default.
For V2:
- Change model name as TimLL OMAP3 Devkit8000
- Change compatible as timll,omap3-devkit8000
- Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 2e1463a... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 102
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 104 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..2e1463a
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,102 @@
+/*
+ * Author: Anil Kumar anilk...@gmail.com
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ omap3.dtsi
+/ {
+ model = TimLL OMAP3 Devkit8000;
+ compatible = timll,omap3-devkit8000, ti,omap3;
+
+ memory {
+ device_type = memory;
+ reg = 0x8000 0x1000; /* 256 MB */
+ };
+
+ leds {
+ compatible = gpio-leds;
+
+ heartbeat {
+ label = devkit8000::led1;
+ gpios = gpio6 26 0; /* 186 - LED1 */
+ default-state = on;
+ linux,default-trigger = heartbeat;
+ };
+
+ mmc {
+ label = devkit8000::led2;
+ gpios = gpio6 3 0; /* 163 - LED2 */
+ default-state = on;
+ linux,default-trigger = none;
+ };
+
+ usr {
+ label = devkit8000::led3;
+ gpios = gpio6 4 0; /* 164 - LED3 */
+ default-state = on;
+ linux,default-trigger = usr;
+};
+ };
+};
+
+i2c1 {
+ clock-frequency = 260;
+
+ twl: twl@48 {
+ reg = 0x48;
+ interrupts = 7; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = intc;
+ };
+};
+
+i2c2 {
+ status = disabled;
+};
+
+i2c3 {
+ status = disabled;
+};
+
+/include/ twl4030.dtsi
+
+mmc1 {
+ vmmc-supply = vmmc1;
+ vmmc_aux-supply = vsim;
+ bus-width = 8;
+};
+
+mmc2 {
+ status = disabled;
+};
+
+mmc3 {
+ status = disabled;
+};
+
+wdt2 {
+ status = disabled;
+};
+
+mcbsp1 {
+ status = disabled;
+};
+
+mcbsp2 {
+ status = disabled;
+};
+
+mcbsp3 {
+ status = disabled;
+};
+
+mcbsp4 {
+ status = disabled;
+};
+
+mcbsp5 {
+ status = disabled;
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..ccecb76 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
ti,omap3-beagle,
+ timll,omap3-devkit8000,
NULL,
};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/2] ARM: dts: omap3: Add gpmc node
Hi,
On Sat, Feb 16, 2013 at 5:54 PM, Ezequiel Garcia
wrote:
> Hi Anil,
>
> On Sat, Feb 16, 2013 at 05:08:27PM +0530, Anil Kumar wrote:
>> Add gpmc DT node.
>>
>> Signed-off-by: Anil Kumar
>> ---
>> :100644 100644 1acc261... 9f36531... March/arm/boot/dts/omap3.dtsi
>> arch/arm/boot/dts/omap3.dtsi | 11 +++
>> 1 files changed, 11 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
>> index 1acc261..9f36531 100644
>> --- a/arch/arm/boot/dts/omap3.dtsi
>> +++ b/arch/arm/boot/dts/omap3.dtsi
>> @@ -397,5 +397,16 @@
>> ti,timer-alwon;
>> ti,timer-secure;
>> };
>> +
>> + gpmc: gpmc@6e00 {
>> + compatible = "ti,omap3430-gpmc";
>> + ti,hwmods = "gpmc";
>> + reg = <0x6e00 0x100>;
>> + interrupts = <20>;
>> + gpmc,num-cs = <8>;
>> + gpmc,num-waitpins = <4>;
>> + #address-cells = <2>;
>> + #size-cells = <1>;
>> + };
>> };
>> };
>> --
>> 1.7.0.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majord...@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> This patch has been already sent twice to the mailing list.
> Perhaps it would be more polite if you could base your work on
> one of those instead of sending it yourself again.
>
> Florian Vaussard sent one on January 28th:
> [PATCH 1/2] ARM: dts: OMAP3: Add GPMC controller
ok, I missed this patch. I will re base my changes on of this patch.
>
> Javier Martinez Canillas sent another one on February 09th:
> [PATCH RFC 6/7] ARM: dts: OMAP: Add an GPMC node for OMAP3
>
> Moreover, you could help to get patches merged faster by sending
> your Acked-by or Tested-by.
>
Sure i do that.
Thanks,
Anil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 2/2] ARM: dts: omap3-devkit8000: add nand dt node
Add the needed sections to enable nand support on
Devkit8000.
Add nand partitions information.
Signed-off-by: Anil Kumar
---
:100644 100644 6338993... 6c6decf... M arch/arm/boot/dts/omap3-devkit8000.dts
arch/arm/boot/dts/omap3-devkit8000.dts | 52
1 files changed, 52 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
index 6338993..6c6decf 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -101,3 +101,55 @@
{
status = "disabled";
};
+
+ {
+ ranges = <0 0 0x3000 0x04>; /* CS0: NAND */
+
+ nand@0,0 {
+ reg = <0 0 0>; /* CS0, offset 0 */
+ nand-bus-width = <16>;
+
+ gpmc,sync-clk = <0>;
+ gpmc,cs-on = <0>;
+ gpmc,cs-rd-off = <44>;
+ gpmc,cs-wr-off = <44>;
+ gpmc,adv-on = <6>;
+ gpmc,adv-rd-off = <34>;
+ gpmc,adv-wr-off = <44>;
+ gpmc,we-off = <40>;
+ gpmc,oe-off = <54>;
+ gpmc,access = <64>;
+ gpmc,rd-cycle = <82>;
+ gpmc,wr-cycle = <82>;
+ gpmc,wr-access = <40>;
+ gpmc,wr-data-mux-bus = <0>;
+
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ x-loader@0 {
+ label = "X-Loader";
+ reg = <0 0x8>;
+ };
+
+ bootloaders@8 {
+ label = "U-Boot";
+ reg = <0x8 0x1e>;
+ };
+
+ bootloaders_env@26 {
+ label = "U-Boot Env";
+ reg = <0x26 0x2>;
+ };
+
+ kernel@28 {
+ label = "Kernel";
+ reg = <0x28 0x40>;
+ };
+
+ filesystem@68 {
+ label = "File System";
+ reg = <0x68 0xf98>;
+ };
+ };
+};
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 1/2] ARM: dts: omap3: Add gpmc node
Add gpmc DT node.
Signed-off-by: Anil Kumar
---
:100644 100644 1acc261... 9f36531... M arch/arm/boot/dts/omap3.dtsi
arch/arm/boot/dts/omap3.dtsi | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 1acc261..9f36531 100644
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -397,5 +397,16 @@
ti,timer-alwon;
ti,timer-secure;
};
+
+ gpmc: gpmc@6e00 {
+ compatible = "ti,omap3430-gpmc";
+ ti,hwmods = "gpmc";
+ reg = <0x6e00 0x100>;
+ interrupts = <20>;
+ gpmc,num-cs = <8>;
+ gpmc,num-waitpins = <4>;
+ #address-cells = <2>;
+ #size-cells = <1>;
+ };
};
};
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/2] arm/dts: OMAP3: Add gpmc DT node support
Add gpmc DT node in dtsi file. Add nand DT node and partitions information for devkit8000. This series is based on top of branch âomap-for-v3.9/gpmcâ git tree http://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git and patches. Anil Kumar:- ARM: dts: add minimal DT support for DevKit8000 Jon Hunter:- ARM: OMAP2+: Fix-up gpmc merge error Done basic testing:- - #cat /proc/mtd (shows nand partitions) - Nand partitions by command line. Anil Kumar (2): ARM: dts: omap3: Add gpmc node ARM: dts: omap3-devkit8000: add nand dt node arch/arm/boot/dts/omap3-devkit8000.dts | 52 arch/arm/boot/dts/omap3.dtsi | 11 +++ 2 files changed, 63 insertions(+), 0 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/2] arm/dts: OMAP3: Add gpmc DT node support
Add gpmc DT node in dtsi file. Add nand DT node and partitions information for devkit8000. This series is based on top of branch âomap-for-v3.9/gpmcâ git tree http://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git and patches. Anil Kumar:- ARM: dts: add minimal DT support for DevKit8000 Jon Hunter:- ARM: OMAP2+: Fix-up gpmc merge error Done basic testing:- - #cat /proc/mtd (shows nand partitions) - Nand partitions by command line. Anil Kumar (2): ARM: dts: omap3: Add gpmc node ARM: dts: omap3-devkit8000: add nand dt node arch/arm/boot/dts/omap3-devkit8000.dts | 52 arch/arm/boot/dts/omap3.dtsi | 11 +++ 2 files changed, 63 insertions(+), 0 deletions(-) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 1/2] ARM: dts: omap3: Add gpmc node
Add gpmc DT node.
Signed-off-by: Anil Kumar anilk...@gmail.com
---
:100644 100644 1acc261... 9f36531... M arch/arm/boot/dts/omap3.dtsi
arch/arm/boot/dts/omap3.dtsi | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 1acc261..9f36531 100644
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -397,5 +397,16 @@
ti,timer-alwon;
ti,timer-secure;
};
+
+ gpmc: gpmc@6e00 {
+ compatible = ti,omap3430-gpmc;
+ ti,hwmods = gpmc;
+ reg = 0x6e00 0x100;
+ interrupts = 20;
+ gpmc,num-cs = 8;
+ gpmc,num-waitpins = 4;
+ #address-cells = 2;
+ #size-cells = 1;
+ };
};
};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 2/2] ARM: dts: omap3-devkit8000: add nand dt node
Add the needed sections to enable nand support on
Devkit8000.
Add nand partitions information.
Signed-off-by: Anil Kumar anilk...@gmail.com
---
:100644 100644 6338993... 6c6decf... M arch/arm/boot/dts/omap3-devkit8000.dts
arch/arm/boot/dts/omap3-devkit8000.dts | 52
1 files changed, 52 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
index 6338993..6c6decf 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -101,3 +101,55 @@
mcbsp5 {
status = disabled;
};
+
+gpmc {
+ ranges = 0 0 0x3000 0x04; /* CS0: NAND */
+
+ nand@0,0 {
+ reg = 0 0 0; /* CS0, offset 0 */
+ nand-bus-width = 16;
+
+ gpmc,sync-clk = 0;
+ gpmc,cs-on = 0;
+ gpmc,cs-rd-off = 44;
+ gpmc,cs-wr-off = 44;
+ gpmc,adv-on = 6;
+ gpmc,adv-rd-off = 34;
+ gpmc,adv-wr-off = 44;
+ gpmc,we-off = 40;
+ gpmc,oe-off = 54;
+ gpmc,access = 64;
+ gpmc,rd-cycle = 82;
+ gpmc,wr-cycle = 82;
+ gpmc,wr-access = 40;
+ gpmc,wr-data-mux-bus = 0;
+
+ #address-cells = 1;
+ #size-cells = 1;
+
+ x-loader@0 {
+ label = X-Loader;
+ reg = 0 0x8;
+ };
+
+ bootloaders@8 {
+ label = U-Boot;
+ reg = 0x8 0x1e;
+ };
+
+ bootloaders_env@26 {
+ label = U-Boot Env;
+ reg = 0x26 0x2;
+ };
+
+ kernel@28 {
+ label = Kernel;
+ reg = 0x28 0x40;
+ };
+
+ filesystem@68 {
+ label = File System;
+ reg = 0x68 0xf98;
+ };
+ };
+};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/2] ARM: dts: omap3: Add gpmc node
Hi,
On Sat, Feb 16, 2013 at 5:54 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
Hi Anil,
On Sat, Feb 16, 2013 at 05:08:27PM +0530, Anil Kumar wrote:
Add gpmc DT node.
Signed-off-by: Anil Kumar anilk...@gmail.com
---
:100644 100644 1acc261... 9f36531... March/arm/boot/dts/omap3.dtsi
arch/arm/boot/dts/omap3.dtsi | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 1acc261..9f36531 100644
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -397,5 +397,16 @@
ti,timer-alwon;
ti,timer-secure;
};
+
+ gpmc: gpmc@6e00 {
+ compatible = ti,omap3430-gpmc;
+ ti,hwmods = gpmc;
+ reg = 0x6e00 0x100;
+ interrupts = 20;
+ gpmc,num-cs = 8;
+ gpmc,num-waitpins = 4;
+ #address-cells = 2;
+ #size-cells = 1;
+ };
};
};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This patch has been already sent twice to the mailing list.
Perhaps it would be more polite if you could base your work on
one of those instead of sending it yourself again.
Florian Vaussard sent one on January 28th:
[PATCH 1/2] ARM: dts: OMAP3: Add GPMC controller
ok, I missed this patch. I will re base my changes on of this patch.
Javier Martinez Canillas sent another one on February 09th:
[PATCH RFC 6/7] ARM: dts: OMAP: Add an GPMC node for OMAP3
Moreover, you could help to get patches merged faster by sending
your Acked-by or Tested-by.
Sure i do that.
Thanks,
Anil
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH V2] ARM: dts: omap3-devkit8000: Enable audio support
Add the needed sections to enable audio support on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar
---
This patch is based on top of kernel 3.8-rc5 and
the following patches.
Peter Ujfalusi:-
ASoC: twl4030: Correct the support for Voice port
ASoC: twl4030: Convert MICBIAS to SUPPLY widget
ASoC: omap-twl4030: Add support for routing, voice port and jack detect
Anil Kumar:-
ARM: dts: add minimal DT support for DevKit8000
https://patchwork.kernel.org/patch/2122461/
-Tested for playback and capture on Devkit8000.
Test process:-
#amixer set 'PredriveR Mixer AudioR2' on
#amixer set 'PredriveL Mixer AudioL2' on
#amixer set PreDriv 100 unmute
#amixer set 'DAC2 Digital Fine' 100
#amixer cset numid=27 1
#arecord | aplay
For V2:
- Remove pin mux as done at device boot time by default.
:100644 100644 6338993... c70116f... M arch/arm/boot/dts/omap3-devkit8000.dts
arch/arm/boot/dts/omap3-devkit8000.dts | 23 +++
1 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
index 6338993..c70116f 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -42,6 +42,19 @@
};
};
+
+ sound {
+ compatible = "ti,omap-twl4030";
+ ti,model = "devkit8000";
+
+ ti,mcbsp = <>;
+ ti,codec = <_audio>;
+ ti,audio-routing =
+ "Ext Spk", "PREDRIVEL",
+ "Ext Spk", "PREDRIVER",
+ "MAINMIC", "Main Mic",
+ "Main Mic", "Mic Bias 1";
+ };
};
{
@@ -51,6 +64,12 @@
reg = <0x48>;
interrupts = <7>; /* SYS_NIRQ cascaded to intc */
interrupt-parent = <>;
+
+ twl_audio: audio {
+ compatible = "ti,twl4030-audio";
+ codec {
+ };
+ };
};
};
@@ -86,10 +105,6 @@
status = "disabled";
};
- {
- status = "disabled";
-};
-
{
status = "disabled";
};
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH V3] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030 (PMIC), MMC1, I2C1 and leds are added.
Signed-off-by: Anil Kumar
Tested-by: Thomas Weber
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V3:
- Remove pin mux as done at device boot time by default.
For V2:
- Change model name as "TimLL OMAP3 Devkit8000"
- Change compatible as "timll,omap3-devkit8000"
- Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 6338993... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 103
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 105 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..6338993
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,103 @@
+/*
+ * Author: Anil Kumar
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ "omap3.dtsi"
+/ {
+ model = "TimLL OMAP3 Devkit8000";
+ compatible = "timll,omap3-devkit8000", "ti,omap3";
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x1000>; /* 256 MB */
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ heartbeat {
+ label = "devkit8000::led1";
+ gpios = < 26 0>; /* 186 -> LED1 */
+ default-state = "on";
+ linux,default-trigger = "heartbeat";
+ };
+
+ mmc {
+ label = "devkit8000::led2";
+ gpios = < 3 0>; /* 163 -> LED2 */
+ default-state = "on";
+ linux,default-trigger = "none";
+ };
+
+ usr {
+ label = "devkit8000::led3";
+ gpios = < 4 0>; /* 164 -> LED3 */
+ default-state = "on";
+ linux,default-trigger = "usr";
+};
+
+ };
+};
+
+ {
+ clock-frequency = <260>;
+
+ twl: twl@48 {
+ reg = <0x48>;
+ interrupts = <7>; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = <>;
+ };
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+/include/ "twl4030.dtsi"
+
+ {
+ vmmc-supply = <>;
+ vmmc_aux-supply = <>;
+ bus-width = <8>;
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..ccecb76 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
"ti,omap3-beagle",
+ "timll,omap3-devkit8000",
NULL,
};
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH V3] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030 (PMIC), MMC1, I2C1 and leds are added.
Signed-off-by: Anil Kumar anilk...@gmail.com
Tested-by: Thomas Weber tho...@tomweber.eu
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V3:
- Remove pin mux as done at device boot time by default.
For V2:
- Change model name as TimLL OMAP3 Devkit8000
- Change compatible as timll,omap3-devkit8000
- Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 6338993... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 103
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 105 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..6338993
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,103 @@
+/*
+ * Author: Anil Kumar anilk...@gmail.com
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ omap3.dtsi
+/ {
+ model = TimLL OMAP3 Devkit8000;
+ compatible = timll,omap3-devkit8000, ti,omap3;
+
+ memory {
+ device_type = memory;
+ reg = 0x8000 0x1000; /* 256 MB */
+ };
+
+ leds {
+ compatible = gpio-leds;
+
+ heartbeat {
+ label = devkit8000::led1;
+ gpios = gpio6 26 0; /* 186 - LED1 */
+ default-state = on;
+ linux,default-trigger = heartbeat;
+ };
+
+ mmc {
+ label = devkit8000::led2;
+ gpios = gpio6 3 0; /* 163 - LED2 */
+ default-state = on;
+ linux,default-trigger = none;
+ };
+
+ usr {
+ label = devkit8000::led3;
+ gpios = gpio6 4 0; /* 164 - LED3 */
+ default-state = on;
+ linux,default-trigger = usr;
+};
+
+ };
+};
+
+i2c1 {
+ clock-frequency = 260;
+
+ twl: twl@48 {
+ reg = 0x48;
+ interrupts = 7; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = intc;
+ };
+};
+
+i2c2 {
+ status = disabled;
+};
+
+i2c3 {
+ status = disabled;
+};
+
+/include/ twl4030.dtsi
+
+mmc1 {
+ vmmc-supply = vmmc1;
+ vmmc_aux-supply = vsim;
+ bus-width = 8;
+};
+
+mmc2 {
+ status = disabled;
+};
+
+mmc3 {
+ status = disabled;
+};
+
+wdt2 {
+ status = disabled;
+};
+
+mcbsp1 {
+ status = disabled;
+};
+
+mcbsp2 {
+ status = disabled;
+};
+
+mcbsp3 {
+ status = disabled;
+};
+
+mcbsp4 {
+ status = disabled;
+};
+
+mcbsp5 {
+ status = disabled;
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..ccecb76 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
ti,omap3-beagle,
+ timll,omap3-devkit8000,
NULL,
};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH V2] ARM: dts: omap3-devkit8000: Enable audio support
Add the needed sections to enable audio support on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar anilk...@gmail.com
---
This patch is based on top of kernel 3.8-rc5 and
the following patches.
Peter Ujfalusi:-
ASoC: twl4030: Correct the support for Voice port
ASoC: twl4030: Convert MICBIAS to SUPPLY widget
ASoC: omap-twl4030: Add support for routing, voice port and jack detect
Anil Kumar:-
ARM: dts: add minimal DT support for DevKit8000
https://patchwork.kernel.org/patch/2122461/
-Tested for playback and capture on Devkit8000.
Test process:-
#amixer set 'PredriveR Mixer AudioR2' on
#amixer set 'PredriveL Mixer AudioL2' on
#amixer set PreDriv 100 unmute
#amixer set 'DAC2 Digital Fine' 100
#amixer cset numid=27 1
#arecord | aplay
For V2:
- Remove pin mux as done at device boot time by default.
:100644 100644 6338993... c70116f... M arch/arm/boot/dts/omap3-devkit8000.dts
arch/arm/boot/dts/omap3-devkit8000.dts | 23 +++
1 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
index 6338993..c70116f 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -42,6 +42,19 @@
};
};
+
+ sound {
+ compatible = ti,omap-twl4030;
+ ti,model = devkit8000;
+
+ ti,mcbsp = mcbsp2;
+ ti,codec = twl_audio;
+ ti,audio-routing =
+ Ext Spk, PREDRIVEL,
+ Ext Spk, PREDRIVER,
+ MAINMIC, Main Mic,
+ Main Mic, Mic Bias 1;
+ };
};
i2c1 {
@@ -51,6 +64,12 @@
reg = 0x48;
interrupts = 7; /* SYS_NIRQ cascaded to intc */
interrupt-parent = intc;
+
+ twl_audio: audio {
+ compatible = ti,twl4030-audio;
+ codec {
+ };
+ };
};
};
@@ -86,10 +105,6 @@
status = disabled;
};
-mcbsp2 {
- status = disabled;
-};
-
mcbsp3 {
status = disabled;
};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] ARM: dts: omap3-devkit8000: Enable audio support
Add the needed sections to enable audio support and related pin mux on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar
---
This patch is based on top of kernel 3.8-rc5 and
the following patches.
Peter Ujfalusi:-
ASoC: twl4030: Correct the support for Voice port
ASoC: twl4030: Convert MICBIAS to SUPPLY widget
ASoC: omap-twl4030: Add support for routing, voice port and jack detect
Anil Kumar:-
ARM: dts: add minimal DT support for DevKit8000
https://patchwork.kernel.org/patch/2122461/
-Tested for playback and capture on Devkit8000.
Test process:-
#amixer set 'PredriveR Mixer AudioR2' on
#amixer set 'PredriveL Mixer AudioL2' on
#amixer set PreDriv 100 unmute
#amixer set 'DAC2 Digital Fine' 100
#amixer cset numid=27 1
#arecord | aplay
:100644 100644 dc59272... 1e2c931... M arch/arm/boot/dts/omap3-devkit8000.dts
arch/arm/boot/dts/omap3-devkit8000.dts | 43 ---
1 files changed, 38 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
index dc59272..1e2c931 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -44,11 +44,27 @@
};
};
+
+ sound {
+ compatible = "ti,omap-twl4030";
+ ti,model = "devkit8000";
+
+ ti,mcbsp = <>;
+ ti,codec = <_audio>;
+ ti,audio-routing =
+ "Ext Spk", "PREDRIVEL",
+ "Ext Spk", "PREDRIVER",
+ "MAINMIC", "Main Mic",
+ "Main Mic", "Mic Bias 1";
+ };
};
_pmx_core {
pinctrl-names = "default";
- pinctrl-0 = <_pins>;
+ pinctrl-0 = <
+ _pins
+ _pins
+ >;
leds_pins: pinmux_led_pins {
pinctrl-single,pins = <
@@ -65,6 +81,21 @@
0x18c 0x118 /* I2C1_SDA */
>;
};
+
+ mcbsp2_pins: pinmux_mcbsp2_pins {
+pinctrl-single,pins = <
+ /*
+* MCBSP2_FSX, OMAP_MUX_MODE0 | OMAP_PIN_INPUT,
+* MCBSP2_CLKX, OMAP_MUX_MODE0 | OMAP_PIN_INPUT
+*/
+ 0x10c 0x01000100
+ /*
+* MCBSP2_DR, OMAP_MUX_MODE0 | OMAP_PIN_INPUT,
+* MCBSP2_DX, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT
+*/
+ 0x110 0x0100
+ >;
+ };
};
{
@@ -74,6 +105,12 @@
reg = <0x48>;
interrupts = <7>; /* SYS_NIRQ cascaded to intc */
interrupt-parent = <>;
+
+ twl_audio: audio {
+ compatible = "ti,twl4030-audio";
+ codec {
+ };
+ };
};
};
@@ -109,10 +146,6 @@
status = "disabled";
};
- {
- status = "disabled";
-};
-
{
status = "disabled";
};
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] ARM: dts: omap3-devkit8000: Enable audio support
Add the needed sections to enable audio support and related pin mux on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar anilk...@gmail.com
---
This patch is based on top of kernel 3.8-rc5 and
the following patches.
Peter Ujfalusi:-
ASoC: twl4030: Correct the support for Voice port
ASoC: twl4030: Convert MICBIAS to SUPPLY widget
ASoC: omap-twl4030: Add support for routing, voice port and jack detect
Anil Kumar:-
ARM: dts: add minimal DT support for DevKit8000
https://patchwork.kernel.org/patch/2122461/
-Tested for playback and capture on Devkit8000.
Test process:-
#amixer set 'PredriveR Mixer AudioR2' on
#amixer set 'PredriveL Mixer AudioL2' on
#amixer set PreDriv 100 unmute
#amixer set 'DAC2 Digital Fine' 100
#amixer cset numid=27 1
#arecord | aplay
:100644 100644 dc59272... 1e2c931... M arch/arm/boot/dts/omap3-devkit8000.dts
arch/arm/boot/dts/omap3-devkit8000.dts | 43 ---
1 files changed, 38 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
index dc59272..1e2c931 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -44,11 +44,27 @@
};
};
+
+ sound {
+ compatible = ti,omap-twl4030;
+ ti,model = devkit8000;
+
+ ti,mcbsp = mcbsp2;
+ ti,codec = twl_audio;
+ ti,audio-routing =
+ Ext Spk, PREDRIVEL,
+ Ext Spk, PREDRIVER,
+ MAINMIC, Main Mic,
+ Main Mic, Mic Bias 1;
+ };
};
omap3_pmx_core {
pinctrl-names = default;
- pinctrl-0 = i2c1_pins;
+ pinctrl-0 =
+ i2c1_pins
+ mcbsp2_pins
+ ;
leds_pins: pinmux_led_pins {
pinctrl-single,pins =
@@ -65,6 +81,21 @@
0x18c 0x118 /* I2C1_SDA */
;
};
+
+ mcbsp2_pins: pinmux_mcbsp2_pins {
+pinctrl-single,pins =
+ /*
+* MCBSP2_FSX, OMAP_MUX_MODE0 | OMAP_PIN_INPUT,
+* MCBSP2_CLKX, OMAP_MUX_MODE0 | OMAP_PIN_INPUT
+*/
+ 0x10c 0x01000100
+ /*
+* MCBSP2_DR, OMAP_MUX_MODE0 | OMAP_PIN_INPUT,
+* MCBSP2_DX, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT
+*/
+ 0x110 0x0100
+ ;
+ };
};
i2c1 {
@@ -74,6 +105,12 @@
reg = 0x48;
interrupts = 7; /* SYS_NIRQ cascaded to intc */
interrupt-parent = intc;
+
+ twl_audio: audio {
+ compatible = ti,twl4030-audio;
+ codec {
+ };
+ };
};
};
@@ -109,10 +146,6 @@
status = disabled;
};
-mcbsp2 {
- status = disabled;
-};
-
mcbsp3 {
status = disabled;
};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Sound record on Devkit8000 with DT boot issue
Hi Peter,
On Mon, Feb 11, 2013 at 11:44 PM, Peter Ujfalusi wrote:
> Hi,
>
> On 02/11/2013 06:58 PM, Anil Kumar wrote:
>>> Here you should have something like:
>>> ti,audio-routing =
>>> "Ext Spk", "PREDRIVEL",
>>> "Ext Spk", "PREDRIVER",
>>> "MAINMIC", "Main Mic",
>>> "Main Mic", "Mic Bias 1";
>>>
>>> So you connect the MicBias1 to Main Mic. When you start playback MicBias1
>>> will
>>> be turned on for you.
>>
>> I tried with this routing (next-20130211 tag kernel). But it is not
>> working for me.
>> So i have gone through other board and found snd_soc_dapm_route for
>>
>> 1) zoom2.c
>>{"MAINMIC", NULL, "Mic Bias 1"},
>>{"Mic Bias 1", NULL, "Ext Mic"},
I was giving zoom2 reference from kernel 3.8-rc5.
>>
>> 2) omap3pandora.c
>> {"MAINMIC", NULL, "Mic Bias 1"},
>> {"Mic Bias 1", NULL, "Mic (internal)"},
same as above comment.
>>
>> But for omap-twl4030.c it is
>> {"MAINMIC", NULL, "Main Mic"},
>> {"Main Mic", NULL, "Mic Bias 1"},
>>
>> It Should will be as ?
>> {"MAINMIC", NULL, "Mic Bias 1"},
>> {"Mic Bias 1", NULL, "Main Mic"},
>>
>> Because with this i am able to get audio on Devkit8000 as
>> ti,audio-routing =
>> "Ext Spk", "PREDRIVEL",
>> "Ext Spk", "PREDRIVER",
>> "MAINMIC", "Mic Bias 1",
>> "Mic Bias 1", "Main Mic";
>
> In 3.9 this should not work...
>
> linux-next should not have zoom2 at least and I converted the machine drivers
> as well in regards to micbias handling:
> e04d6e5 ASoC: twl4030: Convert MICBIAS to SUPPLY widget
> 57d61b9 ASoC: OMAP: Remove obsolete machine drivers for Zoom2 and SDP3430
My board is not botting with linux-next ((next-20130211). So i have
taken omap-twl4030.c changes from next-20130211
and merged into 3.8-rc5 as it does have. But missed changes for
twl4030.c. With these all changes it is working for me now .
Sorry for noise.
I am really thanks for this.
Anil
[...]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Sound record on Devkit8000 with DT boot issue
Hi Peter,
Thanks for helping me. please see my comment inline
On Mon, Feb 11, 2013 at 6:47 PM, Peter Ujfalusi wrote:
> On 02/10/2013 04:21 PM, Anil Kumar wrote:
>> Hi All,
>>
>> I am working on Devkit8000 and adding DT support for that. I am trying
>> to add sound DT node support for this boards.
>> I have nearly done with this but facing issue on record. I do not have
>> much knowledge of twl4030 audio codec but with
>> small Hack[1] (as MainMic connected to the input jack) i am able to
>> record sound on Devkit8000.
>> I do not know that MICBIAS1_EN can be enable by amixer commands.
>> Could you please help me to get out of this ?
>
> You need to pass the routing information via DT for Devkit8000. This is not
> done for the BeagleBoard since it works without it (no need for MICBIAS for
> example)
>
>>
>>
>> 1) Hack [1]
>>
>> diff --git a/sound/soc/codecs/twl4030.c b/sound/soc/codecs/twl4030.c
>> index 63b280b..6780681 100644
>> --- a/sound/soc/codecs/twl4030.c
>> +++ b/sound/soc/codecs/twl4030.c
>> @@ -1473,7 +1473,7 @@ static const struct snd_soc_dapm_widget
>> twl4030_dapm_widgets[] = {
>> SND_SOC_DAPM_SUPPLY("micbias2 select", TWL4030_REG_MICBIAS_CTL, 6, 0,
>> NULL, 0),
>>
>> - SND_SOC_DAPM_MICBIAS("Mic Bias 1", TWL4030_REG_MICBIAS_CTL, 0, 0),
>> + SND_SOC_DAPM_MICBIAS("Mic Bias 1", TWL4030_REG_MICBIAS_CTL, 0, 1),
>
> Yes, this is HACK and it is wrong at the same time.
Agree
>
>> SND_SOC_DAPM_MICBIAS("Mic Bias 2", TWL4030_REG_MICBIAS_CTL, 1, 0),
>> SND_SOC_DAPM_MICBIAS("Headset Mic Bias", TWL4030_REG_MICBIAS_CTL, 2,
>> 0),
>>
>>
>> 2) Sound DT node patch for Devkit8000
>>
>> diff --git a/arch/arm/boot/dts/omap3-
>> devkit8000.dts b/arch/arm/boot/dts/omap3-devkit8000.dts
>> index dc59272..5f3eec0 100644
>> --- a/arch/arm/boot/dts/omap3-devkit8000.dts
>> +++ b/arch/arm/boot/dts/omap3-devkit8000.dts
>> @@ -44,11 +44,22 @@
>> };
>>
>> };
>> +
>> + sound {
>> + compatible = "ti,omap-twl4030";
>> + ti,model = "devkit8000";
>> +
>> + ti,mcbsp = <>;
>> + ti,codec = <_audio>;
>
> Here you should have something like:
> ti,audio-routing =
> "Ext Spk", "PREDRIVEL",
> "Ext Spk", "PREDRIVER",
> "MAINMIC", "Main Mic",
> "Main Mic", "Mic Bias 1";
>
> So you connect the MicBias1 to Main Mic. When you start playback MicBias1 will
> be turned on for you.
I tried with this routing (next-20130211 tag kernel). But it is not
working for me.
So i have gone through other board and found snd_soc_dapm_route for
1) zoom2.c
{"MAINMIC", NULL, "Mic Bias 1"},
{"Mic Bias 1", NULL, "Ext Mic"},
2) omap3pandora.c
{"MAINMIC", NULL, "Mic Bias 1"},
{"Mic Bias 1", NULL, "Mic (internal)"},
But for omap-twl4030.c it is
{"MAINMIC", NULL, "Main Mic"},
{"Main Mic", NULL, "Mic Bias 1"},
It Should will be as ?
{"MAINMIC", NULL, "Mic Bias 1"},
{"Mic Bias 1", NULL, "Main Mic"},
Because with this i am able to get audio on Devkit8000 as
ti,audio-routing =
"Ext Spk", "PREDRIVEL",
"Ext Spk", "PREDRIVER",
"MAINMIC", "Mic Bias 1",
"Mic Bias 1", "Main Mic";
Sorry if i am saying nonsense.
Thanks,
Anil
[...]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Sound record on Devkit8000 with DT boot issue
Hi Peter,
Thanks for helping me. please see my comment inline
On Mon, Feb 11, 2013 at 6:47 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
On 02/10/2013 04:21 PM, Anil Kumar wrote:
Hi All,
I am working on Devkit8000 and adding DT support for that. I am trying
to add sound DT node support for this boards.
I have nearly done with this but facing issue on record. I do not have
much knowledge of twl4030 audio codec but with
small Hack[1] (as MainMic connected to the input jack) i am able to
record sound on Devkit8000.
I do not know that MICBIAS1_EN can be enable by amixer commands.
Could you please help me to get out of this ?
You need to pass the routing information via DT for Devkit8000. This is not
done for the BeagleBoard since it works without it (no need for MICBIAS for
example)
1) Hack [1]
diff --git a/sound/soc/codecs/twl4030.c b/sound/soc/codecs/twl4030.c
index 63b280b..6780681 100644
--- a/sound/soc/codecs/twl4030.c
+++ b/sound/soc/codecs/twl4030.c
@@ -1473,7 +1473,7 @@ static const struct snd_soc_dapm_widget
twl4030_dapm_widgets[] = {
SND_SOC_DAPM_SUPPLY(micbias2 select, TWL4030_REG_MICBIAS_CTL, 6, 0,
NULL, 0),
- SND_SOC_DAPM_MICBIAS(Mic Bias 1, TWL4030_REG_MICBIAS_CTL, 0, 0),
+ SND_SOC_DAPM_MICBIAS(Mic Bias 1, TWL4030_REG_MICBIAS_CTL, 0, 1),
Yes, this is HACK and it is wrong at the same time.
Agree
SND_SOC_DAPM_MICBIAS(Mic Bias 2, TWL4030_REG_MICBIAS_CTL, 1, 0),
SND_SOC_DAPM_MICBIAS(Headset Mic Bias, TWL4030_REG_MICBIAS_CTL, 2,
0),
2) Sound DT node patch for Devkit8000
diff --git a/arch/arm/boot/dts/omap3-
devkit8000.dts b/arch/arm/boot/dts/omap3-devkit8000.dts
index dc59272..5f3eec0 100644
--- a/arch/arm/boot/dts/omap3-devkit8000.dts
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -44,11 +44,22 @@
};
};
+
+ sound {
+ compatible = ti,omap-twl4030;
+ ti,model = devkit8000;
+
+ ti,mcbsp = mcbsp2;
+ ti,codec = twl_audio;
Here you should have something like:
ti,audio-routing =
Ext Spk, PREDRIVEL,
Ext Spk, PREDRIVER,
MAINMIC, Main Mic,
Main Mic, Mic Bias 1;
So you connect the MicBias1 to Main Mic. When you start playback MicBias1 will
be turned on for you.
I tried with this routing (next-20130211 tag kernel). But it is not
working for me.
So i have gone through other board and found snd_soc_dapm_route for
1) zoom2.c
{MAINMIC, NULL, Mic Bias 1},
{Mic Bias 1, NULL, Ext Mic},
2) omap3pandora.c
{MAINMIC, NULL, Mic Bias 1},
{Mic Bias 1, NULL, Mic (internal)},
But for omap-twl4030.c it is
{MAINMIC, NULL, Main Mic},
{Main Mic, NULL, Mic Bias 1},
It Should will be as ?
{MAINMIC, NULL, Mic Bias 1},
{Mic Bias 1, NULL, Main Mic},
Because with this i am able to get audio on Devkit8000 as
ti,audio-routing =
Ext Spk, PREDRIVEL,
Ext Spk, PREDRIVER,
MAINMIC, Mic Bias 1,
Mic Bias 1, Main Mic;
Sorry if i am saying nonsense.
Thanks,
Anil
[...]
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Sound record on Devkit8000 with DT boot issue
Hi Peter,
On Mon, Feb 11, 2013 at 11:44 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
Hi,
On 02/11/2013 06:58 PM, Anil Kumar wrote:
Here you should have something like:
ti,audio-routing =
Ext Spk, PREDRIVEL,
Ext Spk, PREDRIVER,
MAINMIC, Main Mic,
Main Mic, Mic Bias 1;
So you connect the MicBias1 to Main Mic. When you start playback MicBias1
will
be turned on for you.
I tried with this routing (next-20130211 tag kernel). But it is not
working for me.
So i have gone through other board and found snd_soc_dapm_route for
1) zoom2.c
{MAINMIC, NULL, Mic Bias 1},
{Mic Bias 1, NULL, Ext Mic},
I was giving zoom2 reference from kernel 3.8-rc5.
2) omap3pandora.c
{MAINMIC, NULL, Mic Bias 1},
{Mic Bias 1, NULL, Mic (internal)},
same as above comment.
But for omap-twl4030.c it is
{MAINMIC, NULL, Main Mic},
{Main Mic, NULL, Mic Bias 1},
It Should will be as ?
{MAINMIC, NULL, Mic Bias 1},
{Mic Bias 1, NULL, Main Mic},
Because with this i am able to get audio on Devkit8000 as
ti,audio-routing =
Ext Spk, PREDRIVEL,
Ext Spk, PREDRIVER,
MAINMIC, Mic Bias 1,
Mic Bias 1, Main Mic;
In 3.9 this should not work...
linux-next should not have zoom2 at least and I converted the machine drivers
as well in regards to micbias handling:
e04d6e5 ASoC: twl4030: Convert MICBIAS to SUPPLY widget
57d61b9 ASoC: OMAP: Remove obsolete machine drivers for Zoom2 and SDP3430
My board is not botting with linux-next ((next-20130211). So i have
taken omap-twl4030.c changes from next-20130211
and merged into 3.8-rc5 as it does have. But missed changes for
twl4030.c. With these all changes it is working for me now .
Sorry for noise.
I am really thanks for this.
Anil
[...]
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH V2] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030, MMC1, I2C1, leds and there pim mux information are added.
Signed-off-by: Anil Kumar
Tested-by: Thomas Weber
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V2:
-Change model name as "TimLL OMAP3 Devkit8000"
-Change compatible as "timll,omap3-devkit8000"
-Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... dc59272... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 126
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 128 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..dc59272
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,126 @@
+/*
+ * Author: Anil Kumar
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ "omap3.dtsi"
+/ {
+ model = "TimLL OMAP3 Devkit8000";
+ compatible = "timll,omap3-devkit8000", "ti,omap3";
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x1000>; /* 256 MB */
+ };
+
+ leds {
+ compatible = "gpio-leds";
+ pinctrl-names = "default";
+ pinctrl-0 = <_pins>;
+
+ heartbeat {
+ label = "devkit8000::led1";
+ gpios = < 26 0>; /* 186 -> LED1 */
+ default-state = "on";
+ linux,default-trigger = "heartbeat";
+ };
+
+ mmc {
+ label = "devkit8000::led2";
+ gpios = < 3 0>; /* 163 -> LED2 */
+ default-state = "on";
+ linux,default-trigger = "none";
+ };
+
+ usr {
+ label = "devkit8000::led3";
+ gpios = < 4 0>; /* 164 -> LED3 */
+ default-state = "on";
+ linux,default-trigger = "usr";
+};
+
+ };
+};
+
+_pmx_core {
+ pinctrl-names = "default";
+ pinctrl-0 = <_pins>;
+
+ leds_pins: pinmux_led_pins {
+ pinctrl-single,pins = <
+ 0x168 0x4 /* GPIO_163 */
+ 0x16c 0x4 /* GPIO_164 */
+ 0x1b0 0x4 /* GPIO_186 */
+
+ >;
+ };
+
+ i2c1_pins: pinmux_i2c1_pins {
+ pinctrl-single,pins = <
+ 0x188 0x118 /* I2C1_SCL */
+ 0x18c 0x118 /* I2C1_SDA */
+>;
+ };
+};
+
+ {
+ clock-frequency = <260>;
+
+ twl: twl@48 {
+ reg = <0x48>;
+ interrupts = <7>; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = <>;
+ };
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+/include/ "twl4030.dtsi"
+
+ {
+ vmmc-supply = <>;
+ vmmc_aux-supply = <>;
+ bus-width = <8>;
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mac
[PATCH V2] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030, MMC1, I2C1, leds and there pim mux information are added.
Signed-off-by: Anil Kumar anilk...@gmail.com
Tested-by: Thomas Weber tho...@tomweber.eu
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
For V2:
-Change model name as TimLL OMAP3 Devkit8000
-Change compatible as timll,omap3-devkit8000
-Doing i2c1 pinmux default with pinctrl-single driver instead of i2c1
driver probe time.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... dc59272... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. ccecb76... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 126
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 128 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..dc59272
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,126 @@
+/*
+ * Author: Anil Kumar anilk...@gmail.com
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ omap3.dtsi
+/ {
+ model = TimLL OMAP3 Devkit8000;
+ compatible = timll,omap3-devkit8000, ti,omap3;
+
+ memory {
+ device_type = memory;
+ reg = 0x8000 0x1000; /* 256 MB */
+ };
+
+ leds {
+ compatible = gpio-leds;
+ pinctrl-names = default;
+ pinctrl-0 = leds_pins;
+
+ heartbeat {
+ label = devkit8000::led1;
+ gpios = gpio6 26 0; /* 186 - LED1 */
+ default-state = on;
+ linux,default-trigger = heartbeat;
+ };
+
+ mmc {
+ label = devkit8000::led2;
+ gpios = gpio6 3 0; /* 163 - LED2 */
+ default-state = on;
+ linux,default-trigger = none;
+ };
+
+ usr {
+ label = devkit8000::led3;
+ gpios = gpio6 4 0; /* 164 - LED3 */
+ default-state = on;
+ linux,default-trigger = usr;
+};
+
+ };
+};
+
+omap3_pmx_core {
+ pinctrl-names = default;
+ pinctrl-0 = i2c1_pins;
+
+ leds_pins: pinmux_led_pins {
+ pinctrl-single,pins =
+ 0x168 0x4 /* GPIO_163 */
+ 0x16c 0x4 /* GPIO_164 */
+ 0x1b0 0x4 /* GPIO_186 */
+
+ ;
+ };
+
+ i2c1_pins: pinmux_i2c1_pins {
+ pinctrl-single,pins =
+ 0x188 0x118 /* I2C1_SCL */
+ 0x18c 0x118 /* I2C1_SDA */
+;
+ };
+};
+
+i2c1 {
+ clock-frequency = 260;
+
+ twl: twl@48 {
+ reg = 0x48;
+ interrupts = 7; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = intc;
+ };
+};
+
+i2c2 {
+ status = disabled;
+};
+
+i2c3 {
+ status = disabled;
+};
+
+/include/ twl4030.dtsi
+
+mmc1 {
+ vmmc-supply = vmmc1;
+ vmmc_aux-supply = vsim;
+ bus-width = 8;
+};
+
+mmc2 {
+ status = disabled;
+};
+
+mmc3 {
+ status = disabled;
+};
+
+wdt2 {
+ status = disabled;
+};
+
+mcbsp1 {
+ status = disabled;
+};
+
+mcbsp2 {
+ status = disabled;
+};
+
+mcbsp3 {
+ status = disabled;
+};
+
+mcbsp4 {
+ status = disabled;
+};
+
+mcbsp5 {
+ status = disabled;
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..ccecb76 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
ti,omap3-beagle,
+ timll,omap3-devkit8000,
NULL,
};
--
1.7.0.4
--
To unsubscribe
[PATCH] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030, MMC1, I2C1, leds and there pim mux information are added.
Signed-off-by: Anil Kumar
Tested-by: Thomas Weber
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 9864fd7... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. 6e2cef6... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 125
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 127 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..9864fd7
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,125 @@
+/*
+ * Anil Kumar
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ "omap3.dtsi"
+/ {
+ model = "TI OMAP3 Devkit8000";
+ compatible = "ti,omap3-devkit8000", "ti,omap3";
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x1000>; /* 256 MB */
+ };
+
+ leds {
+ compatible = "gpio-leds";
+ pinctrl-names = "default";
+ pinctrl-0 = <_pins>;
+
+ heartbeat {
+ label = "devkit8000::led1";
+ gpios = < 26 0>; /* 186 -> LED1 */
+ default-state = "on";
+ linux,default-trigger = "heartbeat";
+ };
+
+ mmc {
+ label = "devkit8000::led2";
+ gpios = < 3 0>; /* 163 -> LED2 */
+ default-state = "on";
+ linux,default-trigger = "none";
+ };
+
+ usr {
+ label = "devkit8000::led3";
+ gpios = < 4 0>; /* 164 -> LED3 */
+ default-state = "on";
+ linux,default-trigger = "usr";
+};
+
+ };
+};
+
+_pmx_core {
+ leds_pins: pinmux_led_pins {
+ pinctrl-single,pins = <
+ 0x168 0x4 /* GPIO_163 */
+ 0x16c 0x4 /* GPIO_164 */
+ 0x1b0 0x4 /* GPIO_186 */
+
+ >;
+ };
+
+ i2c1_pins: pinmux_i2c1_pins {
+ pinctrl-single,pins = <
+ 0x188 0x118 /* I2C1_SCL */
+ 0x18c 0x118 /* I2C1_SDA */
+>;
+ };
+};
+
+ {
+ pinctrl-names = "default";
+ pinctrl-0 = <_pins>;
+ clock-frequency = <260>;
+
+ twl: twl@48 {
+ reg = <0x48>;
+ interrupts = <7>; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = <>;
+ };
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+/include/ "twl4030.dtsi"
+
+ {
+ vmmc-supply = <>;
+ vmmc_aux-supply = <>;
+ bus-width = <8>;
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
+
+ {
+ status = "disabled";
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..6e2cef6 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
"ti,omap3-beagle",
+ "ti,omap3-devkit8000",
NULL,
};
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] ARM: dts: add minimal DT support for DevKit8000
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030, MMC1, I2C1, leds and there pim mux information are added.
Signed-off-by: Anil Kumar anilk...@gmail.com
Tested-by: Thomas Weber tho...@tomweber.eu
---
-This patch is based on top of kernel 3.8-rc5.
-Tested on Devkit8000.
:100644 100644 5ebb44f... 22ebc76... M arch/arm/boot/dts/Makefile
:00 100644 000... 9864fd7... A arch/arm/boot/dts/omap3-devkit8000.dts
:100644 100644 53cb380b.. 6e2cef6... M arch/arm/mach-omap2/board-generic.c
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3-devkit8000.dts | 125
arch/arm/mach-omap2/board-generic.c|1 +
3 files changed, 127 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 5ebb44f..22ebc76 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -102,6 +102,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \
imx28-tx28.dtb
dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
omap3-beagle.dtb \
+ omap3-devkit8000.dtb \
omap3-beagle-xm.dtb \
omap3-evm.dtb \
omap3-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-devkit8000.dts
b/arch/arm/boot/dts/omap3-devkit8000.dts
new file mode 100644
index 000..9864fd7
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-devkit8000.dts
@@ -0,0 +1,125 @@
+/*
+ * Anil Kumar anilk...@gmail.com
+ *
+ * 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.
+ */
+/dts-v1/;
+
+/include/ omap3.dtsi
+/ {
+ model = TI OMAP3 Devkit8000;
+ compatible = ti,omap3-devkit8000, ti,omap3;
+
+ memory {
+ device_type = memory;
+ reg = 0x8000 0x1000; /* 256 MB */
+ };
+
+ leds {
+ compatible = gpio-leds;
+ pinctrl-names = default;
+ pinctrl-0 = leds_pins;
+
+ heartbeat {
+ label = devkit8000::led1;
+ gpios = gpio6 26 0; /* 186 - LED1 */
+ default-state = on;
+ linux,default-trigger = heartbeat;
+ };
+
+ mmc {
+ label = devkit8000::led2;
+ gpios = gpio6 3 0; /* 163 - LED2 */
+ default-state = on;
+ linux,default-trigger = none;
+ };
+
+ usr {
+ label = devkit8000::led3;
+ gpios = gpio6 4 0; /* 164 - LED3 */
+ default-state = on;
+ linux,default-trigger = usr;
+};
+
+ };
+};
+
+omap3_pmx_core {
+ leds_pins: pinmux_led_pins {
+ pinctrl-single,pins =
+ 0x168 0x4 /* GPIO_163 */
+ 0x16c 0x4 /* GPIO_164 */
+ 0x1b0 0x4 /* GPIO_186 */
+
+ ;
+ };
+
+ i2c1_pins: pinmux_i2c1_pins {
+ pinctrl-single,pins =
+ 0x188 0x118 /* I2C1_SCL */
+ 0x18c 0x118 /* I2C1_SDA */
+;
+ };
+};
+
+i2c1 {
+ pinctrl-names = default;
+ pinctrl-0 = i2c1_pins;
+ clock-frequency = 260;
+
+ twl: twl@48 {
+ reg = 0x48;
+ interrupts = 7; /* SYS_NIRQ cascaded to intc */
+ interrupt-parent = intc;
+ };
+};
+
+i2c2 {
+ status = disabled;
+};
+
+i2c3 {
+ status = disabled;
+};
+
+/include/ twl4030.dtsi
+
+mmc1 {
+ vmmc-supply = vmmc1;
+ vmmc_aux-supply = vsim;
+ bus-width = 8;
+};
+
+mmc2 {
+ status = disabled;
+};
+
+mmc3 {
+ status = disabled;
+};
+
+wdt2 {
+ status = disabled;
+};
+
+mcbsp1 {
+ status = disabled;
+};
+
+mcbsp2 {
+ status = disabled;
+};
+
+mcbsp3 {
+ status = disabled;
+};
+
+mcbsp4 {
+ status = disabled;
+};
+
+mcbsp5 {
+ status = disabled;
+};
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index 53cb380..6e2cef6 100644
--- a/arch/arm/mach-omap2/board-generic.c
+++ b/arch/arm/mach-omap2/board-generic.c
@@ -110,6 +110,7 @@ MACHINE_END
static const char *omap3_gp_boards_compat[] __initdata = {
ti,omap3-beagle,
+ ti,omap3-devkit8000,
NULL,
};
--
1.7.0.4
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
noapic for smp
Hi, I have a rhel4 (2.6.9-5.EL) system. The SMP kernel boot fails(rather locks up system). But when use "noapic" it boots fine. Is it that my system "APIC" is bad? Will "noapic" have performance impact (IRQ routing,etc)? My system is a Uni processor with HT enabled. with regards, Anil __ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
noapic for smp
Hi, I have a rhel4 (2.6.9-5.EL) system. The SMP kernel boot fails(rather locks up system). But when use noapic it boots fine. Is it that my system APIC is bad? Will noapic have performance impact (IRQ routing,etc)? My system is a Uni processor with HT enabled. with regards, Anil __ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
driver compile parse errors for RHEL4
Hi,
I am getting parse errors when I try to build aic7xxx( Adaptec SCSI
controller) driver for RHEL4.
I am using my own build enviroment (I mean Makefiles, scripts) to build this.
#gcc -v
Reading specs from
/usr/adaptec/build/gcc343-32bit/lib/gcc/i386-redhat-linux/3.4.3/specs
Configured with: ./configure --prefix=/usr/adaptec/build/gcc343-32bit
--enable-threads=posix --disable-checking --target=i386-redhat-linux
--host=i686-redhat-linux-gnu
--with-libs=/usr/adaptec/build/gcc343-32bit/lib
--with-headers=/usr/adaptec/build/gcc343-32bit/include
--enable-languages=c --disable-libunwind-exceptions --with-system-zlib
--enable-__cxa_atexit --enable-java-awt=gtk --enable-shared
--mandir=/usr/adaptec/build/gcc343-32bit/man
--infodir=/usr/adaptec/build/gcc343-32bit/info
Thread model: posix
gcc version 3.4.3
The sources for the driver can be found under
/usr/src/linux/driver/scsi/aic7xxx when you download 2.6.9 kernel from
www.kernel.org.
The errors are as follows:
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:23: error: parse error before '(' token
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:40: error: parse error before '(' token
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:57: error: parse error before '(' token
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:82: error: parse error before '(' token
Can you please let me know if my gcc is installed correctly, I mean if
I disable/enable any of the flags. If not I will look into my
Makefiles and scripts.
with regards,
Anil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
driver compile parse errors for RHEL4
Hi,
I am getting parse errors when I try to build aic7xxx( Adaptec SCSI
controller) driver for RHEL4.
I am using my own build enviroment (I mean Makefiles, scripts) to build this.
#gcc -v
Reading specs from
/usr/adaptec/build/gcc343-32bit/lib/gcc/i386-redhat-linux/3.4.3/specs
Configured with: ./configure --prefix=/usr/adaptec/build/gcc343-32bit
--enable-threads=posix --disable-checking --target=i386-redhat-linux
--host=i686-redhat-linux-gnu
--with-libs=/usr/adaptec/build/gcc343-32bit/lib
--with-headers=/usr/adaptec/build/gcc343-32bit/include
--enable-languages=c --disable-libunwind-exceptions --with-system-zlib
--enable-__cxa_atexit --enable-java-awt=gtk --enable-shared
--mandir=/usr/adaptec/build/gcc343-32bit/man
--infodir=/usr/adaptec/build/gcc343-32bit/info
Thread model: posix
gcc version 3.4.3
The sources for the driver can be found under
/usr/src/linux/driver/scsi/aic7xxx when you download 2.6.9 kernel from
www.kernel.org.
The errors are as follows:
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:23: error: parse error before '(' token
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:40: error: parse error before '(' token
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:57: error: parse error before '(' token
drivers/scsi/aic7xxx/aic7xxx_reg_print.c:82: error: parse error before '(' token
Can you please let me know if my gcc is installed correctly, I mean if
I disable/enable any of the flags. If not I will look into my
Makefiles and scripts.
with regards,
Anil
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
module insert question
Hi, Can you please let me know, what all files does the OS look into to load modules? I see the following messages during boot rather installation: == Finished bus probing modules to insert tg3 aic79xx == which files does the OS look into to load tg3 and aic79xx after finishing bus probing. I guess modprobe.conf, modules.alias, modules.pcimap. with regards, Anil - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
module insert question
Hi, Can you please let me know, what all files does the OS look into to load modules? I see the following messages during boot rather installation: == Finished bus probing modules to insert tg3 aic79xx == which files does the OS look into to load tg3 and aic79xx after finishing bus probing. I guess modprobe.conf, modules.alias, modules.pcimap. with regards, Anil - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
loading driver automatically & manually
Hi, I am trying to install RHEL 4, 2.6.9-5.EL. I have adaptec 39320 controller, The install CD already has aic79xx driver in it. The driver does NOT load for some reason. If I take the same aic79xx driver source, Create an img and install RHEL4 using linux dd, it works fine. Can you please let me know, what files/lookup tables does the OS look into for loading a driver for 2.6? Also can you please point me to steps on to how to replace an existing driver(I suspect the default driver in RHEL4 CD may be wrong) in the RHEL4 install CD with my own aic79xx built driver? with regards, Anil - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
loading driver automatically manually
Hi, I am trying to install RHEL 4, 2.6.9-5.EL. I have adaptec 39320 controller, The install CD already has aic79xx driver in it. The driver does NOT load for some reason. If I take the same aic79xx driver source, Create an img and install RHEL4 using linux dd, it works fine. Can you please let me know, what files/lookup tables does the OS look into for loading a driver for 2.6? Also can you please point me to steps on to how to replace an existing driver(I suspect the default driver in RHEL4 CD may be wrong) in the RHEL4 install CD with my own aic79xx built driver? with regards, Anil - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
driver compile Parse error with gcc-3.4.3
Hi,
I am new to linux. I am trying to build one of my drivers for
2.6.9-5.EL, RHEL 4, I am getting compile parse errors as follows:
error: parse error before '(' token
#gcc -v
Configured with: ./configure --prefix=/usr/adaptec/build/gcc343-32bit
--enable-threads=posix --disable-checking --target=i386-redhat-linux
--host=i686-redhat-linux-gnu
--with-libs=/usr/adaptec/build/gcc343-32bit/lib
--with-headers=/usr/adaptec/build/gcc343-32bit/include
--enable-languages=c --disable-libunwind-exceptions --with-system-zlib
--enable-__cxa_atexit --enable-java-awt=gtk --enable-shared
--mandir=/usr/adaptec/build/gcc343-32bit/man
--infodir=/usr/adaptec/build/gcc343-32bit/info
Thread model: posix
gcc version 3.4.3
regards,
Anil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
driver compile Parse error with gcc-3.4.3
Hi,
I am new to linux. I am trying to build one of my drivers for
2.6.9-5.EL, RHEL 4, I am getting compile parse errors as follows:
error: parse error before '(' token
#gcc -v
Configured with: ./configure --prefix=/usr/adaptec/build/gcc343-32bit
--enable-threads=posix --disable-checking --target=i386-redhat-linux
--host=i686-redhat-linux-gnu
--with-libs=/usr/adaptec/build/gcc343-32bit/lib
--with-headers=/usr/adaptec/build/gcc343-32bit/include
--enable-languages=c --disable-libunwind-exceptions --with-system-zlib
--enable-__cxa_atexit --enable-java-awt=gtk --enable-shared
--mandir=/usr/adaptec/build/gcc343-32bit/man
--infodir=/usr/adaptec/build/gcc343-32bit/info
Thread model: posix
gcc version 3.4.3
regards,
Anil
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
RE: Validation of memory allocated through kmalloc
use sys_mprotect(...) to verify the validity of the returned address. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Sunday, June 10, 2001 2:45 PM To: [EMAIL PROTECTED] Subject: Validation of memory allocated through kmalloc Hi, Is there some kernel api to validate memory allocated using kmalloc. Suppose, I allocate some memory using kmalloc and at a later point of execution I would like to validate if the memory allocated is not possibly freed by some other thread. Pls suggest a patch/pointers if any. I also noticed a commented 'CONFIG_DEBUG_MALLOC' config option (2.4.3 source), It doesn't seem to be functional. Any pointers towards the history behind it would also be helpful. Thanks in advance, Kiran - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ DISCLAIMER: This correspondence is confidential and intended for the named recipient(s) only. If you are not the named recipient and receive this correspondence in error, you must not copy, distribute or take any action in reliance on it and you should delete it from your system and notify the sender immediately. Unless otherwise stated, any views or opinions expressed are solely those of the author and do not represent those of Subex Systems Limited. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Validation of memory allocated through kmalloc
use sys_mprotect(...) to verify the validity of the returned address. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Sunday, June 10, 2001 2:45 PM To: [EMAIL PROTECTED] Subject: Validation of memory allocated through kmalloc Hi, Is there some kernel api to validate memory allocated using kmalloc. Suppose, I allocate some memory using kmalloc and at a later point of execution I would like to validate if the memory allocated is not possibly freed by some other thread. Pls suggest a patch/pointers if any. I also noticed a commented 'CONFIG_DEBUG_MALLOC' config option (2.4.3 source), It doesn't seem to be functional. Any pointers towards the history behind it would also be helpful. Thanks in advance, Kiran - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ DISCLAIMER: This correspondence is confidential and intended for the named recipient(s) only. If you are not the named recipient and receive this correspondence in error, you must not copy, distribute or take any action in reliance on it and you should delete it from your system and notify the sender immediately. Unless otherwise stated, any views or opinions expressed are solely those of the author and do not represent those of Subex Systems Limited. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: sizeof problem in kernel modules
struct { short x; long y; short z; }bad_struct;
struct { long y; short x; short z; }good_struct;
I would expect both structs to be 8byte in size , or atleast the same size !
but good_struct turns out to be 8bytes and bad_struct 12 .
what am I doing wrong here ?
thx !
hofrat
///
It's general padding performed everywhere for a 32-bit m/c. Since the short
number is considered to be of 2 bytes whereas new data should start at the
next 32 bit alignment( if the data length exceeds the padding required )
hence next 2 bytes are left as padding, so the actual struct. of your
defined structutres are as follows,
struct{
short x; /* 2- bytes */
/* again 2- bytes padding */
long y; /* 4 - bytes */
short z; /* 2 - bytes */
/* again 2 - bytes padding
}bad_struct;
struct{
long y; /* 4 - bytes */
short x; /* 2 - bytes */
short z; /* 2 - bytes */
}good_struct;
anil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
RE: sizeof problem in kernel modules
struct { short x; long y; short z; }bad_struct;
struct { long y; short x; short z; }good_struct;
I would expect both structs to be 8byte in size , or atleast the same size !
but good_struct turns out to be 8bytes and bad_struct 12 .
what am I doing wrong here ?
thx !
hofrat
///
It's general padding performed everywhere for a 32-bit m/c. Since the short
number is considered to be of 2 bytes whereas new data should start at the
next 32 bit alignment( if the data length exceeds the padding required )
hence next 2 bytes are left as padding, so the actual struct. of your
defined structutres are as follows,
struct{
short x; /* 2- bytes */
/* again 2- bytes padding */
long y; /* 4 - bytes */
short z; /* 2 - bytes */
/* again 2 - bytes padding
}bad_struct;
struct{
long y; /* 4 - bytes */
short x; /* 2 - bytes */
short z; /* 2 - bytes */
}good_struct;
anil
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
RE: threading question
Since while using only a small subset of primitives provided by the pthreads the burden for the other primitive maintanence is much more so i too feel when we use only a small part its better to implement in our own requiredd way for performance issues. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of bert hubert Sent: Friday, June 15, 2001 12:32 AM To: Alan Cox Cc: Kip Macy; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: threading question On Thu, Jun 14, 2001 at 07:28:32PM +0100, Alan Cox wrote: > There are really only two reasons for threaded programming. > > - Poor programmer skills/language expression of event handling The converse is that pthreads are: - Very easy to use from C at a reasonable runtime overhead It is very convenient for a userspace coder to be able to just start a function in a different thread. Now it might be so that a kernel is not there to provide ease of use for userspace coders but it is a factor. I see lots of people only using: pthread_create()/pthread_join() mutex_lock/unlock sem_post/sem_wait no signals My gut feeling is that you could implement this subset in a way that is both fast and right - although it would not be 'pthreads compliant'. Can anybody confirm this feeling? Regards, bert -- http://www.PowerDNS.com Versatile DNS Services Trilab The Technology People 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: threading question
Since while using only a small subset of primitives provided by the pthreads the burden for the other primitive maintanence is much more so i too feel when we use only a small part its better to implement in our own requiredd way for performance issues. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of bert hubert Sent: Friday, June 15, 2001 12:32 AM To: Alan Cox Cc: Kip Macy; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: threading question On Thu, Jun 14, 2001 at 07:28:32PM +0100, Alan Cox wrote: There are really only two reasons for threaded programming. - Poor programmer skills/language expression of event handling The converse is that pthreads are: - Very easy to use from C at a reasonable runtime overhead It is very convenient for a userspace coder to be able to just start a function in a different thread. Now it might be so that a kernel is not there to provide ease of use for userspace coders but it is a factor. I see lots of people only using: pthread_create()/pthread_join() mutex_lock/unlock sem_post/sem_wait no signals My gut feeling is that you could implement this subset in a way that is both fast and right - although it would not be 'pthreads compliant'. Can anybody confirm this feeling? Regards, bert -- http://www.PowerDNS.com Versatile DNS Services Trilab The Technology People 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Validating dynamically allocated kernel memory
try "sys_mprotect" with neccessary bit patterns set i.e, read/write/exec type of protection check. anil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, June 11, 2001 5:12 PM To: [EMAIL PROTECTED] Subject: Validating dynamically allocated kernel memory Hi, Is there some kernel api to validate memory allocated using kmalloc. Suppose, I allocate some memory using kmalloc and at a later point of execution I would like to validate if the memory allocated is not possibly freed by some other thread. Pls suggest a patch/pointers if any. I also noticed a commented 'CONFIG_DEBUG_MALLOC' config option (2.4.3 source), It doesn't seem to be functional. Any pointers towards the history behind it would also be helpful. Thanks in advance, Kiran PS: My previous post went through minus subject due to oversight :-(...Apologising and resending - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE:
you can use "sys_mprotect" call which is kernel space equ. of "mprotect" . The implementation for the same can be found in "mm\mprotect.c". anil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, June 11, 2001 10:29 AM To: [EMAIL PROTECTED] Subject: Hi, Is there some kernel api to validate memory allocated using kmalloc. Suppose, I allocate some memory using kmalloc and at a later point of execution I would like to validate if the memory allocated is not possibly freed by some other thread. Pls suggest a patch/pointers if any. I also noticed a commented 'CONFIG_DEBUG_MALLOC' config option (2.4.3 source), It doesn't seem to be functional. Any pointers towards the history behind it would also be helpful. Thanks in advance, Kiran - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE:
you can use sys_mprotect call which is kernel space equ. of mprotect . The implementation for the same can be found in mm\mprotect.c. anil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, June 11, 2001 10:29 AM To: [EMAIL PROTECTED] Subject: Hi, Is there some kernel api to validate memory allocated using kmalloc. Suppose, I allocate some memory using kmalloc and at a later point of execution I would like to validate if the memory allocated is not possibly freed by some other thread. Pls suggest a patch/pointers if any. I also noticed a commented 'CONFIG_DEBUG_MALLOC' config option (2.4.3 source), It doesn't seem to be functional. Any pointers towards the history behind it would also be helpful. Thanks in advance, Kiran - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Validating dynamically allocated kernel memory
try sys_mprotect with neccessary bit patterns set i.e, read/write/exec type of protection check. anil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, June 11, 2001 5:12 PM To: [EMAIL PROTECTED] Subject: Validating dynamically allocated kernel memory Hi, Is there some kernel api to validate memory allocated using kmalloc. Suppose, I allocate some memory using kmalloc and at a later point of execution I would like to validate if the memory allocated is not possibly freed by some other thread. Pls suggest a patch/pointers if any. I also noticed a commented 'CONFIG_DEBUG_MALLOC' config option (2.4.3 source), It doesn't seem to be functional. Any pointers towards the history behind it would also be helpful. Thanks in advance, Kiran PS: My previous post went through minus subject due to oversight :-(...Apologising and resending - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: semaphores and noatomic flag
Will it not be a very specialized case rather than being general call type? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mihai Moise Sent: Monday, June 04, 2001 11:05 PM To: [EMAIL PROTECTED] Subject: semaphores and noatomic flag I write this to discuss the reasons why the semop system call should have an IPC_NOATOMIC flag. Suppose we have two processes, called client and server, which communicate through a shared memory segment and two semaphores, and need to synchonize their activities so that they don't operate simultaneously except at startup. The server would do, down(smephore 0) to wait for a message from the client. When the client needs the server to execute, it would, up(semaphore 0) /* wake up server */ down(semaphore 1) /* put itself to sleep */ after the server has completed its portion of the task, it would, up(semaphore 1) /* wake up client */ down(semaphore 0) /* put iself to sleep */ The problem is that the two system calls make the whole process twice as slow as it needs to be, and they are both needed because the semop system call is implemented in an atomic manner. If the semop system call had an IPC_NOATOMIC flag, then the each process would only have to do one call, semop(up semaphore 0 & down semaphore 1, IPC_NOATOMIC) which would be interpreted in the kernel as the sequence of two system calls I have written previously. I want to know what other people think about this idea. Mihai - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: semaphores and noatomic flag
Will it not be a very specialized case rather than being general call type? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mihai Moise Sent: Monday, June 04, 2001 11:05 PM To: [EMAIL PROTECTED] Subject: semaphores and noatomic flag I write this to discuss the reasons why the semop system call should have an IPC_NOATOMIC flag. Suppose we have two processes, called client and server, which communicate through a shared memory segment and two semaphores, and need to synchonize their activities so that they don't operate simultaneously except at startup. The server would do, down(smephore 0) to wait for a message from the client. When the client needs the server to execute, it would, up(semaphore 0) /* wake up server */ down(semaphore 1) /* put itself to sleep */ after the server has completed its portion of the task, it would, up(semaphore 1) /* wake up client */ down(semaphore 0) /* put iself to sleep */ The problem is that the two system calls make the whole process twice as slow as it needs to be, and they are both needed because the semop system call is implemented in an atomic manner. If the semop system call had an IPC_NOATOMIC flag, then the each process would only have to do one call, semop(up semaphore 0 down semaphore 1, IPC_NOATOMIC) which would be interpreted in the kernel as the sequence of two system calls I have written previously. I want to know what other people think about this idea. Mihai - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel Address
Under which directory is the Linus's kernel? anil - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel Address
Under which directory is the Linus's kernel? anil - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
File read.
hi, How do i read file within the kernel modules. I hope we can't use the FS open... calls within kernel. thanks - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
File read.
hi, How do i read file within the kernel modules. I hope we can't use the FS open... calls within kernel. thanks - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Linking
How do i link the kernel functions such as test_ans_set functions with my applications. thanks, anil - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
__exit
what does __exit, __p and other such directives means in the linux source code. what is its significance. thanks, anil - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
__exit
what does __exit, __p and other such directives means in the linux source code. what is its significance. thanks, anil - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Linking
How do i link the kernel functions such as test_ans_set functions with my applications. thanks, anil - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RAID Benchmarking
Hi, I want to know , how to Benchmark the performance of RAID.Is there any tool for benchmarking? with regards, Anil __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID Benchmarking
Hi, I want to know , how to Benchmark the performance of RAID.Is there any tool for benchmarking? with regards, Anil __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: passing arguments to module
> >can anybody tell how to pass argument to modules? > > RTFM. man modprobe. man insmod. man modules.conf. > sorry i didn't ask the question properly. I need to know how does kernel modules accept run time arguments from user? Thanks Anil __ Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays! http://calendar.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
passing arguments to module
Hi, can anybody tell how to pass argument to modules? thanks in advance, Anil Prasad Note:Please CC the answer __ Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays! http://calendar.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
passing arguments to module
Hi, can anybody tell how to pass argument to modules? thanks in advance, Anil Prasad Note:Please CC the answer __ Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays! http://calendar.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: passing arguments to module
can anybody tell how to pass argument to modules? RTFM. man modprobe. man insmod. man modules.conf. sorry i didn't ask the question properly. I need to know how does kernel modules accept run time arguments from user? Thanks Anil __ Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays! http://calendar.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
problem with startx in linux kernel 2.4
Hi, I ahave installed Red Hat 7.0 kernel ver 2.4.0-test9 After I boot, when I do #startx I get an error as server crash. My processor is Pentium II I am attaching with this mail the error output I get and also /var/log/XFree86.0.log file Please let me know how to fix this with regards, Anil __ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
problem with startx in linux kernel 2.4
Hi, I ahave installed Red Hat 7.0 kernel ver 2.4.0-test9 After I boot, when I do #startx I get an error as server crash. My processor is Pentium II I am attaching with this mail the error output I get and also /var/log/XFree86.0.log file Please let me know how to fix this with regards, Anil __ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Installing kernel 2.4
Hi , I installed Red Hat 7.0, I am able to find the linux-2.2.16 in /usr/src These are the following steps I did to install kernel 2.4: cd /usr/src #rm -r linux # rm -rf linux-2.2.16 #tar -xvf linux-2.4.0-test9.tar #cd /usr/src #ls linux redhat #mv linux linux-2.4.0-test9 #ln -s linux-2.4.0-test9 linux #ls linux->linux-2.4.0-test9 linux-2.4.0-test9 redhat #cd /usr/src/linux #make xconfig I just save & exit without changing the configuration. #make dep #make clean #make bzImage #make modules #make modules_install I find that System.map is mapped to 2.4.0, ie.. new System-2.4.0-test9.map is created #cd /boot #ls #vmlinuz->vmlinuz-2.4.0-test9 #cd /usr/src/linux/arch/i386/boot #cp bzImage /boot/vmlinuz #vi /etc/lilo.conf changed image from image = /boot/vmlinuz-2.2.16-22 to image = /boot/vmlinuz-2.4.0-test9 #lilo linux dos when I boot linux The system hangs after messages: loading linux.. uncompressing linux, booting linux kernel OK. The System hangs here. Please let me know where I am wrong with regards, Anil __ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
physical end of disk
Hi, I want to know how does the ide driver calculate the end of the disk. Is there any function in the ide driver that finds the end of the disk? I dont know the particular ide mailing list.So I have posted to linux-kernel mailing list. with regards, Anil __ Do You Yahoo!? >From homework help to love advice, Yahoo! Experts has your answer. http://experts.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
physical end of disk
Hi, I want to know how does the ide driver calculate the end of the disk. Is there any function in the ide driver that finds the end of the disk? I dont know the particular ide mailing list.So I have posted to linux-kernel mailing list. with regards, Anil __ Do You Yahoo!? From homework help to love advice, Yahoo! Experts has your answer. http://experts.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
mkraid
Hi, I have a problem with mkraid I am working on a Red hat Linux ver 7.0 kernel version: 2.2.16 No raid patch no raid tools when I run #mkraid /dev/md0 when I check /proc/mdstat,I find md0 active with raid information. But when again I run #mkraid /dev/md0 I get an message: handling MD device /dev/md0 analyzing super-block disk 0:/dev/hde1,2109681kB,raid superblock at 2109568KB /dev/hde1 appears to be already part of a raid array-- use -f to force desctruction of the old superblock mkraid: aborted,see the syslog and /proc/mdstat for potential clues. I tried -f option, but no use. I did a reboot and once again mkraid, but still I get the above messages. Please let me know where am I wrong , How can I do mkraid succesfully again? Expecting reply from you with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
mkraid
Hi, I have a problem with mkraid I am working on a Red hat Linux ver 7.0 kernel version: 2.2.16 No raid patch no raid tools when I run #mkraid /dev/md0 when I check /proc/mdstat,I find md0 active with raid information. But when again I run #mkraid /dev/md0 I get an message: handling MD device /dev/md0 analyzing super-block disk 0:/dev/hde1,2109681kB,raid superblock at 2109568KB /dev/hde1 appears to be already part of a raid array-- use -f to force desctruction of the old superblock mkraid: aborted,see the syslog and /proc/mdstat for potential clues. I tried -f option, but no use. I did a reboot and once again mkraid, but still I get the above messages. Please let me know where am I wrong , How can I do mkraid succesfully again? Expecting reply from you with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID superblock
Hi, After I create a RAID setup on the drives,The superblock will be generated at the end of the drives. If I move these drives to other linux system, will this system recognise the RAID setup without reconfiguring the Linux ? with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID from BIOS
Hi, 1. Does Linux support this: Setting RAID options & configurations from BIOS itself. 2.I am not able to post messages to linux-raid group. with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID superblock
Hi, After I create a RAID setup on the drives,The superblock will be generated at the end of the drives. If I move these drives to other linux system, will this system recognise the RAID setup without reconfiguring the Linux ? with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
regarding fsck
Hi, I am getting a kernel panic when I boot linux. There is some bad block. To get rid of this, I want to run fsck.I boot linux with a boot diskette and then with rescue.img I get to the command prompt and then run fsck. #e2fsck /dev/hdb5 //hdb5 is my linux native when I run fsck I get following message: Group decriptors look bad... trying backup block... e2fsck:Bad magic number in superblock while trying to open /dev/hdb5 The superblock could not be read or does not describe a correct ext2 filesystem.If the device is valid and it really contains ext2 filesystem(and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock: e2fsck -b 8193 I run #e2fsck -b 8193 /dev/hdb5 I get the same message as I got above. How can I get my linux back? with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
regarding fsck
Hi, I am getting a kernel panic when I boot linux. There is some bad block. To get rid of this, I want to run fsck.I boot linux with a boot diskette and then with rescue.img I get to the command prompt and then run fsck. #e2fsck /dev/hdb5 //hdb5 is my linux native when I run fsck I get following message: Group decriptors look bad... trying backup block... e2fsck:Bad magic number in superblock while trying to open /dev/hdb5 The superblock could not be read or does not describe a correct ext2 filesystem.If the device is valid and it really contains ext2 filesystem(and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock: e2fsck -b 8193 device I run #e2fsck -b 8193 /dev/hdb5 I get the same message as I got above. How can I get my linux back? with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID setup
Hi, Does Linux give options to choose RAID levels from BIOS? with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID setup
Hi, Does Linux give options to choose RAID levels from BIOS? with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Bootable RAID
Hi, I want to make a Bootable RAID. can I make a partition on the disk which I want to make as bootable or should I be use whole disk? What I mean is like this: In the lilo.conf file I do like this: disk = /dev/md0 boot = /dev/hdc Is this all what I can do? or can I make a partiton in /dev/hdc & specify that as disk? In that case lilo.conf file will be like this: disk = /dev/md0 boot = /dev/hdc1 can I use partition of the disk as boot? Expecting reply from you with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Bootable RAID
Hi, I want to make a Bootable RAID. can I make a partition on the disk which I want to make as bootable or should I be use whole disk? What I mean is like this: In the lilo.conf file I do like this: disk = /dev/md0 boot = /dev/hdc Is this all what I can do? or can I make a partiton in /dev/hdc specify that as disk? In that case lilo.conf file will be like this: disk = /dev/md0 boot = /dev/hdc1 can I use partition of the disk as boot? Expecting reply from you with regards, Anil __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
remap_page_range
Hi, suppose i allocate an buffer by calling kmalloc. i want to map this buffer to user address space. will remap_page_range will automatically map this buffer to calling process's address space. thanks. __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
remap_page_range
Hi, suppose i allocate an buffer by calling kmalloc. i want to map this buffer to user address space. will remap_page_range will automatically map this buffer to calling process's address space. thanks. __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID setup
Hi, I want to setup RAID. I am working on kernel version 2.2.12. I am using RAID patches available. I create a RAID configuring file called /etc/raidtab #mkraid /dev/md0/*md0 is the device I am selecting*/ After this when I check /proc/mdstat , I find that /dev/md0 is not running. The /proc/mdstat gives message: device md0:inactive. Where am I wrong? should I be doing something else before & after mkraid? I am not able to post messages to linu-raid group. May I know what is the correct mail id for this group? with regards, Anil __ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID setup
Hi, I want to setup RAID. I am working on kernel version 2.2.12. I am using RAID patches available. I create a RAID configuring file called /etc/raidtab #mkraid /dev/md0/*md0 is the device I am selecting*/ After this when I check /proc/mdstat , I find that /dev/md0 is not running. The /proc/mdstat gives message: device md0:inactive. Where am I wrong? should I be doing something else before after mkraid? I am not able to post messages to linu-raid group. May I know what is the correct mail id for this group? with regards, Anil __ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID setup
Hi, I want to setup RAID. I am working on kernel version 2.2.12. I am using RAID patches available. I create a RAID configuring file called /etc/raidtab #mkraid /dev/md0/*md0 is the device I am selecting*/ After this when I check /proc/mdstat , I find that /dev/md0 is not running. The /proc/mdstat gives message: device md0:inactive. what exactly should /proc/mdstat show, when I run mkraid command? Where am I wrong? should I be doing something else before & after mkraid? with regards, Anil __ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RAID setup
Hi, I want to setup RAID. I am working on kernel version 2.2.12. I am using RAID patches available. I create a RAID configuring file called /etc/raidtab #mkraid /dev/md0/*md0 is the device I am selecting*/ After this when I check /proc/mdstat , I find that /dev/md0 is not running. The /proc/mdstat gives message: device md0:inactive. what exactly should /proc/mdstat show, when I run mkraid command? Where am I wrong? should I be doing something else before after mkraid? with regards, Anil __ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
disk partition & RAID
Hi, I want to setup the RAID. For this I am partitioning the disks .The following is the procedure: fdisk /dev/hde fdisk -n /dev/hde /*to add new partition*/ I specify the first & last cylinder fdisk -w /dev/hde /*save & quit*/ when I do so , I get following : The partition table has been altered! calling ioctl() to re-read partition table. hde:unknown partition table What does this mean? where am I wrong? I am creating a /etc/raidtab file for raid configuration . Then # mkraid /dev/md0 I get error : device too small(0KB). Surprisingly, while bootup itself the Partition check shows : hde : unknown partition table what does this mean & how it affects the RAID setup? hde is the externel disk I am using for RAID setup. I am not able to post any messages to :linux-raid group. with regards, Anil __ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
disk partition RAID
Hi, I want to setup the RAID. For this I am partitioning the disks .The following is the procedure: fdisk /dev/hde fdisk -n /dev/hde /*to add new partition*/ I specify the first last cylinder fdisk -w /dev/hde /*save quit*/ when I do so , I get following : The partition table has been altered! calling ioctl() to re-read partition table. hde:unknown partition table What does this mean? where am I wrong? I am creating a /etc/raidtab file for raid configuration . Then # mkraid /dev/md0 I get error : device too small(0KB). Surprisingly, while bootup itself the Partition check shows : hde : unknown partition table what does this mean how it affects the RAID setup? hde is the externel disk I am using for RAID setup. I am not able to post any messages to :linux-raid group. with regards, Anil __ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
