From: Tomasz Figa <tomasz.figa@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rajeshwari Birje <rajeshwari.birje@gmail.com>,
Tomasz Figa <t.figa@samsung.com>,
Rajeshwari S Shinde <rajeshwari.s@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
linux-spi@vger.kernel.org, Simon Glass <sjg@chromium.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Doug Anderson <dianders@google.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Lukasz Czerwinski <l.czerwinski@samsung.com>
Subject: Re: [PATCH V4] spi: s3c64xx: Enable Word transfer
Date: Sun, 10 Nov 2013 18:26:34 +0100 [thread overview]
Message-ID: <3104102.55j2C8XQ5u@flatron> (raw)
In-Reply-To: <20131108110517.GK2493@sirena.org.uk>
On Friday 08 of November 2013 11:05:17 Mark Brown wrote:
> On Thu, Nov 07, 2013 at 10:39:37AM +0100, Tomasz Figa wrote:
> > On Thursday 07 of November 2013 14:52:36 Rajeshwari Birje wrote:
>
> > > The reordering of the words is taken care by the Swap configuration
> > > (swap_cfg) register, which I have set for both 16 and 32 bits_per_word
> > > case. I have tested this patch and works fine for me and also has
> > > improved the timing performance.
>
> > This driver seems to have already worked fine with 32 bits per word,
> > using the s5c73m3 camera sensor, which uses SPI for firmware upload.
>
> This is all sounding very confused. Either this patch is a bug fix or
> it's breaking the driver but I can't tell without more information about
> what it's supposed to do. Can someone explain in concrete terms what
> the intended effect of the patch is on wire behaviour?
>
> It is possible that the s5c73m3 driver is buggy here if it's only been
> tested with the s3c64xx driver (which seems likely) since the author
> could have worked around the driver behaviour.
I'm confused here as well.
Looking at the W25Q32DW datasheet[1], it does not really support 32 bit
words and using such with it seems more like an abuse of this feature.
As for the s5c73m3 sensor, we should ask Andrzej or Sylwester to look
at the datasheet and see how SPI transfer are supposed to work there.
[1] http://www.winbond.com.tw/NR/rdonlyres/D35D5D04-4CE9-46A1-8950-AEA573045507/0/W25Q32DW.pdf
Best regards,
Tomasz
next prev parent reply other threads:[~2013-11-10 17:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 5:32 [PATCH V4] spi: s3c64xx: Enable Word transfer Rajeshwari S Shinde
[not found] ` <1382074356-28430-1-git-send-email-rajeshwari.s-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-10-19 16:25 ` Mark Brown
[not found] ` <CAPnjgZ1A335KstnpTRwpxEbBArtqh1sYSPQJBw6LX5zUeptpfA@mail.gmail.com>
2013-10-19 20:04 ` Mark Brown
2013-10-29 10:59 ` Rajeshwari Birje
[not found] ` <CAPs=JDeOqkJT32quBH1tF9FtFUOt=CHP7m6ZqzhfASM2uPj-dw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-29 11:29 ` Rajeshwari Birje
[not found] ` <CAPs=JDdzvnM5BzgRLhLsJrdwcVSwxd6x8_kFz0EvB=OjFfVszw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-29 16:39 ` Mark Brown
[not found] ` <20131029163926.GA6776-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-30 6:22 ` Rajeshwari Birje
[not found] ` <CAPs=JDeDbevjOtMH0y+9aVSbNSV4zmEQxWygtB-f69XzooSinQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-30 17:00 ` Mark Brown
2013-10-30 17:06 ` Tomasz Figa
2013-10-31 10:47 ` Rajeshwari Birje
2013-10-31 12:37 ` Tomasz Figa
2013-11-06 4:53 ` Rajeshwari Birje
2013-11-06 8:21 ` Mark Brown
[not found] ` <20131106082141.GA11602-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-07 9:22 ` Rajeshwari Birje
[not found] ` <CAPs=JDctq1yRbuwnFH40dnQJJHF0C_D1p3iVokSPusPXA27Qeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-07 9:39 ` Tomasz Figa
2013-11-07 9:59 ` Lukasz Czerwinski
2013-11-08 11:05 ` Mark Brown
2013-11-10 17:26 ` Tomasz Figa [this message]
2013-11-13 8:28 ` Andrzej Hajda
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=3104102.55j2C8XQ5u@flatron \
--to=tomasz.figa@gmail.com \
--cc=a.hajda@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=broonie@kernel.org \
--cc=dianders@google.com \
--cc=l.czerwinski@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=rajeshwari.birje@gmail.com \
--cc=rajeshwari.s@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sjg@chromium.org \
--cc=t.figa@samsung.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).