All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-unisoc@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interrupt-controller: Convert rda,8810pl-intc to YAML
Date: Mon, 6 Jun 2022 09:39:45 +0530	[thread overview]
Message-ID: <20220606040945.GA21449@thinkpad> (raw)
In-Reply-To: <20220603121258.GA4919@standask-GA-A55M-S2HP>

On Fri, Jun 03, 2022 at 02:12:58PM +0200, Stanislav Jakubek wrote:
> On Sun, May 29, 2022 at 04:05:12PM +0200, Krzysztof Kozlowski wrote:
> > On 27/05/2022 14:56, Stanislav Jakubek wrote:
> > > Convert RDA Micro interrupt controller bindings to DT schema format.
> > > 
> > > Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
> > > ---
> > > 
> > > Didn't know what to do about the interrupt sources listed in the original txt file,
> > > so I've split them off into a separate file. Hope that's okay.
> > 
> > Interrupt sources are not kept in header files.
> 
> Ok, should I move them somewhere else or is it fine to drop them?
> 
> > Additionally are you
> > sure this is a property of the interrupt controller, not a property of
> > SoC itself? I would assume that one interrupt controller implementation
> > (e.g. GIC) can be used in different SoCs and the sources are every time
> > different because they depend on the actual wiring...
> > 
> 
> I honestly have no idea, I just wanted to make some YAML conversions.
> Maybe Mani could answer this?
> 

You can drop them. I didn't include it in a header file because it could vary
between SoCs. So added here for documenting purposes.

Thanks,
Mani

> > 
> > Best regards,
> > Krzysztof
> 
> 
> Thanks,
> Stanislav

-- 
மணிவண்ணன் சதாசிவம்

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

WARNING: multiple messages have this Message-ID (diff)
From: Manivannan Sadhasivam <mani@kernel.org>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-unisoc@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interrupt-controller: Convert rda,8810pl-intc to YAML
Date: Mon, 6 Jun 2022 09:39:45 +0530	[thread overview]
Message-ID: <20220606040945.GA21449@thinkpad> (raw)
In-Reply-To: <20220603121258.GA4919@standask-GA-A55M-S2HP>

On Fri, Jun 03, 2022 at 02:12:58PM +0200, Stanislav Jakubek wrote:
> On Sun, May 29, 2022 at 04:05:12PM +0200, Krzysztof Kozlowski wrote:
> > On 27/05/2022 14:56, Stanislav Jakubek wrote:
> > > Convert RDA Micro interrupt controller bindings to DT schema format.
> > > 
> > > Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
> > > ---
> > > 
> > > Didn't know what to do about the interrupt sources listed in the original txt file,
> > > so I've split them off into a separate file. Hope that's okay.
> > 
> > Interrupt sources are not kept in header files.
> 
> Ok, should I move them somewhere else or is it fine to drop them?
> 
> > Additionally are you
> > sure this is a property of the interrupt controller, not a property of
> > SoC itself? I would assume that one interrupt controller implementation
> > (e.g. GIC) can be used in different SoCs and the sources are every time
> > different because they depend on the actual wiring...
> > 
> 
> I honestly have no idea, I just wanted to make some YAML conversions.
> Maybe Mani could answer this?
> 

You can drop them. I didn't include it in a header file because it could vary
between SoCs. So added here for documenting purposes.

Thanks,
Mani

> > 
> > Best regards,
> > Krzysztof
> 
> 
> Thanks,
> Stanislav

-- 
மணிவண்ணன் சதாசிவம்

  parent reply	other threads:[~2022-06-06  4:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 12:56 [PATCH] dt-bindings: interrupt-controller: Convert rda,8810pl-intc to YAML Stanislav Jakubek
2022-05-27 12:56 ` Stanislav Jakubek
2022-05-29 14:05 ` Krzysztof Kozlowski
2022-05-29 14:05   ` Krzysztof Kozlowski
2022-06-03 12:12   ` Stanislav Jakubek
2022-06-03 12:12     ` Stanislav Jakubek
2022-06-05 14:50     ` Krzysztof Kozlowski
2022-06-05 14:50       ` Krzysztof Kozlowski
2022-06-06  4:09     ` Manivannan Sadhasivam [this message]
2022-06-06  4:09       ` Manivannan Sadhasivam

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=20220606040945.GA21449@thinkpad \
    --to=mani@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unisoc@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stano.jakubek@gmail.com \
    --cc=tglx@linutronix.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.