All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mario Hüttel" <mario.huettel@gmx.net>
To: linux-can@vger.kernel.org
Cc: Mario Huettel <mario.huettel@gmx.net>
Subject: [PATCH v4 1/7] can: m_can: Disabled Interrupt Line 1
Date: Sat,  8 Apr 2017 14:10:09 +0200	[thread overview]
Message-ID: <20170408121015.11428-1-mario.huettel@gmx.net> (raw)

From: Mario Huettel <mario.huettel@gmx.net>

* Disabled interrupt line 1. The driver didn't use it.

Signed-off-by: Mario Huettel <mario.huettel@gmx.net>
---
 drivers/net/can/m_can/m_can.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
index 7a6554e..6797977 100644
--- a/drivers/net/can/m_can/m_can.c
+++ b/drivers/net/can/m_can/m_can.c
@@ -349,7 +349,8 @@ static inline void m_can_config_endisable(const struct m_can_priv *priv,
 
 static inline void m_can_enable_all_interrupts(const struct m_can_priv *priv)
 {
-	m_can_write(priv, M_CAN_ILE, ILE_EINT0 | ILE_EINT1);
+	/* Only interrupt line 0 is used in this driver */
+	m_can_write(priv, M_CAN_ILE, ILE_EINT0);
 }
 
 static inline void m_can_disable_all_interrupts(const struct m_can_priv *priv)
-- 
1.9.1


             reply	other threads:[~2017-04-08 12:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-08 12:10 Mario Hüttel [this message]
2017-04-08 12:10 ` [PATCH v4 2/7] can: m_can: Removed initialization of FIFO water marks Mario Hüttel
2017-04-08 12:10 ` [PATCH v4 3/7] can: m_can: Removed virtual address from print Mario Hüttel
2017-04-08 12:10 ` [PATCH v4 4/7] can: m_can: Updated register defines to newest version Mario Hüttel
2017-04-08 12:10 ` [PATCH v4 5/7] can: m_can: Enable M_CAN version dependent initialization Mario Hüttel
2017-04-08 12:10 ` [PATCH v4 6/7] can: m_can: Configuration for TX and TX event FIFOs Mario Hüttel
2017-04-08 12:10 ` [PATCH v4 7/7] can: m_can: Enable TX FIFO Handling for M_CAN IP version >= v3.1.x Mario Hüttel
     [not found]   ` <1f88411b-aa58-4e17-02cb-43fc0ffb953c@Microchip.com>
2017-04-13  6:30     ` Oliver Hartkopp
2017-04-13  6:50       ` Quentin Schulz
2017-04-18  6:04         ` AW: " Huettel Mario (AE/PJ-SCI1)
2017-04-18  6:17           ` Yang, Wenyou
2017-04-18  6:37             ` AW: " Huettel Mario (AE/PJ-SCI1)
2017-04-18  6:50             ` Huettel Mario (AE/PJ-SCI1)
2017-04-18  6:52               ` Wenyou.Yang
2017-04-19  7:11               ` AW: " Yang, Wenyou
2017-04-14  6:04       ` Yang, Wenyou
     [not found]     ` <0f51bfad-b6ac-6cb5-0487-5b746eecb8b7@Microchip.com>
2017-04-19 13:05       ` Quentin Schulz
2017-04-19 13:08       ` Oliver Hartkopp

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=20170408121015.11428-1-mario.huettel@gmx.net \
    --to=mario.huettel@gmx.net \
    --cc=linux-can@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 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.