public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/3] apalis_t30: fix optional pcie port reset for reliable pcie operation
Date: Wed, 9 Aug 2017 20:18:57 +0000	[thread overview]
Message-ID: <1502309935.27304.17.camel@toradex.com> (raw)
In-Reply-To: <7cd32d60-a4a2-2424-6c5e-bd531ac4a9d6@wwwdotorg.org>

On Wed, 2017-08-09 at 12:51 -0600, Stephen Warren wrote:
> On 08/09/2017 09:44 AM, Marcel Ziswiler wrote:
> > From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> > 
> > Allow optionally bringing up the Apalis type specific 4 lane PCIe
> > port
> > as well as the PCIe switch as found on the Apalis Evaluation board.
> > In
> > order to avoid violating the PCIe reset timing do this by
> > overriding the
> > tegra_pcie_board_port_reset() function. Note however that both the
> > Apalis type specific 4 lane PCIe port as well as the regular Apalis
> > PCIe
> > port are also left disabled in the device tree by default.
> > diff --git a/board/toradex/apalis_t30/apalis_t30.c
> > b/board/toradex/apalis_t30/apalis_t30.c
> > +void tegra_pcie_board_port_reset(struct tegra_pcie_port *port)
> > +			/*
> > +			 * Reset PLX PEX 8605 PCIe Switch plus
> > PCIe devices on
> > +			 * Apalis Evaluation Board
> > +			 */
> > +			gpio_direction_output(PEX_PERST_N, 0);
> > +			gpio_direction_output(RESET_MOCI_CTRL, 0);
> > +
> > +			/*
> > +			 * Must be asserted for 100 ms after power
> > and clocks
> > +			 * are stable
> > +			 */
> > +			mdelay(100);
> > +
> > +			gpio_set_value(PEX_PERST_N, 1);
> > +			/*
> > +			 * Err_5: PEX_REFCLK_OUTpx/nx Clock
> > Outputs is not
> > +			 * Guaranteed Until 900 us After
> > PEX_PERST# De-assertion
> > +			 */
> > +			mdelay(1);
> > +			gpio_set_value(RESET_MOCI_CTRL, 1);
> 
> Don't we need to also call the core tegra_pcie_port_reset() function 
> here, so that the driver gets to do any reset of the PCIe controller
> HW 
> that's required? I think that part should happen irrespective of
> whether 
> CONFIG_APALIS_T30_PCIE_EVALBOARD_INIT is enabled?

I really don't think so. All it really would do is just resetting by the means of the regular PEX_CTL signals which our design is not using like that anyway.

  reply	other threads:[~2017-08-09 20:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 15:44 [U-Boot] [PATCH v2 0/3] fix apalis_t30 optional pcie operation Marcel Ziswiler
2017-08-09 15:44 ` [U-Boot] [PATCH v2 1/3] apalis_t30: describe pcie ports Marcel Ziswiler
2017-08-09 15:44 ` [U-Boot] [PATCH v2 2/3] apalis_t30: fix pcie port 0 and 1 pin muxing Marcel Ziswiler
2017-08-09 15:44 ` [U-Boot] [PATCH v2 3/3] apalis_t30: fix optional pcie port reset for reliable pcie operation Marcel Ziswiler
2017-08-09 18:51   ` Stephen Warren
2017-08-09 20:18     ` Marcel Ziswiler [this message]
2017-08-09 21:18       ` Stephen Warren

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=1502309935.27304.17.camel@toradex.com \
    --to=marcel.ziswiler@toradex.com \
    --cc=u-boot@lists.denx.de \
    /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