From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Kukjin Kim' <kgene.kim@samsung.com>,
'Grant Likely' <grant.likely@secretlab.ca>,
'Jassi Brar' <jassisinghbrar@gmail.com>
Cc: 'padma venkat' <padma.kvr@gmail.com>,
'Tony Nadackal' <tonykn@gmail.com>,
'Padmavathi Venna' <padma.v@samsung.com>,
sbkim73@samsung.com, spi-devel-general@lists.sourceforge.net,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, tony.kn@samsung.com,
naushad@samsung.com
Subject: RE: [PATCH 2/2] SPI: SAMSUNG: Bug fix for SPI with different FIFO level
Date: Mon, 04 Jul 2011 19:08:55 +0900 [thread overview]
Message-ID: <005601cc3a32$64bd5fd0$2e381f70$%kim@samsung.com> (raw)
In-Reply-To: <005501cc3a30$6c916190$45b424b0$%kim@samsung.com>
Kukjin Kim wrote:
>
> Grant Likely wrote:
> >
> > On Mon, Jul 4, 2011 at 12:55 AM, Grant Likely
<grant.likely@secretlab.ca>
> wrote:
> > > On Fri, Jul 01, 2011 at 11:43:08AM +0530, Jassi Brar wrote:
> > >> On Fri, Jul 1, 2011 at 11:29 AM, padma venkat <padma.kvr@gmail.com>
> wrote:
> > >> > Hi Jassi,
> > >> >
> > >> > On Fri, Jul 1, 2011 at 11:22 AM, Jassi Brar
> <jassisinghbrar@gmail.com> wrote:
> > >> >> On Fri, Jul 1, 2011 at 11:16 AM, padma venkat
<padma.kvr@gmail.com>
> > wrote:
> > >> >>> Hi Tony,
> > >> >>>
> > >> >>> On Thu, Jun 30, 2011 at 4:30 PM, Tony Nadackal <tonykn@gmail.com>
> > wrote:
> > >> >>>> Hi Padma,
> > >> >>>> With regards to your patch, even though one can check the tx
done
> > status
> > >> >>>> using the TX_DONE bit, the present macro itself would work
> perfectly
> > fine if
> > >> >>>> the 'fifo_lvl_mask' is set properly.
> > >> >>>> For example in 6450 channel 1, the fifo_lvl_mask should be 0x1ff
> (for
> > 9bits,
> > >> >>>> 15:23), while even in your patch, it is wrongly set as 0x7f(only
> 7bits).
> > >> >>>>
> > >> >>>> Thus, if this fifo_lvl_mask was defined correctly, the existing
> macro
> > would
> > >> >>>> itself have worked.
> > >> >>> Thanks for your comment.
> > >> >>> I considered changing to the fifo_lvl_mask to 1ff as you
mentioned.
> > >> >>> But I think that the fifo_lvl_mask reflects the actual FIFO
> capacity
> > >> >>> in the SPI driver.
> > >> >>> For the failing channels the FIFO trigger level is 64 bytes and
so
> i
> > >> >>> retained that value.
> > >> >>> In the driver it polls till the FIFO capacity level otherwise it
> goes
> > >> >>> for DMA.So if we keep
> > >> >>> the FIFO level as 1ff when the actual capacity is 7f then it
fails.
> > >> >>>
> > >> >>> Jassi what do you think about this?
> > >> >>>
> > >> >>
> > >> >> 'fifo_lvl_mask' is h/w specific and can't be set for convenience.
> > >> >>
> > >> >> I don't have access to post-s3c64xx datasheets.
> > >> >> Please check and reply if TX_DONE bit is at same offset for all
> > >> >> channels of an SoC, because
> > >> >> I suspect it's otherwise.
> > >> >>
> > >> > Yes. The TX_DONE bit is at the same offset for all the channels of
an
> SoC.
> > >> > in S5P64X0,S5PV210 and S5PV310 it is at offset 25.
> > >> >
> > >>
> > >> Then, Patches-1,2
> > >>
> > >> Acked-by: Jassi Brar <jassisinghbrar@gmail.com>
> > >
> > > Are these bug fixes that should be in v3.0, or do I queue them up for
> v3.1?
> >
> > Regardless, this one touches a lot of arch/arm files, so I'd rather
> > see both patches go through the samsung tree:
> >
> > Acked-by: Grant Likely <grant.likely@secretlab.ca>
> >
>
> Thanks Grant, Jassi and all,
>
> I will apply these 1 and 2 in my -fix tree for 3.0 with your acks.
>
Oops, this needs previous 'cleanup spi platform specific code' so can't
apply -fix tree now.
Padmavathi, I will apply these 1 and 2 on -next for 3.1 after your updated
'cleanup spi' patches...
If any problems, please let me know.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2011-07-04 10:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 12:38 [PATCH 1/2] ARM: SAMSUNG: Added tx_st_done variable in the platform data of SPI Padmavathi Venna
2011-06-30 12:38 ` [PATCH 2/2] SPI: SAMSUNG: Bug fix for SPI with different FIFO level Padmavathi Venna
2011-06-30 7:08 ` Jassi Brar
2011-06-30 9:05 ` padma venkat
2011-06-30 9:52 ` Jassi Brar
[not found] ` <BANLkTi=9c5asfr=Jg6xwjQZW_a369UO64Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-30 11:00 ` Tony Nadackal
2011-07-01 5:46 ` padma venkat
2011-07-01 5:52 ` Jassi Brar
2011-07-01 5:59 ` padma venkat
2011-07-01 6:13 ` Jassi Brar
2011-07-04 6:55 ` Grant Likely
2011-07-04 6:58 ` Grant Likely
2011-07-04 9:54 ` Kukjin Kim
2011-07-04 10:04 ` padma venkat
2011-07-04 10:08 ` Kukjin Kim [this message]
2011-07-04 15:06 ` Grant Likely
2011-07-05 5:51 ` Kukjin Kim
2011-07-06 6:22 ` Kukjin Kim
2011-07-06 6:30 ` Grant Likely
2011-07-06 7:17 ` Kukjin Kim
2011-07-06 17:30 ` 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='005601cc3a32$64bd5fd0$2e381f70$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=grant.likely@secretlab.ca \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=naushad@samsung.com \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=sbkim73@samsung.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tony.kn@samsung.com \
--cc=tonykn@gmail.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;
as well as URLs for NNTP newsgroup(s).