From: isdn@linux-pingi.de
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: netdev@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mISDN: Order IPAC register defines
Date: Sun, 13 Mar 2016 04:13:20 +0100 [thread overview]
Message-ID: <56E4DAD0.3040800@linux-pingi.de> (raw)
In-Reply-To: <56E4A3AE.8050407@maciej.szmigiero.name>
Acked-by: Karsten Keil <keil@b1-systems.de>
Am 13.03.2016 um 00:18 schrieb Maciej S. Szmigiero:
> It looks like IPAC/ISAC chips register defines weren't in any particular
> order.
>
> Order them by their number to make it easier to spot holes.
>
> Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
> ---
> drivers/isdn/hardware/mISDN/ipac.h | 40 +++++++++++++++++++-------------------
> 1 file changed, 20 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/isdn/hardware/mISDN/ipac.h b/drivers/isdn/hardware/mISDN/ipac.h
> index 8121e046b739..76aa6f8f298e 100644
> --- a/drivers/isdn/hardware/mISDN/ipac.h
> +++ b/drivers/isdn/hardware/mISDN/ipac.h
> @@ -99,32 +99,32 @@ struct ipac_hw {
>
> /* All registers original Siemens Spec */
> /* IPAC/ISAC registers */
> -#define ISAC_MASK 0x20
> #define ISAC_ISTA 0x20
> -#define ISAC_STAR 0x21
> +#define ISAC_MASK 0x20
> #define ISAC_CMDR 0x21
> +#define ISAC_STAR 0x21
> +#define ISAC_MODE 0x22
> +#define ISAC_TIMR 0x23
> #define ISAC_EXIR 0x24
> -#define ISAC_ADF2 0x39
> +#define ISAC_RBCL 0x25
> +#define ISAC_RSTA 0x27
> +#define ISAC_RBCH 0x2A
> #define ISAC_SPCR 0x30
> -#define ISAC_ADF1 0x38
> #define ISAC_CIR0 0x31
> #define ISAC_CIX0 0x31
> -#define ISAC_CIR1 0x33
> -#define ISAC_CIX1 0x33
> -#define ISAC_STCR 0x37
> -#define ISAC_MODE 0x22
> -#define ISAC_RSTA 0x27
> -#define ISAC_RBCL 0x25
> -#define ISAC_RBCH 0x2A
> -#define ISAC_TIMR 0x23
> -#define ISAC_SQXR 0x3b
> -#define ISAC_SQRR 0x3b
> -#define ISAC_MOSR 0x3a
> -#define ISAC_MOCR 0x3a
> #define ISAC_MOR0 0x32
> #define ISAC_MOX0 0x32
> +#define ISAC_CIR1 0x33
> +#define ISAC_CIX1 0x33
> #define ISAC_MOR1 0x34
> #define ISAC_MOX1 0x34
> +#define ISAC_STCR 0x37
> +#define ISAC_ADF1 0x38
> +#define ISAC_ADF2 0x39
> +#define ISAC_MOCR 0x3a
> +#define ISAC_MOSR 0x3a
> +#define ISAC_SQRR 0x3b
> +#define ISAC_SQXR 0x3b
>
> #define ISAC_RBCH_XAC 0x80
>
> @@ -212,13 +212,13 @@ struct ipac_hw {
> #define ISAC_CMD_DUI 0xF
>
> /* ISAC/ISACX/IPAC/IPACX L1 indications */
> -#define ISAC_IND_RS 0x1
> -#define ISAC_IND_PU 0x7
> #define ISAC_IND_DR 0x0
> +#define ISAC_IND_RS 0x1
> #define ISAC_IND_SD 0x2
> #define ISAC_IND_DIS 0x3
> -#define ISAC_IND_EI 0x6
> #define ISAC_IND_RSY 0x4
> +#define ISAC_IND_EI 0x6
> +#define ISAC_IND_PU 0x7
> #define ISAC_IND_ARD 0x8
> #define ISAC_IND_TI 0xA
> #define ISAC_IND_ATI 0xB
> @@ -339,9 +339,9 @@ struct ipac_hw {
> #define ISACX__AUX 0x08
> #define ISACX__CIC 0x10
> #define ISACX__ST 0x20
> +#define IPACX__ON 0x2C
> #define IPACX__ICB 0x40
> #define IPACX__ICA 0x80
> -#define IPACX__ON 0x2C
>
> /* ISACX/IPACX _CMDRD (W) */
> #define ISACX_CMDRD_XRES 0x01
>
>
next prev parent reply other threads:[~2016-03-13 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 23:18 [PATCH 1/2] mISDN: Order IPAC register defines Maciej S. Szmigiero
2016-03-13 3:13 ` isdn [this message]
2016-03-14 19:51 ` David Miller
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=56E4DAD0.3040800@linux-pingi.de \
--to=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).