From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
Jamie Iles <jamie@jamieiles.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH 3/5] tty/8250_dw: Add support for OCTEON UARTS.
Date: Wed, 19 Jun 2013 17:10:08 +0300 [thread overview]
Message-ID: <20130619141008.GA32331@xps8300> (raw)
In-Reply-To: <1371582775-12141-4-git-send-email-ddaney.cavm@gmail.com>
On Tue, Jun 18, 2013 at 12:12:53PM -0700, David Daney wrote:
> A few differences needed by OCTEON:
>
> o These are DWC UARTS, but have USR at a different offset.
>
> o OCTEON must have 64-bit wide register accesses, so we have OCTEON
> specific register accessors.
>
> o No UCV register, so we hard code some properties.
>
> Signed-off-by: David Daney <david.daney@cavium.com>
<snip>
> @@ -270,10 +301,8 @@ static int dw8250_probe(struct platform_device *pdev)
> uart.port.serial_out = dw8250_serial_out;
> uart.port.private_data = data;
>
> - dw8250_setup_port(&uart);
> -
> if (pdev->dev.of_node) {
> - err = dw8250_probe_of(&uart.port);
> + err = dw8250_probe_of(&uart.port, data);
> if (err)
> return err;
> } else if (ACPI_HANDLE(&pdev->dev)) {
> @@ -284,6 +313,9 @@ static int dw8250_probe(struct platform_device *pdev)
> return -ENODEV;
> }
>
> + if (!data->no_ucv)
> + dw8250_setup_port(&uart);
Moving the dw8250_setup_port() call here breaks dw8250_probe_acpi(). It
expects values from the CPR register for the DMA burst size calculation.
The DMA support can be moved to a separate function. This way it can
be called after this point, and it will then be available for both DT
and ACPI. I can make a patch tomorrow. That should solve this issue.
Thanks,
--
heikki
next prev parent reply other threads:[~2013-06-19 14:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 19:12 [PATCH 0/5] MIPS/tty/8250: Use standard 8250 drivers for OCTEON David Daney
2013-06-18 19:12 ` [PATCH 1/5] Revert "MIPS: Octeon: Fix build error if CONFIG_SERIAL_8250=n" David Daney
2013-06-18 19:12 ` [PATCH 2/5] MIPS: OCTEON: Set proper UART clock in internal device trees David Daney
2013-06-18 19:12 ` [PATCH 3/5] tty/8250_dw: Add support for OCTEON UARTS David Daney
2013-06-18 19:26 ` Greg Kroah-Hartman
2013-06-19 10:01 ` Arnd Bergmann
2013-06-19 10:52 ` Ralf Baechle
2013-06-19 16:45 ` David Daney
2013-06-19 18:52 ` Arnd Bergmann
2013-06-19 19:12 ` David Daney
2013-06-19 14:10 ` Heikki Krogerus [this message]
2013-06-19 16:47 ` David Daney
2013-06-18 19:12 ` [PATCH 4/5] MIPS: OCTEON: Remove custom serial setup code David Daney
2013-06-18 19:12 ` [PATCH 5/5] MIPS: Update cavium_octeon_defconfig David Daney
2013-06-18 19:26 ` [PATCH 0/5] MIPS/tty/8250: Use standard 8250 drivers for OCTEON Greg Kroah-Hartman
2013-06-18 19:36 ` Ralf Baechle
2013-06-18 19:59 ` David Daney
2013-06-18 21:28 ` Jamie Iles
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=20130619141008.GA32331@xps8300 \
--to=heikki.krogerus@linux.intel.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jamie@jamieiles.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=ralf@linux-mips.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).