From: Dirk Behme <dirk.behme@googlemail.com>
To: abhishek@nextbitcpu.com
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: trouble configuring the touchscreen driver for OMAP OSK 5912
Date: Fri, 16 Feb 2007 15:00:46 +0100 [thread overview]
Message-ID: <45D5B90E.2030906@googlemail.com> (raw)
In-Reply-To: <B62D67BD8EC3324C8A3DACEEA1A0D6C6A30A12@dlee12.ent.ti.com>
Kipisz, Steven wrote:
> I don't have my code handy right now, but if I remember correctly, in
> menuconfig you need to enable SPI. The touchscreen on the display
> module is an ADS7846 so you need to enable that touchscreen. If I
> remember correctly, you need to enable SPI support first before the
> ADS7846 shows up as an option under Touchscreens.
Mistral QVLM display module at OSK works quite well for me.
My config:
#
# SPI support
#
CONFIG_SPI=y
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=y
CONFIG_SPI_OMAP_UWIRE=y
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
...
CONFIG_KEYBOARD_OMAP=y
...
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=y
Hth,
Dirk
> -----Original Message-----
> From: linux-omap-open-source-bounces+s-kipisz2=ti.com@linux.omap.com
> [mailto:linux-omap-open-source-bounces+s-kipisz2=ti.com@linux.omap.com]
> On Behalf Of abhishek@nextbitcpu.com
> Sent: Friday, February 16, 2007 12:20 AM
> To: linux-omap-open-source@linux.omap.com
> Subject: trouble configuring the touchscreen driver for OMAP OSK 5912
>
> Hello,
>
> I have been trying to build the linux kernel for the omap osk 5912 with
> touchscreen option but it is not working. The OSK is connected to a
> Mistral QVLM display module.
> I am using linux kernel version 2.6.18 along with the appropriate omap
> patch patch-2.6.18-omap1. After applying the patch i use the following
> procedure.
>
> make clean
> make omap_osk_5912_defconfig
> make menuconfig
>
> I use the following link for reference
> http://oskfordummies.hp.infoseek.co.jp/howto/touch.html
>
> According to this refence document i have to enable the options
>
> CONFIG_INPUT_EVDEV
> CONFIG_INPUT_TOUCHSCREEN
> CONFIG_TOUCHSCREEN_OMAP
>
> i am not getting any option for CONFIG_TOUCHSCREEN_OMAP. Also while
> trying
> to enable the LCD i dont get an option for CONFIG_FB_OMAP_INTERNAL_LCDC.
>
> here is the Input Device Drivers section of .config file generated after
> the 'make menuconfig' command.
>
> #
> # Input Device Drivers
> #
> CONFIG_INPUT_KEYBOARD=y
> # CONFIG_KEYBOARD_ATKBD is not set
> # CONFIG_KEYBOARD_SUNKBD is not set
> # CONFIG_KEYBOARD_LKKBD is not set
> # CONFIG_KEYBOARD_XTKBD is not set
> # CONFIG_KEYBOARD_NEWTON is not set
> CONFIG_KEYBOARD_OMAP=y
> # CONFIG_INPUT_MOUSE is not set
> # CONFIG_INPUT_JOYSTICK is not set
> CONFIG_INPUT_TOUCHSCREEN=y
> # CONFIG_TOUCHSCREEN_GUNZE is not set
> # CONFIG_TOUCHSCREEN_ELO is not set
> # CONFIG_TOUCHSCREEN_MTOUCH is not set
> # CONFIG_TOUCHSCREEN_MK712 is not set
> # CONFIG_INPUT_MISC is not set
>
> #
>
>
> The graphics support section of .config
>
> #
> # Graphics support
> #
> CONFIG_FIRMWARE_EDID=y
> CONFIG_FB=y
> # CONFIG_FB_CFB_FILLRECT is not set
> # CONFIG_FB_CFB_COPYAREA is not set
> # CONFIG_FB_CFB_IMAGEBLIT is not set
> # CONFIG_FB_MACMODES is not set
> # CONFIG_FB_BACKLIGHT is not set
> CONFIG_FB_MODE_HELPERS=y
> # CONFIG_FB_TILEBLITTING is not set
> # CONFIG_FB_S1D13XXX is not set
> # CONFIG_FB_VIRTUAL is not set
> CONFIG_FB_OMAP=y
> # CONFIG_FB_OMAP_LCDC_EXTERNAL is not set
> # CONFIG_FB_OMAP_LCD_MIPID is not set
> # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
> CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2
> # CONFIG_FB_OMAP_DMA_TUNE is not set
>
> #
>
> Still i continued with the following procedure and loaded the kernel
> using
> using tftp.
>
> $ make
> $ arm-linux-objcopy -O binary -R .note -R .comment -S
> arch/arm/boot/compressed/vmlinux linux.bin
> $ gzip -9 linux.bin
> $ /usr/src/u-boot-1.1.6/tools/mkimage -A arm -O linux -T kernel -C gzip
> -a
> 0x10c08000 -e 0x10c08000 -n 'Linux Kernel Image' -d linux.bin.gz
> uImage.cc
> $ cp uImage.cc /tftpboot/uImage.cc
>
> The kernel boots correctly but when i run the command
>
> cat /proc/bus/input/devices
>
> nothing is displayed.
>
> Is there anything i missed out when compiling the kernel? Plese help.
>
> Abhishek Desai
>
>
>
>
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
prev parent reply other threads:[~2007-02-16 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 6:19 trouble configuring the touchscreen driver for OMAP OSK 5912 abhishek
2007-02-16 11:52 ` Kipisz, Steven
2007-02-16 14:00 ` Dirk Behme [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45D5B90E.2030906@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=abhishek@nextbitcpu.com \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.