Linux ACPI
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Daniel Scally <djrscally@gmail.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Implementation of fwnode_operations :: device_get_match_data() for software nodes?
Date: Tue, 28 Feb 2023 01:07:47 +0200	[thread overview]
Message-ID: <20230227230747.zzthvwb7vsg5sq7e@skbuf> (raw)
In-Reply-To: <Y/yfs3Zo70gV/V9b@kuha.fi.intel.com>

Hi Heikki,

On Mon, Feb 27, 2023 at 02:18:59PM +0200, Heikki Krogerus wrote:
> Try this - I'm sorry, I don't know does it actually work:

Thanks for the patch. I'm not able to tell you right now if it works or
not, because my PowerPC board on which I needed this started developing
this issue in U-Boot over the weekend:

DRAM:  Initializing....using SPD
Detected UDIMM i-DIMM
Waiting for D_INIT timeout. Memory may not work.
2 GiB left unmapped

and now I'm in the process of resoldering the DDR slot, process of which
I've had enough for today and I'll continue tomorrow.

  reply	other threads:[~2023-02-27 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 20:37 Implementation of fwnode_operations :: device_get_match_data() for software nodes? Vladimir Oltean
2023-02-27 12:18 ` Heikki Krogerus
2023-02-27 23:07   ` Vladimir Oltean [this message]
2023-02-27 22:26 ` Andy Shevchenko
2023-02-27 23:44   ` Vladimir Oltean
2023-03-01 14:33     ` Andy Shevchenko
2023-03-01 14:36       ` Vladimir Oltean
2023-03-01 15:09         ` Andy Shevchenko
2023-03-01 15:25           ` Vladimir Oltean
2023-03-01 15:34             ` Andy Shevchenko
2023-03-01 17:18               ` Vladimir Oltean
2023-03-01 17:33                 ` Andy Shevchenko
2023-03-01 17:43                   ` Vladimir Oltean
2024-03-25 13:41                     ` Andy Shevchenko
2024-03-25 15:16                       ` Herve Codina
2024-03-25 15:39                         ` Andy Shevchenko
2024-03-25 15:57                           ` Herve Codina

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=20230227230747.zzthvwb7vsg5sq7e@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=djrscally@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sakari.ailus@linux.intel.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