From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/7] spi: altera: Use struct-based register access
Date: Mon, 20 Oct 2014 17:10:35 +0200 [thread overview]
Message-ID: <201410201710.35241.marex@denx.de> (raw)
In-Reply-To: <CAD6G_RQ3WqUKM-xHATdMBYVkAJpQfCog-GBcvCJZrGw-=vyJFw@mail.gmail.com>
On Monday, October 20, 2014 at 04:53:15 PM, Jagan Teki wrote:
[...]
> > -#define ALTERA_SPI_RXDATA 0
> > -#define ALTERA_SPI_TXDATA 4
> > -#define ALTERA_SPI_STATUS 8
> > -#define ALTERA_SPI_CONTROL 12
> > -#define ALTERA_SPI_SLAVE_SEL 20
> > +struct altera_spi_regs {
> > + u32 rxdata;
> > + u32 txdata;
> > + u32 status;
> > + u32 control;
> > + u32 _reserved;
> > + u32 slave_sel;
> > +};
>
> Can you place this structure definition below of all macro defines, i
> don't think the
> next level patches does that, does they?
Does it make sense to you, to first define the bits in registers and then
the register layout ? It does not make sense to me, so I would prefer to
keep it like it is.
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-20 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 18:43 [U-Boot] [PATCH 1/7] spi: altera: Use struct-based register access Marek Vasut
2014-10-19 18:43 ` [U-Boot] [PATCH 2/7] spi: altera: Clean up bit definitions Marek Vasut
2014-10-19 18:43 ` [U-Boot] [PATCH 3/7] spi: altera: Clean up most checkpatch issues Marek Vasut
2014-10-19 18:43 ` [U-Boot] [PATCH 4/7] spi: altera: Zap endless loop Marek Vasut
2014-10-20 15:03 ` Jagan Teki
2014-10-19 18:43 ` [U-Boot] [PATCH 5/7] spi: altera: Clean up the use of variable d Marek Vasut
2014-10-19 18:43 ` [U-Boot] [PATCH 6/7] spi: altera: Add short note about EPCS/EPCQx1 Marek Vasut
2014-10-20 15:10 ` Jagan Teki
2014-10-20 15:13 ` Marek Vasut
2014-10-20 17:27 ` Jagan Teki
2014-10-19 18:43 ` [U-Boot] [PATCH 7/7] spi: altera: Move the config options to the top Marek Vasut
2014-10-20 7:36 ` [U-Boot] [PATCH 1/7] spi: altera: Use struct-based register access Pavel Machek
2014-10-20 14:53 ` Jagan Teki
2014-10-20 15:10 ` Marek Vasut [this message]
2014-10-20 17:19 ` Jagan Teki
2014-10-21 22:15 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2014-10-22 19:55 Marek Vasut
2014-10-23 14:45 ` Pavel Machek
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=201410201710.35241.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 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.