All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] arm64: dts: rockchip: vdd_log is not an i2c slave
Date: Mon, 19 Feb 2018 07:01:55 +0100	[thread overview]
Message-ID: <1705208.FSornk7tld@phil> (raw)
In-Reply-To: <20180218154359.9362-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Am Sonntag, 18. Februar 2018, 16:43:59 CET schrieb Vicente Bergas:
> The vdd_log power supply is controlled by a PWM pin, not by i2c register access.
> There is a boot message that reports an error about not being able to bring that supply up.
> Also, the eMMC is not detected and /dev/mmcblk2 does not exist.
> 
> References:
> [1]
> Schematic page 16, search for LOG_DVS_PWM
> https://dl.vamrs.com/products/sapphire_excavator/RK_SAPPHIRE_SOCBOARD_RK3399_LPDDR3D178P232SD8_V12_20161109HXS.pdf
> (alternate link)
> http://opensource.rock-chips.com/images/f/f0/RK_Sapphire_RK3399.rar
> 
> [2]
> arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
> 
> Signed-off-by: Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

I've adapted the commit message a bit and applied the patch
for 4.17

For the emmc, that is a separate issue and you'll need to look at the logs
to see if there is anything shown. Especially device-numbering
(your mmcblk2) is not guaranteed, so this could very well also be
mmcblk0 or mmcblk1


Thanks
Heiko

       reply	other threads:[~2018-02-19  6:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180218154359.9362-1-vicencb@gmail.com>
     [not found] ` <20180218154359.9362-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-19  6:01   ` Heiko Stuebner [this message]
2018-02-19 17:34     ` [PATCH] arm64: dts: rockchip: vdd_log is not an i2c slave Vicente Bergas

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=1705208.FSornk7tld@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.