From: Jan Kiszka <jan.kiszka@siemens.com>
To: Technical Support <techsupport@commtech-fastcom.com>
Cc: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: gpio-exar: Why filtering out Commtech devices?
Date: Tue, 23 May 2017 17:05:34 +0200 [thread overview]
Message-ID: <2445db07-a150-e954-099c-f39faefeb4b5@siemens.com> (raw)
In-Reply-To: <CAPpjZG_HPFqKzf+7rBxM27TJcZJ4+vfUYSPChifM-JTN7ekTOA@mail.gmail.com>
On 2017-05-23 16:33, Technical Support wrote:
> Both the PCI and the PCIe cards use the MPIO pins and the device driver
> actually sets the pins as outputs after registering the device with the
> PCI core. So the changes made to the default settings shouldn't break
> anything.
>
> Do the new default settings keep the UART_EXAR_MPIOINT_X_X values at
> 0x00 to disable their interrupts?
Look at
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=7dea8165f1d6434dc7572004363f86339f0f4322
Interrupts remain off, but all pins are now inputs. Again, if the logic
on the PCIe cards need any of them to be driven low, my patch causes a
regression. In that case, we also need to make the MPIO setup card-specific.
Thanks,
Jan
>
> -Landon
>
> Commtech, Inc.
> Voice: 316-636-1131 <tel:%28316%29%20636-1131>
> http://www.fastcomproducts.com
>
>
>
>
> On Mon, May 22, 2017 at 1:18 PM, Jan Kiszka <jan.kiszka@siemens.com
> <mailto:jan.kiszka@siemens.com>> wrote:
>
> On 2017-05-22 18:24, Jan Kiszka wrote:
> > On 2017-05-22 17:17, Technical Support wrote:
> >> Hello,
> >>
> >> The Exar MPIO pins are used by our device driver to control features of
> >> the line driver and can't be used as GPIO pins. I agree, the condition
> >> can be moved to 8250_exar prior to a platform device being created for
> >> the gpio_exar driver.
> >>
> >
> > Thanks a lot for the feedback! I will send a refactoring patch.
>
> Hmm, are you possibly talking about PCI device with the IDs 0x2, 0x4,
> 0xa, 0xb (4222PCI335, 4224PCI335, 2324PCI335, 2328PCI335), because those
> actually set the GPIOs for apparent internal reasons. However,
> 0x20..0x22 (4222PCIE, 4224PCIE, 4228PCIE) already share setup_gpio() via
> pci_xr17v35x_setup(), and that looks different.
>
> I'm also asking again because we just changed the default MPIO settings
> for the latter to all inputs. If you depended on them to be all outputs
> and 0, we may have broken something.
>
> Thanks,
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA ITP SES-DE
> Corporate Competence Center Embedded Linux
>
>
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-05-23 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 11:46 gpio-exar: Why filtering out Commtech devices? Jan Kiszka
2017-05-21 20:08 ` Sudip Mukherjee
2017-05-22 5:48 ` Jan Kiszka
2017-05-22 5:51 ` Jan Kiszka
[not found] ` <CAPpjZG9MGDzS0Bu2c6M-Pob5JkzeAptDu8QNnDJETinCenee0w@mail.gmail.com>
2017-05-22 16:24 ` Jan Kiszka
2017-05-22 18:18 ` Jan Kiszka
[not found] ` <CAPpjZG_HPFqKzf+7rBxM27TJcZJ4+vfUYSPChifM-JTN7ekTOA@mail.gmail.com>
2017-05-23 15:05 ` Jan Kiszka [this message]
[not found] ` <CAPpjZG953JHZWt8UzgEmYurSMh9o1v5HvxmO+4FD41M92GA-Ww@mail.gmail.com>
2017-05-23 21:16 ` Jan Kiszka
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=2445db07-a150-e954-099c-f39faefeb4b5@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sudip.mukherjee@codethink.co.uk \
--cc=techsupport@commtech-fastcom.com \
/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