diff options
author | Noe Rubinstein <nrubinstein@proformatique.com> | 2010-12-09 18:59:56 +0100 |
---|---|---|
committer | Noe Rubinstein <nrubinstein@proformatique.com> | 2010-12-09 18:59:56 +0100 |
commit | 7d883bf6b79a6ba50993ad34287ecf2f6698e8c8 (patch) | |
tree | bf15ef406f1857f61a0acf06f4de674962dcf7ad | |
parent | 3ac1d0d7ca9901e2024daffeb4a05dea99136104 (diff) |
deactivate requests are okay in TE.
It seems there is no one-to-one correlation between the PH-ACTIVATE,
MPH-ACTIVATE, PH-DEACTIVATE and MPH-DEACTIVATE directives on layer 1 and
V_SU_ACT writes in A_SU_WR_STA.
-rw-r--r-- | xhfc/xhfc_st_state.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/xhfc/xhfc_st_state.c b/xhfc/xhfc_st_state.c index dfa9897..b34d180 100644 --- a/xhfc/xhfc_st_state.c +++ b/xhfc/xhfc_st_state.c @@ -97,7 +97,7 @@ void deactivate_request(struct xhfc_span* s) u8 a_su_wr_sta = 0; int sta = GET_V_SU_STA(s->state); - if (!s->nt || (s->nt && (sta == G1 || sta == G4))) { + if (s->nt && (sta == G1 || sta == G4)) { printk(KERN_INFO DRIVER_NAME ": " "deactivate impossible by definition of layer 1" " in state %c%d on port %d\n", |