linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: dillon min <dillon.minfei@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Mark Brown <broonie@kernel.org>, <p.zabel@pengutronix.de>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	Hua Dillon <dillonhua@gmail.com>
Subject: Re: [PATCH v2 2/3] ARM: dts: stm32: enable l3gd20 on stm32429-disco board
Date: Thu, 14 May 2020 17:14:22 +0200	[thread overview]
Message-ID: <f3af6148-7b22-303b-aa72-996d061a3c78@st.com> (raw)
In-Reply-To: <CAL9mu0KJ0j6Rxf7YjKxVWKz_d+B6vrwqqxJM-fmzG=NonLeDYQ@mail.gmail.com>



On 5/14/20 9:07 AM, dillon min wrote:
> Hi Alexandre,
> 
> Alexandre Torgue <alexandre.torgue@st.com> 于2020年5月14日周四 下午10:10写道:
>>
>> Hi Dillon
>>
>> On 5/12/20 9:36 AM, dillon.minfei@gmail.com wrote:
>>> From: dillon min <dillon.minfei@gmail.com>
>>>
>>> L3gd20, st mems motion sensor, 3-axis digital output gyroscope,
>>> connect to stm32f429 via spi5
>>>
>>> Signed-off-by: dillon min <dillon.minfei@gmail.com>
>>> ---
>>>
>>> Hi Alexandre,
>>>
>>> V2:
>>>       1, insert blank line at stm32f420-disco.dts line 143
>>>       2, add more description about l3gd20 in commit message
>>>
>>> V1:
>>>       enable l3gd20 dts binding on stm32f429-disco
>>>
>>> thanks.
>>>
>>> dillon,
>>>
>>>    arch/arm/boot/dts/stm32f429-disco.dts | 25 +++++++++++++++++++++++++
>>>    1 file changed, 25 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/stm32f429-disco.dts b/arch/arm/boot/dts/stm32f429-disco.dts
>>> index 30c0f67..1bfb903 100644
>>> --- a/arch/arm/boot/dts/stm32f429-disco.dts
>>> +++ b/arch/arm/boot/dts/stm32f429-disco.dts
>>> @@ -49,6 +49,8 @@
>>>    #include "stm32f429.dtsi"
>>>    #include "stm32f429-pinctrl.dtsi"
>>>    #include <dt-bindings/input/input.h>
>>> +#include <dt-bindings/interrupt-controller/irq.h>
>>> +#include <dt-bindings/gpio/gpio.h>
>>>
>>>    / {
>>>        model = "STMicroelectronics STM32F429i-DISCO board";
>>> @@ -127,3 +129,26 @@
>>>        pinctrl-names = "default";
>>>        status = "okay";
>>>    };
>>> +
>>> +&spi5 {
>>> +     status = "okay";
>>> +     pinctrl-0 = <&spi5_pins>;
>>> +     pinctrl-names = "default";
>>> +     #address-cells = <1>;
>>> +     #size-cells = <0>;
>>> +     cs-gpios = <&gpioc 1 GPIO_ACTIVE_LOW>;
>>> +     dmas = <&dma2 3 2 0x400 0x0>,
>>> +            <&dma2 4 2 0x400 0x0>;
>>> +     dma-names = "rx", "tx";
>>> +
>>
>> You added this spi5 node in this patch but also in the display series. I
>> will have issue to merge. Even if I could fix it easily, as you are
>> going to resend, the good practice could be to have several patches in
>> one series: one patch for spi5 controller, another for gyro and another
>> for display.
>>
>> And also same remark than Linus did in display series move DMA to soc
>> dtsi file please.
> 
> Sure, how about this patch sequence:
> 1 add spi5 dma to soc (stm32f429.dtsi)
> 2 add pin map for spi5 (stm32f4-pinctrl.dtsi)
> 3 add spi5 controller with gyro (stm32f429-disco.dts)
> 4 add spi modification to support gyro (spi-stm32.c)
> 
> 5 add ltdc pin map for stm32f429-disco board (stm32f4-pinctrl.dtsi)
> 6 add ilitek-ili9341 dts bindings for disco (stm32f429-disco.dts,
> depends on above step 3)
> 7 add yaml document about ilitek-ili9341 (ilitek,ili9341.yaml)
> 8 add clk changes to support ltdc driver (clk-stm32f4.c)
> 
> so, i will combine gyro and display two patches to one patchset next
> time. right ?
> 

looks good

> thanks.
>>
>>
>>> +     l3gd20: l3gd20@0 {
>>> +             compatible = "st,l3gd20-gyro";
>>> +             spi-max-frequency = <10000000>;
>>> +             st,drdy-int-pin = <2>;
>>> +             interrupt-parent = <&gpioa>;
>>> +             interrupts = <1 IRQ_TYPE_EDGE_RISING>,
>>> +                             <2 IRQ_TYPE_EDGE_RISING>;
>>> +             reg = <0>;
>>> +             status = "okay";
>>> +     };
>>> +};
>>>

  reply	other threads:[~2020-05-14 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  7:36 [PATCH v2 0/3] Enable l3gd20 on stm32f429-disco board dillon.minfei
2020-05-12  7:36 ` [PATCH v2 1/3] ARM: dts: stm32: Add pin map for spi5 " dillon.minfei
2020-05-12  7:36 ` [PATCH v2 2/3] ARM: dts: stm32: enable l3gd20 on stm32429-disco board dillon.minfei
2020-05-14 14:09   ` Alexandre Torgue
2020-05-14  7:07     ` dillon min
2020-05-14 15:14       ` Alexandre Torgue [this message]
2020-05-12  7:36 ` [PATCH v2 3/3] spi: stm32: Add SPI_SIMPLEX_RX, SPI_3WIRE_RX support for stm32f4 dillon.minfei

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=f3af6148-7b22-303b-aa72-996d061a3c78@st.com \
    --to=alexandre.torgue@st.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dillon.minfei@gmail.com \
    --cc=dillonhua@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).