public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/3] spi: mxs_spi: DM conversion
Date: Fri, 11 May 2018 13:31:49 +0200	[thread overview]
Message-ID: <ef5cbde7-e628-6ac2-ddab-7453453bf810@gmail.com> (raw)
In-Reply-To: <CAE_TBZxbpoQ0eYax5NyBNsaeN=N5wNzwM3CphjWx15dFtun5=A@mail.gmail.com>

On 05/11/2018 01:09 PM, Akash Gajjar wrote:
> Hello Marek,
> 
> On Fri, May 11, 2018 at 4:09 PM, Marek Vasut <marek.vasut@gmail.com
> <mailto:marek.vasut@gmail.com>> wrote:
> 
>     On 05/11/2018 12:08 PM, Gajjar Akash wrote:
>     > Hi Marek,
>     >
>     > Thanks for the review comments.
>     >
>     >     > -struct mxs_spi_slave {
>     >     > -     struct spi_slave        slave;
>     >     > -     uint32_t                max_khz;
>     >     > -     uint32_t                mode;
>     >     > -     struct mxs_ssp_regs     *regs;
>     >     > +struct mxs_spi_priv {
>     >     > +     struct mxs_ssp_regs *regs;
>     >     > +     u32     max_khz;
>     >     > +     u32     mode;
>     >     > +     u32     bus;
>     >     > +     u32     cs;
>     >
>     >     Type cleanup should be a separate patch
>     >
>     >  
>     > Okay, I will prepare seperate patch for type cleanup.
>     >
>     >
>     >     >  };
>     >     >               if (mxs_wait_mask_set(&ssp_regs->hw_ssp_ctrl0_reg,
>     >     >                       SSP_CTRL0_RUN, MXS_SPI_MAX_TIMEOUT)) {
>     >     > -                     printf("MXS SPI: Timeout waiting for
>     start\n");
>     >     > +                     debug("MXS SPI: Timeout waiting for
>     start\n");
>     >
>     >     printf , we don't want to hide errors
>     >
>     >  
>     > okay, will revert it back to printf.
>     >
>     >
>     >     >                       return -ETIMEDOUT;
>     >     >               }
>     >
>     >     > +
>     >     > +#ifndef __SPI_MXS_H
>     >     > +#define __SPI_MXS_H
>     >     > +
>     >     > +struct mxs_spi_platdata {
>     >     > +     struct mxs_ssp_regs *regs;
>     >     > +     u32 bus;
>     >     > +     u32 max_hz;
>     >     > +     u32 cs;
>     >
>     >     Why is this header here at all ?
>     >
>     >  
>     > I didnt get this comment. do I need to place it somewhere else?
> 
>     See the beginning of this email, it seems the same structure exists
>     twice.
> 
> 
> ​My intention was to have two individual structure for private and
> platform data.​
> But now I could use one structre and access its members using two
> structure variables(one for private and one for platadata).
> 
> Is That looks okay?

I do not quite understand what you mean, but there is a duplication of
information here. That's a problem and should be fixed.

-- 
Best regards,
Marek Vasut

      reply	other threads:[~2018-05-11 11:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <akash@openedev.com>
2018-04-26 16:46 ` [U-Boot] [PATCH v1 1/3] spi: sh_qspi: DM conversion Akash Gajjar
2018-04-27  6:06   ` Jagan Teki
2018-04-26 16:48 ` [U-Boot] [PATCH v1 2/3] spi: sh_spi: " Akash Gajjar
2018-04-27  6:22   ` Jagan Teki
2018-04-26 16:50 ` [U-Boot] [PATCH v1 3/3] spi: mxs_spi: " Akash Gajjar
2018-04-27  6:40   ` Jagan Teki
2018-05-09  6:36 ` [U-Boot] [PATCH v2 1/3] spi: sh_qspi: full " Akash Gajjar
2018-05-09 11:21   ` Jagan Teki
2018-05-09  6:57 ` [U-Boot] [PATCH v2 2/3] spi: sh_spi: " Akash Gajjar
2018-05-09  7:04 ` [U-Boot] [PATCH v2 3/3] spi: mxs_spi: full dm conversion Akash Gajjar
2018-05-09  7:07 ` [U-Boot] [PATCH v1 1/1] spi: lpc32xx_ssp: DM conversion Akash Gajjar
2018-09-04  6:33   ` Jagan Teki
2018-09-19 11:32     ` Vladimir Zapolskiy
2018-11-05 10:09       ` Jagan Teki
2018-05-10 14:13 ` [U-Boot] [PATCH v3 1/3] spi: sh_qspi: " Akash Gajjar
2018-05-10 14:15 ` [U-Boot] [PATCH v3 2/3] spi: sh_spi: " Akash Gajjar
2018-05-10 14:17 ` [U-Boot] [PATCH v3 3/3] spi: mxs_spi: " Akash Gajjar
2018-05-10 14:30   ` Marek Vasut
2018-05-11 10:08     ` Gajjar Akash
2018-05-11 10:39       ` Marek Vasut
2018-05-11 11:09         ` Akash Gajjar
2018-05-11 11:31           ` Marek Vasut [this message]

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=ef5cbde7-e628-6ac2-ddab-7453453bf810@gmail.com \
    --to=marek.vasut@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox