Re: [PATCH RFC v2 04/11] tty: xuartps: Remove bogus comment and register write

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2014-03-07 at 09:28PM +0000, One Thousand Gnomes wrote:
> On Fri,  7 Mar 2014 11:13:27 -0800
> Soren Brinkmann <soren.brinkmann@xxxxxxxxxx> wrote:
> 
> > Signed-off-by: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx>
> > ---
> >  drivers/tty/serial/xilinx_uartps.c | 6 +-----
> >  1 file changed, 1 insertion(+), 5 deletions(-)
> > 
> > diff --git a/drivers/tty/serial/xilinx_uartps.c b/drivers/tty/serial/xilinx_uartps.c
> > index a4bd6242e72d..a39c2d290902 100644
> > --- a/drivers/tty/serial/xilinx_uartps.c
> > +++ b/drivers/tty/serial/xilinx_uartps.c
> > @@ -1082,11 +1082,7 @@ static void xuartps_console_write(struct console *co, const char *s,
> >  
> >  	xuartps_writel(ctrl, XUARTPS_CR_OFFSET);
> >  
> > -	/* restore interrupt state, it seems like there may be a h/w bug
> > -	 * in that the interrupt enable register should not need to be
> > -	 * written based on the data sheet
> > -	 */
> > -	xuartps_writel(~imr, XUARTPS_IDR_OFFSET);
> > +	/* restore interrupt state */
> 
> It would be appropriate for the changelog at least to explain why the
> note about the data sheet differing is going away !

I don't know why anybody ever thought things are broken. IMHO, the
comment does not make any sense. Why would it not be required to write
the enable register when you enable interrupts?
I think someone read the data sheet wrong.

	Sören


--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux