All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagannadh.teki@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/3] cadence-quadspi: Fix issues with non 32bit aligned accesses
Date: Tue, 23 Jan 2018 14:54:42 +0530	[thread overview]
Message-ID: <CAD6G_RQ_YUq+N7LL-xLH4117u66B3pGx-F_Lb_ZbpxUJnQfxSQ@mail.gmail.com> (raw)
In-Reply-To: <297e1b66-dae3-9884-1ad1-34ae452d97c1@ti.com>

On Tue, Jan 23, 2018 at 2:46 PM, Vignesh R <vigneshr@ti.com> wrote:
>
>
> On Tuesday 23 January 2018 02:37 PM, Jagan Teki wrote:
>> On Tue, Jan 23, 2018 at 2:32 PM, Vignesh R <vigneshr@ti.com> wrote:
>>>
>>>
>>> On Tuesday 23 January 2018 02:15 PM, Jagan Teki wrote:
>>>> On Tue, Jan 23, 2018 at 1:42 PM, Simon Goldschmidt
>>>> <sgoldschmidt@de.pepperl-fuchs.com> wrote:
>>>>> Jagan,
>>>>>
>>>>>
>>>>> the merge window is now less than 1 week for 2018.03 if I'm not mistaken.
>>>>> Can you apply this, please?
>>>>
>>>> Can you resend these on-top of u-boot-spi/master, have few changes on
>>>> wait_for_bit good to test those as well.
>>>
>>> u-boot-spi/master throws few warnings when I build for my platform:
>>> ~/workspace/u-boot:0f520af57c60:~ make distclean;make k2g_evm_defconfig;make -j4 -s;
>>>
>>> In file included from drivers/spi/cadence_qspi_apb.c:31:0:
>>> include/wait_bit.h: In function 'wait_for_bit_be16':
>>> include/wait_bit.h:76:31: warning: implicit declaration of function 'readw_be' [-Wimplicit-function-declaration]
>>>  BUILD_WAIT_FOR_BIT(be16, u16, readw_be)
>>>                                ^
>>> include/wait_bit.h:48:9: note: in definition of macro 'BUILD_WAIT_FOR_BIT'
>>>    val = read(reg);     \
>>>          ^~~~
>>> include/wait_bit.h: In function 'wait_for_bit_be32':
>>> include/wait_bit.h:78:31: warning: implicit declaration of function 'readl_be' [-Wimplicit-function-declaration]
>>>  BUILD_WAIT_FOR_BIT(be32, u32, readl_be)
>>>                                ^
>>> include/wait_bit.h:48:9: note: in definition of macro 'BUILD_WAIT_FOR_BIT'
>>>    val = read(reg);     \
>>>          ^~~~
>>
>> Did you change wait_for_bit function with _le32? [1]
>>
>> [1] http://git.denx.de/?p=u-boot-spi.git;a=commitdiff;h=9a5ff2669ef185d3a4bf73415c531e8d013993d8
>>
>
> Yes, I am building plain u-boot-spi/master(HEAD: 0f520af57c60f3baba8
> ("spi: kirkwood_spi: implement workaround for FE-9144572")). So, above
> commit is part of the tree.
>
> Problem is above commit adds
> BUILD_WAIT_FOR_BIT(be32, u32, read*_be) variants.
> But, readl_be and readw_be seems to be undefined for ARM?

yes, but wait_for_bit_le32 work for arm?

  reply	other threads:[~2018-01-23  9:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 13:19 [U-Boot] [PATCH v2 0/3] cadence-quadspi: Fix issues with non 32bit aligned accesses Vignesh R
2018-01-09 13:19 ` [U-Boot] [PATCH v2 1/3] Revert "spi: cadence_qspi_apb: Use 32 bit indirect read transaction when possible" Vignesh R
2018-01-09 13:19 ` [U-Boot] [PATCH v2 2/3] Revert "spi: cadence_qspi_apb: Use 32 bit indirect write " Vignesh R
2018-01-09 13:19 ` [U-Boot] [PATCH v2 3/3] spi: cadence_qspi_apb: Make flash writes 32 bit aligned Vignesh R
2018-01-15 11:36 ` [U-Boot] [PATCH v2 0/3] cadence-quadspi: Fix issues with non 32bit aligned accesses Vignesh R
2018-01-15 11:45   ` Marek Vasut
2018-01-15 12:01     ` Simon Goldschmidt
2018-01-15 13:47       ` Jason Rush
2018-01-23  8:12         ` Simon Goldschmidt
2018-01-23  8:45           ` Jagan Teki
2018-01-23  9:02             ` Vignesh R
2018-01-23  9:07               ` Jagan Teki
2018-01-23  9:16                 ` Vignesh R
2018-01-23  9:24                   ` Jagan Teki [this message]
2018-01-23  9:26                   ` Simon Goldschmidt
2018-01-23  9:31                     ` Jagan Teki
2018-01-23 10:05                       ` Vignesh R
2018-01-10 15:33 Goldschmidt Simon
2018-01-10 15:39 ` Marek Vasut

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=CAD6G_RQ_YUq+N7LL-xLH4117u66B3pGx-F_Lb_ZbpxUJnQfxSQ@mail.gmail.com \
    --to=jagannadh.teki@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.