From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 1/5] spi: cadence_qspi: move trigger base configuration in init
Date: Thu, 27 Aug 2015 17:51:48 +0200 [thread overview]
Message-ID: <201508271751.48122.marex@denx.de> (raw)
In-Reply-To: <9026814FBF99304F9FA3AC3FB72F3E2F01EAF25236@SAFEX1MAIL4.st.com>
On Thursday, August 27, 2015 at 05:46:12 PM, Vikas MANOCHA wrote:
> Hi,
>
> > -----Original Message-----
> > From: Marek Vasut [mailto:marex at denx.de]
> > Sent: Thursday, August 27, 2015 1:36 AM
> > To: Vikas MANOCHA
> > Cc: u-boot at lists.denx.de; sr at denx.de; grmoore at opensource.altera.com;
> > jteki at openedev.com
> > Subject: Re: [PATCH v5 1/5] spi: cadence_qspi: move trigger base
> > configuration in init
> >
> > On Thursday, August 27, 2015 at 12:44:26 AM, Vikas Manocha wrote:
> > > No need to configure indirect trigger address for every read/write.
> > >
> > > Signed-off-by: Vikas Manocha <vikas.manocha@st.com>
> > > ---
> > >
> > > Changes in v5: fixed type cast compilation warnings.
> > > Changes in v4: removed extra type casts.
> > > Changes in v3: added commit message & removed extra bracket.
> > > Changes in v2: Rebased to master
> > >
> > > drivers/spi/cadence_qspi_apb.c | 9 ++-------
> > > 1 file changed, 2 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/drivers/spi/cadence_qspi_apb.c
> > > b/drivers/spi/cadence_qspi_apb.c index d053407..d377ad1 100644
> > > --- a/drivers/spi/cadence_qspi_apb.c
> > > +++ b/drivers/spi/cadence_qspi_apb.c
> > > @@ -534,6 +534,8 @@ void cadence_qspi_apb_controller_init(struct
> > > cadence_spi_platdata *plat)
> > >
> > > /* Indirect mode configurations */
> > > writel((plat->sram_size/2), plat->regbase +
> > >
> > > CQSPI_REG_SRAMPARTITION);
> > > + writel((u32)plat->ahbbase &
> >
> > CQSPI_INDIRECTTRIGGER_ADDR_MASK,
> >
> > Why can't you just drop this masking and the cast ?
>
> Masking is dropped in another patch in same series.
So you're adding broken code first only to fix it later ? I don't like this.
> Casting is required as ahbbase is a pointer.
ahbbase is used as u32 value all around the place, so just fix it to u32
and drop the cast.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-08-27 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 22:44 [U-Boot] [PATCH v5 0/5] spi: cadence_qspi: optimize & fix indirect rd-writes Vikas Manocha
2015-08-26 22:44 ` [U-Boot] [PATCH v5 1/5] spi: cadence_qspi: move trigger base configuration in init Vikas Manocha
2015-08-27 8:36 ` Marek Vasut
2015-08-27 15:46 ` Vikas MANOCHA
2015-08-27 15:51 ` Marek Vasut [this message]
2015-08-27 16:02 ` Vikas MANOCHA
[not found] ` <90E716605AAA5544831C65DACA66330C87EC6A0DEC@SAFEX1MAIL4.st.com>
2015-08-31 20:20 ` Vikas MANOCHA
2015-08-26 22:44 ` [U-Boot] [PATCH v5 2/5] spi: cadence_qspi: fix indirect read/write start address Vikas Manocha
2015-08-27 8:37 ` Marek Vasut
2015-08-27 17:21 ` Vikas MANOCHA
2015-08-26 22:44 ` [U-Boot] [PATCH v5 3/5] spi: cadence_qspi: fix base trigger address & transfer " Vikas Manocha
2015-08-27 8:40 ` Marek Vasut
2015-08-27 17:23 ` Vikas MANOCHA
2015-08-26 22:44 ` [U-Boot] [PATCH v5 4/5] spi: cadence_qspi: rename ahbbase to flashbase for clarity Vikas Manocha
2015-08-26 22:44 ` [U-Boot] [PATCH v5 5/5] spi: cadence_qspi: get fifo width from device tree Vikas Manocha
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=201508271751.48122.marex@denx.de \
--to=marex@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox