linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@gnudd.com>
To: nsaenzjulienne@suse.de
Cc: hch@infradead.org, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	hpa@zytor.com, x86@kernel.org, bhelgaas@google.com,
	helgaas@kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 2/2] x86/PCI: sta2x11: use default DMA address translation
Date: Thu, 31 Oct 2019 14:59:00 +0100	[thread overview]
Message-ID: <20191031135900.GA11804@mail.gnudd.com> (raw)
In-Reply-To: <51101de0f3b0fc5a3678c1ee0c723b131471f1b6.camel@suse.de>

>> But I can't tested it either, and kinda wonder if this code is actually
>> still used by anyone..

I wonder too.
 
> Maybe Alessandro can shine some light on this (though I wonder his
> mail is stil valid).

Yes, the mail is valid, and I'm busy as usual.

Now, this STA2X11 is a chipset by ST-Ericcson that was bringing the
AMBA peripherals to the PC world. It was meant to be used as an I/O
device in the automotive sector, as far as I know (the audio part had
features aimed at automotive installations).  I'm sure the chip was
never used in standard PC's -- the eval board was a PCIe slot, but
that's it.

So, I can't test and I don't know if there are users of this chip.
If there are users, they are big numbers.  I think we can accept any
clean-up patch on the code base: if anything goes wrong, the users
will surface with a fix when they'll consider an upgrade to their
installed systems.

/alessndro

      parent reply	other threads:[~2019-10-31 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 11:00 [PATCH v2 0/2] x86: Get rid of custom DMA functions Nicolas Saenz Julienne
2019-10-18 11:00 ` [PATCH v2 1/2] dma-direct: check for overflows on 32 bit DMA addresses Nicolas Saenz Julienne
2019-10-30 21:41   ` Christoph Hellwig
2019-10-31 10:44     ` Nicolas Saenz Julienne
2019-10-18 11:00 ` [PATCH v2 2/2] x86/PCI: sta2x11: use default DMA address translation Nicolas Saenz Julienne
2019-10-30 21:45   ` Christoph Hellwig
2019-10-31 10:43     ` Nicolas Saenz Julienne
2019-10-31 13:59     ` Alessandro Rubini [this message]

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=20191031135900.GA11804@mail.gnudd.com \
    --to=rubini@gnudd.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=hch@infradead.org \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).