From: Eddie James <eajames@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
openbmc@lists.ozlabs.org
Cc: Andrew Jeffery <andrew@aj.id.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 4/5] fsi/scom: Add register definitions
Date: Wed, 13 Jun 2018 09:57:42 -0500 [thread overview]
Message-ID: <4bbb38ae-2d34-b63f-ed67-d55d31673af3@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180612051911.20690-5-benh@kernel.crashing.org>
On 06/12/2018 12:19 AM, Benjamin Herrenschmidt wrote:
> Add a few more register and bit definitions, also define and use
> SCOM_READ_CMD (which is 0 but it makes the code clearer)
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Reviewed-by: Eddie James <eajames@linux.vnet.ibm.com>
> ---
> drivers/fsi/fsi-scom.c | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/fsi/fsi-scom.c b/drivers/fsi/fsi-scom.c
> index 6ddfb6021420..e98573ecdae1 100644
> --- a/drivers/fsi/fsi-scom.c
> +++ b/drivers/fsi/fsi-scom.c
> @@ -30,8 +30,25 @@
> #define SCOM_DATA0_REG 0x00
> #define SCOM_DATA1_REG 0x04
> #define SCOM_CMD_REG 0x08
> +#define SCOM_FSI2PIB_RESET_REG 0x18
> +#define SCOM_STATUS_REG 0x1C /* Read */
> +#define SCOM_PIB_RESET_REG 0x1C /* Write */
>
> +/* Command register */
> #define SCOM_WRITE_CMD 0x80000000
> +#define SCOM_READ_CMD 0x00000000
> +
> +/* Status register bits */
> +#define SCOM_STATUS_ERR_SUMMARY 0x80000000
> +#define SCOM_STATUS_PROTECTION 0x01000000
> +#define SCOM_STATUS_PIB_ABORT 0x00100000
> +#define SCOM_STATUS_PIB_RESP_MASK 0x00007000
> +#define SCOM_STATUS_PIB_RESP_SHIFT 12
> +
> +#define SCOM_STATUS_ANY_ERR (SCOM_STATUS_ERR_SUMMARY | \
> + SCOM_STATUS_PROTECTION | \
> + SCOM_STATUS_PIB_ABORT | \
> + SCOM_STATUS_PIB_RESP_MASK)
>
> struct scom_device {
> struct list_head link;
> @@ -85,7 +102,7 @@ static int get_scom(struct scom_device *scom_dev, uint64_t *value,
>
> mutex_lock(&scom_dev->lock);
> *value = 0ULL;
> - data = cpu_to_be32(addr);
> + data = cpu_to_be32(SCOM_READ_CMD | addr);
> rc = fsi_device_write(scom_dev->fsi_dev, SCOM_CMD_REG, &data,
> sizeof(uint32_t));
> if (rc)
next prev parent reply other threads:[~2018-06-13 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 5:19 [RFC PATCH 0/5] FSI scom driver overhaul Benjamin Herrenschmidt
2018-06-12 5:19 ` [RFC PATCH 1/5] fsi/scom: Add mutex around FSI2PIB accesses Benjamin Herrenschmidt
2018-06-13 14:59 ` Eddie James
2018-06-12 5:19 ` [RFC PATCH 2/5] fsi/scom: Whitespace fixes Benjamin Herrenschmidt
2018-06-13 14:58 ` Eddie James
2018-06-12 5:19 ` [RFC PATCH 3/5] fsi/scom: Fixup endian annotations Benjamin Herrenschmidt
2018-06-13 14:58 ` Eddie James
2018-06-12 5:19 ` [RFC PATCH 4/5] fsi/scom: Add register definitions Benjamin Herrenschmidt
2018-06-13 14:57 ` Eddie James [this message]
2018-06-12 5:19 ` [RFC PATCH 5/5] fsi/scom: Major overhaul Benjamin Herrenschmidt
2018-06-13 14:57 ` Eddie James
2018-06-13 23:00 ` Benjamin Herrenschmidt
2018-06-14 14:12 ` Eddie James
2018-06-16 5:04 ` Joel Stanley
2018-06-17 1:17 ` Benjamin Herrenschmidt
2018-06-17 1:22 ` Benjamin Herrenschmidt
2018-06-18 4:09 ` Alistair Popple
2018-06-18 4:46 ` Benjamin Herrenschmidt
2018-06-18 5:05 ` Alistair Popple
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=4bbb38ae-2d34-b63f-ed67-d55d31673af3@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
/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
Powered by JetHome