From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Raja, Govindraj" <govindraj.raja@ti.com>
Cc: linux-omap@vger.kernel.org,
spi-devel-general <spi-devel-general@lists.sourceforge.net>,
linux-arm-kernel@lists.infradead.org, Charulatha V <charu@ti.com>,
Benoit Cousson <b-cousson@ti.com>,
"Datta, Shubhrajyoti" <shubhrajyoti@ti.com>,
Partha Basak <p-basak2@ti.com>
Subject: Re: [PATCH 0/7 v2] OMAP: McSPI: Hwmod adaptation + runtime conversion
Date: Thu, 16 Dec 2010 10:17:18 -0800 [thread overview]
Message-ID: <874oadfuq9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTikgzMjU9wfzzMjEXzFCUvRz6hKtv=N8dKXf10YM@mail.gmail.com> (Govindraj Raja's message of "Thu, 16 Dec 2010 14:57:46 +0530")
Hi Govindraj,
"Raja, Govindraj" <govindraj.raja@ti.com> writes:
> On Wed, Dec 15, 2010 at 9:42 PM, Kevin Hilman <khilman@deeprootsystems.com>
> wrote:
>
> "Govindraj.R" <govindraj.raja@ti.com> writes:
>
> > Changes invloves:
> > ----------------
> > 1) Addition of hwmod data for omap2/3/4.
> > 1) McSPI driver hwmod adaptation with cleanup of base address
> > macros and using omap-device API's.
> > 2) Runtime Conversion of McSPI driver
> >
> > Changes from v1:
> > ---------------
> > 1) Fixing patch 5/5 comments for hwmod+runtime
> > Split the patch 5/5 to hwmod adaptation
> > and then runtime conversion
> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg33387.html
> >
> > Testing Updates:
> > ----------------
> > Was tested using data transfer test module available at:
> > http://dev.omapzoom.org/?p=richo/device_driver_test.git;a=blob;f=mcspi/
> test_code/
> > utils/mcspi_modules/omap_mcspi_datatest.c;
> > h=e42ec10c5c844abdde6a7175a268b379fbbdb655;
> > hb=5d9a755d50e58de861c5e8991f2f607bc49b5dc3
>
> Can you summarize what this test does?
>
> On what platforms was this tested?
>
> How was it tested for OMAP1 and OMAP2?
>
>
>
> Using the above mentioned test module we had done some
> data transfer tests.
> Platforms used used where :
> 1) OMAP2430 SDP.
> 2) OMAP3 (ZOOM boards zoom2/3).
> 3) OMAP4430 SDP [ Here even basic Ethernet functionality was checked which is
> over SPI interface]
Can you describe a little more about the testing please? What exactly
does the data transfer test do? Is it a loopback test? Does it use
on-board SPI peripherals? If so, which ones, etc.
> We boot tested on 2420/n800.
>
> Coming to omap1,
>
> This driver[omap2_mcspi.c] is applicable only from omap2_plus
> for omap1 omap_uwire.c is the spi driver file.
OK, thanks for clarification.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Raja\, Govindraj" <govindraj.raja@ti.com>
Cc: linux-omap@vger.kernel.org,
spi-devel-general <spi-devel-general@lists.sourceforge.net>,
linux-arm-kernel@lists.infradead.org, Charulatha V <charu@ti.com>,
Benoit Cousson <b-cousson@ti.com>, "Datta\,
Shubhrajyoti" <shubhrajyoti@ti.com>,
Partha Basak <p-basak2@ti.com>
Subject: Re: [PATCH 0/7 v2] OMAP: McSPI: Hwmod adaptation + runtime conversion
Date: Thu, 16 Dec 2010 10:17:18 -0800 [thread overview]
Message-ID: <874oadfuq9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTikgzMjU9wfzzMjEXzFCUvRz6hKtv=N8dKXf10YM@mail.gmail.com> (Govindraj Raja's message of "Thu, 16 Dec 2010 14:57:46 +0530")
Hi Govindraj,
"Raja, Govindraj" <govindraj.raja@ti.com> writes:
> On Wed, Dec 15, 2010 at 9:42 PM, Kevin Hilman <khilman@deeprootsystems.com>
> wrote:
>
> "Govindraj.R" <govindraj.raja@ti.com> writes:
>
> > Changes invloves:
> > ----------------
> > 1) Addition of hwmod data for omap2/3/4.
> > 1) McSPI driver hwmod adaptation with cleanup of base address
> > macros and using omap-device API's.
> > 2) Runtime Conversion of McSPI driver
> >
> > Changes from v1:
> > ---------------
> > 1) Fixing patch 5/5 comments for hwmod+runtime
> > Split the patch 5/5 to hwmod adaptation
> > and then runtime conversion
> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg33387.html
> >
> > Testing Updates:
> > ----------------
> > Was tested using data transfer test module available at:
> > http://dev.omapzoom.org/?p=richo/device_driver_test.git;a=blob;f=mcspi/
> test_code/
> > utils/mcspi_modules/omap_mcspi_datatest.c;
> > h=e42ec10c5c844abdde6a7175a268b379fbbdb655;
> > hb=5d9a755d50e58de861c5e8991f2f607bc49b5dc3
>
> Can you summarize what this test does?
>
> On what platforms was this tested?
>
> How was it tested for OMAP1 and OMAP2?
>
>
>
> Using the above mentioned test module we had done some
> data transfer tests.
> Platforms used used where :
> 1) OMAP2430 SDP.
> 2) OMAP3 (ZOOM boards zoom2/3).
> 3) OMAP4430 SDP [ Here even basic Ethernet functionality was checked which is
> over SPI interface]
Can you describe a little more about the testing please? What exactly
does the data transfer test do? Is it a loopback test? Does it use
on-board SPI peripherals? If so, which ones, etc.
> We boot tested on 2420/n800.
>
> Coming to omap1,
>
> This driver[omap2_mcspi.c] is applicable only from omap2_plus
> for omap1 omap_uwire.c is the spi driver file.
OK, thanks for clarification.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7 v2] OMAP: McSPI: Hwmod adaptation + runtime conversion
Date: Thu, 16 Dec 2010 10:17:18 -0800 [thread overview]
Message-ID: <874oadfuq9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTikgzMjU9wfzzMjEXzFCUvRz6hKtv=N8dKXf10YM@mail.gmail.com> (Govindraj Raja's message of "Thu, 16 Dec 2010 14:57:46 +0530")
Hi Govindraj,
"Raja, Govindraj" <govindraj.raja@ti.com> writes:
> On Wed, Dec 15, 2010 at 9:42 PM, Kevin Hilman <khilman@deeprootsystems.com>
> wrote:
>
> "Govindraj.R" <govindraj.raja@ti.com> writes:
>
> > Changes invloves:
> > ----------------
> > 1) Addition of hwmod data for omap2/3/4.
> > 1) McSPI driver hwmod adaptation with cleanup of base address
> > ? ?macros and using omap-device API's.
> > 2) Runtime Conversion of McSPI driver
> >
> > Changes from v1:
> > ---------------
> > 1) Fixing patch 5/5 comments for hwmod+runtime
> > ? ?Split the patch 5/5 to hwmod adaptation
> > ? ?and then runtime conversion
> > ? ?http://www.mail-archive.com/linux-omap at vger.kernel.org/msg33387.html
> >
> > Testing Updates:
> > ----------------
> > Was tested using data transfer test module available at:
> > http://dev.omapzoom.org/?p=richo/device_driver_test.git;a=blob;f=mcspi/
> test_code/
> > utils/mcspi_modules/omap_mcspi_datatest.c;
> > h=e42ec10c5c844abdde6a7175a268b379fbbdb655;
> > hb=5d9a755d50e58de861c5e8991f2f607bc49b5dc3
>
> Can you summarize what this test does?
>
> On what platforms was this tested?
>
> How was it tested for OMAP1 and OMAP2?
>
>
>
> Using the above mentioned test module we had done some
> data transfer tests.
> Platforms used used where :
> 1) OMAP2430 SDP.
> 2) OMAP3 (ZOOM boards zoom2/3).
> 3) OMAP4430 SDP [ Here even basic?Ethernet?functionality?was checked which is
> over SPI interface]
Can you describe a little more about the testing please? What exactly
does the data transfer test do? Is it a loopback test? Does it use
on-board SPI peripherals? If so, which ones, etc.
> We boot tested on 2420/n800.
>
> Coming to omap1,
>
> This driver[omap2_mcspi.c] is applicable only from omap2_plus
> for omap1?omap_uwire.c is the spi driver file.
OK, thanks for clarification.
Kevin
next prev parent reply other threads:[~2010-12-16 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 14:01 [PATCH 0/7 v2] OMAP: McSPI: Hwmod adaptation + runtime conversion Govindraj.R
2010-12-01 14:01 ` Govindraj.R
2010-12-08 9:19 ` Govindraj
2010-12-08 9:19 ` Govindraj
2010-12-15 16:12 ` Kevin Hilman
2010-12-15 16:12 ` Kevin Hilman
[not found] ` <87d3p3kobt.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-12-16 9:27 ` Raja, Govindraj
2010-12-16 9:27 ` Raja, Govindraj
2010-12-16 18:17 ` Kevin Hilman [this message]
2010-12-16 18:17 ` Kevin Hilman
2010-12-16 18:17 ` Kevin Hilman
2010-12-17 12:52 ` Govindraj
2010-12-17 12:52 ` Govindraj
2010-12-16 11:33 ` Govindraj
2010-12-16 11:33 ` Govindraj
2010-12-29 7:27 ` Govindraj
2010-12-29 7:27 ` Govindraj
2010-12-29 7:32 ` Grant Likely
2010-12-29 7:32 ` Grant Likely
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=874oadfuq9.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=charu@ti.com \
--cc=govindraj.raja@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=shubhrajyoti@ti.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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.