mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250_pci: Fix EXAR feature control register constants
Date: Tue, 7 Feb 2017 13:01:21 +0100	[thread overview]
Message-ID: <438e72ec-59e8-5fce-129d-8a8f381f1c5e@siemens.com> (raw)
In-Reply-To: <CAHp75VcmVSwMrEB2+nyWWFeMWct6afqe-N2ROHSXw6cr8ym=gg@mail.gmail.com>

On 2017-02-07 12:55, Andy Shevchenko wrote:
> +Cc Sudip
> 
> On Fri, Feb 3, 2017 at 3:22 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> According to the XR17V352 manual, bit 4 is IrDA control and bit 5 for
>> 485. Fortunately, no driver used them so far.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>  include/uapi/linux/serial_reg.h | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/uapi/linux/serial_reg.h b/include/uapi/linux/serial_reg.h
>> index b4c0484..b1f60cb 100644
>> --- a/include/uapi/linux/serial_reg.h
>> +++ b/include/uapi/linux/serial_reg.h
>> @@ -366,8 +366,8 @@
>>  #define UART_EXAR_DVID         0x8d    /* Device identification */
>>
>>  #define UART_EXAR_FCTR         0x08    /* Feature Control Register */
>> -#define UART_FCTR_EXAR_IRDA    0x08    /* IrDa data encode select */
>> -#define UART_FCTR_EXAR_485     0x10    /* Auto 485 half duplex dir ctl */
>> +#define UART_FCTR_EXAR_IRDA    0x10    /* IrDa data encode select */
>> +#define UART_FCTR_EXAR_485     0x20    /* Auto 485 half duplex dir ctl */
>>  #define UART_FCTR_EXAR_TRGA    0x00    /* FIFO trigger table A */
>>  #define UART_FCTR_EXAR_TRGB    0x60    /* FIFO trigger table B */
>>  #define UART_FCTR_EXAR_TRGC    0x80    /* FIFO trigger table C */
> 
> 
> 

BTW, I recalled that Greg preferred to remove these regs from uapi. Once
I'm done with moving the fastcom exar code over to 8250_exar.c
(currently compiling...), I'll also write a patch to move these defines
in the same file.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2017-02-07 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 13:22 Jan Kiszka
2017-02-07 11:55 ` Andy Shevchenko
2017-02-07 12:01   ` Jan Kiszka [this message]
2017-02-07 12:21     ` Andy Shevchenko

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=438e72ec-59e8-5fce-129d-8a8f381f1c5e@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudip.mukherjee@codethink.co.uk \
    /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

all inboxes | Powered by JetHome®