All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Joel Stanley <joel@jms.id.au>, openbmc@lists.ozlabs.org
Subject: Re: [PATCH v2 linux dev-5.3 3/4] ARM: dts: aspeed-g6: Add lpc devices
Date: Tue, 24 Sep 2019 15:51:05 -0400	[thread overview]
Message-ID: <9540FAF9-C027-4455-80C2-D48113D3BFF8@fuzziesquirrel.com> (raw)
In-Reply-To: <9196f950-59ea-4e7f-82f7-29769e0a2c81@www.fastmail.com>

at 2:37 AM, Andrew Jeffery <andrew@aj.id.au> wrote:

>
>
> On Fri, 20 Sep 2019, at 00:53, Brad Bishop wrote:
>> Assume everything is the same as G5, except the interrupt is updated.
>>
>> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
>> ---
>>  arch/arm/boot/dts/aspeed-g6.dtsi | 91 ++++++++++++++++++++++++++++++++
>>  1 file changed, 91 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/aspeed-g6.dtsi  
>> b/arch/arm/boot/dts/aspeed-g6.dtsi
>> index 72038c16f541..b4991cbe1f36 100644
>> --- a/arch/arm/boot/dts/aspeed-g6.dtsi
>> +++ b/arch/arm/boot/dts/aspeed-g6.dtsi
>> @@ -249,6 +249,97 @@
>>  				status = "disabled";
>>  			};
>>
>> +			lpc: lpc@1e789000 {
>> +				compatible = "aspeed,ast2600-lpc", "simple-mfd";
>> +				reg = <0x1e789000 0x1000>;
>> +
>> +				#address-cells = <1>;
>> +				#size-cells = <1>;
>> +				ranges = <0x0 0x1e789000 0x1000>;
>> +
>> +				lpc_bmc: lpc-bmc@0 {
>> +					compatible = "aspeed,ast2600-lpc-bmc", "simple-mfd", "syscon";
>> +					reg = <0x0 0x80>;
>> +					reg-io-width = <4>;
>> +
>> +					#address-cells = <1>;
>> +					#size-cells = <1>;
>> +					ranges = <0x0 0x0 0x80>;
>> +
>> +					kcs1: kcs1@0 {
>> +						compatible = "aspeed,ast2600-kcs-bmc";
>> +						interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH>;
>> +						kcs_chan = <1>;
>> +						status = "disabled";
>> +					};
>> +					kcs2: kcs2@0 {
>> +						compatible = "aspeed,ast2600-kcs-bmc";
>> +						interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH>;
>> +						kcs_chan = <2>;
>> +						status = "disabled";
>> +					};
>> +					kcs3: kcs3@0 {
>> +						compatible = "aspeed,ast2600-kcs-bmc";
>> +						interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH>;
>> +						kcs_chan = <3>;
>> +						status = "disabled";
>> +					};
>> +				};
>> +
>> +				lpc_host: lpc-host@80 {
>> +					compatible = "aspeed,ast2600-lpc-host", "simple-mfd", "syscon";
>> +					reg = <0x80 0x1e0>;
>> +					reg-io-width = <4>;
>> +
>> +					#address-cells = <1>;
>> +					#size-cells = <1>;
>> +					ranges = <0x0 0x80 0x1e0>;
>> +
>> +					kcs4: kcs4@0 {
>> +						compatible = "aspeed,ast2600-kcs-bmc";
>> +						interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH>;
>> +						kcs_chan = <4>;
>> +						status = "disabled";
>> +					};
>
> I've got some patches floating around that I need to respin that adjust  
> the kcs binding.
> The new dtsi with the existing binding means we're going to increase the  
> amplification
> of dtc warnings :(
>
>> +
>> +					lpc_ctrl: lpc-ctrl@0 {
>> +						compatible = "aspeed,ast2600-lpc-ctrl";
>> +						reg = <0x0 0x80>;
>> +						clocks = <&syscon ASPEED_CLK_GATE_LCLK>;
>> +						status = "disabled";
>> +					};
>> +
>> +					lpc_snoop: lpc-snoop@0 {
>> +						compatible = "aspeed,ast2600-lpc-snoop";
>> +						reg = <0x0 0x80>;
>> +						interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH>;
>> +						status = "disabled";
>> +					};
>> +
>> +					lhc: lhc@20 {
>> +						compatible = "aspeed,ast2600-lhc";
>> +						reg = <0x20 0x24 0x48 0x8>;
>> +					};
>> +
>> +					lpc_reset: reset-controller@18 {
>> +						compatible = "aspeed,ast2600-lpc-reset";
>> +						reg = <0x18 0x4>;
>> +						#reset-cells = <1>;
>> +					};
>> +
>> +					ibt: ibt@c0 {
>> +						compatible = "aspeed,ast2600-ibt-bmc";
>> +						reg = <0xc0 0x18>;
>> +						interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH>;
>> +						status = "disabled";
>> +					};
>> +
>> +					sio_regs: regs {
>> +						compatible = "aspeed,bmc-misc";
>> +					};
>
> Can you please split the sio_regs one out to a separate patch?

Split in v3.

> The necessary patches got nak'ed upstream a while back and I haven't  
> circled back around
> to implement something more palatable. Put the patch adding it at the top  
> of
> your series, then you can send the earlier ones upstream.
>
> Andrew

  reply	other threads:[~2019-09-24 19:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 15:23 [PATCH v2 linux dev-5.3 0/5] ARM: dts: aspeed-g6 lpc, rainier Brad Bishop
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 1/4] dt-bindings: lpc: add aspeed-g6 compatible strings Brad Bishop
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 2/4] ARM: aspeed-g6: lpc: add " Brad Bishop
2019-09-20  6:31   ` Andrew Jeffery
2019-09-24 19:50     ` Brad Bishop
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 3/4] ARM: dts: aspeed-g6: Add lpc devices Brad Bishop
2019-09-20  6:37   ` Andrew Jeffery
2019-09-24 19:51     ` Brad Bishop [this message]
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 4/4] ARM: dts: aspeed: add Rainier system Brad Bishop
2019-09-20  7:25   ` Andrew Jeffery
2019-09-24 19:53     ` Brad Bishop
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 0/5] ARM: dts: aspeed-g6 lpc, rainier Brad Bishop
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 1/4] dt-bindings: lpc: add aspeed-g6 compatible strings Brad Bishop
2019-09-19 16:25   ` Eddie James
2019-09-20  6:30     ` Andrew Jeffery
2019-09-24 19:49       ` Brad Bishop
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 2/4] ARM: aspeed-g6: lpc: add " Brad Bishop
2019-09-19 16:26   ` Eddie James
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 3/4] ARM: dts: aspeed-g6: Add lpc devices Brad Bishop
2019-09-19 16:29   ` Eddie James
2019-09-20  8:04   ` Andrew Jeffery
2019-09-19 15:23 ` [PATCH v2 linux dev-5.3 4/4] ARM: dts: aspeed: add Rainier system Brad Bishop
2019-09-19 16:31   ` Eddie James
2019-09-19 15:32 ` [PATCH v2 linux dev-5.3 0/5] ARM: dts: aspeed-g6 lpc, rainier Brad Bishop

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=9540FAF9-C027-4455-80C2-D48113D3BFF8@fuzziesquirrel.com \
    --to=bradleyb@fuzziesquirrel.com \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.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.