From: Imre Deak <imre.deak@solidboot.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: 'Linux OMAP ML' <linux-omap-open-source@linux.omap.com>
Subject: Re: TSC2101/2102
Date: Thu, 15 Mar 2007 12:23:25 +0200 [thread overview]
Message-ID: <20070315102325.GA4555@bitbox.mine.nu> (raw)
In-Reply-To: <002801c7669f$d0fe2be0$c7a3580a@swcenter.sec.samsung.co.kr>
Hi,
On Thu, Mar 15, 2007 at 10:18:14AM +0900, Kyungmin Park wrote:
> [...]
>
> In the previous time, I implemented the tsc2101 on OMAP2 based on tsc2301.
> [1]
I needed only the basic register read / write interface to access the
TSC2101 GPIO lines. The TS part you wrote is still needed, it's
init function being called from the tsc2101.c probe, as it's done in
tsc2301-core.c.
> The current code only supports 16-bit tsc2101 for OMAP1.
> We have to consider OMAP2 tsc2101 for H4 and apollon.
Is the 32-bit interface some alternate interface configuration for the chip?
In the TSC2101 spec I found at least only a description of the 16-bit
protocoll. Could you point to a documentation for this?
--Imre
>
> Here's simple changes.
>
> +struct tsc2101_platform_data {
> + int (*init)(struct spi_device *spi);
> + void (*cleanup)(struct spi_device *spi);
> + void (*enable_mclk)(struct spi_device *spi);
> + void (*disable_mclk)(struct spi_device *spi);
>
> + int bits_per_word;
>
> +};
>
> How about to add 'bits_per_word' to platform. So if the bits_per_word is
> empty. it assumes it will use 16-bit, otherwise we use it provided from
> platform.
>
> +struct tsc2101_device {
> + struct mutex mutex;
> + int mclk_enabled;
> + struct clock *mclk_ck;
> + struct spi_message message;
> + struct spi_transfer transfer[2];
> + u16 command;
> + void (*enable_mclk)(struct spi_device *spi);
> + void (*disable_mclk)(struct spi_device *spi);
>
> + int 32bit_shift; /* 16 if 32-bit bus, otherwise 0 */
>
> +};
>
> Please change the command from u16 to u32. Umm, I'm not sure we have to
> change the parameter from u16 *data to u32 *data.
>
> I will check it.
>
> Thank you,
> Kyungmin Park
>
> 1. http://linux.omap.com/pipermail/linux-omap-open-source/2007-
> January/008933.html
>
next prev parent reply other threads:[~2007-03-15 10:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 14:06 TSC2101/2102 Imre Deak
2007-03-09 14:23 ` TSC2101/2102 andrzej zaborowski
2007-03-14 13:21 ` TSC2101/2102 Nishanth Menon
2007-03-14 17:09 ` TSC2101/2102 Imre Deak
2007-03-14 20:35 ` TSC2101/2102 Dirk Behme
2007-03-15 1:18 ` TSC2101/2102 Kyungmin Park
2007-03-15 10:23 ` Imre Deak [this message]
2007-03-15 14:23 ` Regarding use of DirectFB Raja Mallik
2007-03-15 17:09 ` Cliff Brake
2007-03-16 0:28 ` TSC2101/2102 Kyungmin Park
2007-03-16 7:41 ` TSC2101/2102 Imre Deak
2007-03-16 8:05 ` TSC2101/2102 Kyungmin Park
2007-03-16 9:49 ` TSC2101/2102 Imre Deak
2007-03-19 2:02 ` TSC2101/2102 Kyungmin Park
2007-03-19 7:37 ` TSC2101/2102 Jarkko Nikula
2007-03-19 8:04 ` TSC2101/2102 Kyungmin Park
2007-03-19 8:37 ` TSC2101/2102 Jarkko Nikula
2007-03-19 19:22 ` TSC2101/2102 tony
2007-03-20 1:46 ` TSC2101/2102 Kyungmin Park
2007-03-20 13:27 ` TSC2101/2102 tony
2007-03-20 13:54 ` TSC2101/2102 Jarkko Nikula
2007-03-20 15:38 ` TSC2101/2102 Tony Lindgren
2007-03-21 19:24 ` TSC2101/2102 Eduardo Valentin
2007-03-22 6:48 ` TSC2101/2102 Jarkko Nikula
2007-03-30 18:49 ` TSC2101/2102 Tony Lindgren
2007-03-31 12:52 ` TSC2101/2102 Eduardo Valentin
2007-03-31 17:01 ` TSC2101/2102 Imre Deak
2007-04-02 13:43 ` TSC2101/2102 Eduardo Valentin
2007-04-02 20:23 ` TSC2101/2102 Imre Deak
2007-04-02 20:41 ` TSC2101/2102 Eduardo Valentin
2007-04-03 11:22 ` TSC2101/2102 Eduardo Valentin
2007-04-03 14:36 ` TSC2101/2102 Imre Deak
2007-04-03 15:10 ` TSC2101/2102 Eduardo Valentin
2007-04-03 19:23 ` TSC2101/2102 Tony Lindgren
2007-03-29 20:26 ` TSC2101/2102 Tony Lindgren
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=20070315102325.GA4555@bitbox.mine.nu \
--to=imre.deak@solidboot.com \
--cc=kmpark@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox