All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v1 1/2] clk: socfpga: Read the clock parent's register base in probe function
Date: Mon, 6 Apr 2020 07:28:53 -0400	[thread overview]
Message-ID: <20200406112853.GI27133@bill-the-cat> (raw)
In-Reply-To: <1583742120-6661-2-git-send-email-chee.hong.ang@intel.com>

On Mon, Mar 09, 2020 at 01:21:59AM -0700, chee.hong.ang at intel.com wrote:

> From: Chee Hong Ang <chee.hong.ang@intel.com>
> 
> This commit (82de42fa14682d408da935adfb0f935354c5008f) calls child's
> ofdata_to_platdata() method before the parent is probed in dm core.
> This has caused the driver no longer able to get the correct parent
> clock's register base in the ofdata_to_platdata() method because the
> parent clocks will only be probed after the child's ofdata_to_platdata().
> To resolve this, the clock parent's register base will only be retrieved
> by the child in probe() method instead of ofdata_to_platdata().
> 
> Signed-off-by: Chee Hong Ang <chee.hong.ang@intel.com>
> Reviewed-by: Ley Foon Tan <ley.foon.tan@intel.com>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200406/d63d249c/attachment.sig>

  parent reply	other threads:[~2020-04-06 11:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09  8:21 [PATCH v1 0/2] Fix A10 clock driver crash after changes in DM core chee.hong.ang at intel.com
2020-03-09  8:21 ` [PATCH v1 1/2] clk: socfpga: Read the clock parent's register base in probe function chee.hong.ang at intel.com
2020-03-09  9:05   ` Tan, Ley Foon
2020-03-09 12:28   ` Marek Vasut
2020-03-09 12:52     ` Ang, Chee Hong
2020-03-09 12:53       ` Marek Vasut
2020-03-11 11:50   ` Simon Glass
2020-03-11 11:54     ` Marek Vasut
2020-03-11 12:27       ` Simon Glass
2020-04-01  2:33         ` Ang, Chee Hong
2020-04-02  2:34           ` Simon Glass
2020-04-02  2:40             ` Marek Vasut
2020-04-02  2:44               ` Ang, Chee Hong
2020-04-02 18:50                 ` Simon Glass
2020-04-02 19:45                   ` Marek Vasut
2020-04-02 19:49                     ` Simon Glass
2020-04-02 19:50                       ` Marek Vasut
2020-04-02 19:53                       ` Simon Goldschmidt
2020-04-02 19:54                         ` Marek Vasut
2020-04-02 19:56                           ` Simon Glass
2020-04-02 19:58                           ` Simon Goldschmidt
2020-04-02 20:54                     ` Tom Rini
2020-04-02 21:07                       ` Marek Vasut
2020-04-02 21:52                         ` Simon Glass
2020-04-02 22:10                         ` Tom Rini
2020-04-02 22:47                           ` Marek Vasut
2020-04-03  3:52                             ` Tan, Ley Foon
2020-04-03 12:21                               ` Tom Rini
2020-04-06  8:57                                 ` Tan, Ley Foon
2020-04-06 11:28   ` Tom Rini [this message]
2020-04-06 11:34     ` Marek Vasut
2020-03-09  8:22 ` [PATCH v1 2/2] clk: socfpga: Switch to use ofnode API chee.hong.ang at intel.com
2020-03-09  9:05   ` Tan, Ley Foon

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=20200406112853.GI27133@bill-the-cat \
    --to=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.