mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Jiucheng Xu <jiuchengxu@163.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: AML <linux-amlogic@lists.infradead.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Chris Healy <healych@amazon.com>, Will Deacon <will@kernel.org>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Pierre-Hugues Husson <phh@phh.me>,
	jiucheng.xu@amlogic.com
Subject: Re: Conflict between video-lut and pmu on meson-g12
Date: Wed, 1 Mar 2023 15:36:58 +0800	[thread overview]
Message-ID: <a0d7a363-a693-d114-c28a-2290dfa0f89f@163.com> (raw)
In-Reply-To: <CAFBinCBb_5KChqD6wqj_MFxEH_hxL_U3nnA=+1AR8dhdQQVCzw@mail.gmail.com>

+ jiuchengxu@163.com

Amlogic mail sending server has problem. Add my personal email.
Comments inline.

On 2023/3/1 5:49, Martin Blumenstingl wrote:
> [ EXTERNAL EMAIL ]
>
> Hello Jiucheng Xu,
>
> On Tue, Feb 28, 2023 at 10:04 PM Martin Blumenstingl
> <martin.blumenstingl@googlemail.com> wrote:
> [...]
>>> A simple solution might be to specify the "actual" base of
>>> the register set, and count from 0 in the driver?
>> I think your fix is correct (formally it would need to be split into a
>> driver and a .dtsi patch - but let's do things step by step).
> While thinking more about this - I think the whole .dtsi code should
> be improved. Both of the PMU IO regions are part of the &dmc region.
> So I think &pmu should be moved inside &dmc (with the offsets adjusted
> accordingly of course).
Okay I agree with you.I will put &pmu node into &dmc node.
>
> Also I think the dt-bindings are incomplete: according to the driver
> code we're using XTAL as input clock.
> But this is not described anywhere in the dt-bindings.
> dt-bindings should always describe the hardware. The driver can decide
> not to use it but the bindings must always be complete.
Sorry, I couldn't get your point. I didn't know the relationship between
XTAL and DMC. Would you please share more the information?
> And with this comes the question: is the DMC PLL specific to the PMU
> or is it shared with something else (e.g. the actual memory
> controller)? On the 32-bit SoCs (Meson8b/S805 for example) there's a
> whole DDR clock controller (used by the DDR memory controller), so I'm
> wondering if these newer SoCs are still following that approach.
Yes, the PLL is the base input clock of DMC and PMU inside. I have never
seen the meson8b board. I think G12 is a newer generation which has some 
improvement than old
SoCs.

My English is not well. Maybe I doesn't answer your point since I got 
miss-understanding.

Thanks & Best regards
Jiucheng
>
> Best regards,
> Martin
>


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2023-03-01  7:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 16:48 Marc Gonzalez
2023-02-28 21:04 ` Martin Blumenstingl
2023-02-28 21:49   ` Martin Blumenstingl
2023-03-01  7:36     ` Jiucheng Xu [this message]
2023-03-01 13:28     ` Marc Gonzalez
2023-03-09  9:48       ` Marc Gonzalez
2023-03-09 21:36         ` Martin Blumenstingl
2023-03-23 16:12           ` [PATCH] arm64: dts: meson-g12-common: specify full DMC range Marc Gonzalez
2023-03-23 16:23             ` [PATCH] perf/amlogic: resolve conflict between canvas & pmu Marc Gonzalez
2023-03-25 20:54               ` Martin Blumenstingl
2023-03-27  7:48                 ` Neil Armstrong
2023-03-25 20:43             ` [PATCH] arm64: dts: meson-g12-common: specify full DMC range Martin Blumenstingl

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=a0d7a363-a693-d114-c28a-2290dfa0f89f@163.com \
    --to=jiuchengxu@163.com \
    --cc=healych@amazon.com \
    --cc=jbrunet@baylibre.com \
    --cc=jiucheng.xu@amlogic.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=phh@phh.me \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®