linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>,
	chester62515@gmail.com, Matthias Brugger <mbrugger@suse.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>, dl-S32 <S32@nxp.com>
Subject: Re: s32 architecture upstream tree
Date: Mon, 24 Mar 2025 08:05:37 +0100	[thread overview]
Message-ID: <2da5156e-a793-4c97-a1f2-1d0daed2dc7d@linaro.org> (raw)
In-Reply-To: <7139ce39-c089-5932-4d99-93e9dcc7d321@oss.nxp.com>

On 24/03/2025 07:48, Ghennadi Procopciuc wrote:
> On 3/24/2025 8:43 AM, Daniel Lezcano wrote:
>> On 24/03/2025 07:27, Ghennadi Procopciuc wrote:
>>> On 3/22/2025 1:39 PM, Daniel Lezcano wrote:
>>>>
>>>> Hi,
>>>>
>>>> the MAINTAINER file does not give the information about the location of
>>>> the repository for the s32.
>>>>
>>>> Where is the repo to base the work on ? Especially the device tree
>>>>
>>>> Thanks in advance
>>>>
>>>>     -- Daniel
>>>>
>>>>
>>>
>>> Hi Daniel,
>>>
>>> Shawn Guo's tree should be used for the device tree patches. Please
>>> refer to the 'ARM/FREESCALE IMX / MXC ARM ARCHITECTURE' entry in the
>>> MAINTAINERS file.
>>
>> Thanks for the pointer.
>>
>> I don't see the SCMI clock bindings. Who is taking care of that ?
>>
>>
> 
> Hi,
> 
> If you're referring to a header in 'include/dt-bindings', it does not
> exist. The feedback was to use raw numbers [0], making the header
> unnecessary.

Great, even simpler !


-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


      reply	other threads:[~2025-03-24  7:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 11:39 s32 architecture upstream tree Daniel Lezcano
2025-03-24  6:27 ` Ghennadi Procopciuc
2025-03-24  6:43   ` Daniel Lezcano
2025-03-24  6:48     ` Ghennadi Procopciuc
2025-03-24  7:05       ` Daniel Lezcano [this message]

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=2da5156e-a793-4c97-a1f2-1d0daed2dc7d@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=S32@nxp.com \
    --cc=chester62515@gmail.com \
    --cc=ghennadi.procopciuc@oss.nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mbrugger@suse.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;
as well as URLs for NNTP newsgroup(s).