All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tamseel Shams" <m.shams@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
	<alim.akhtar@samsung.com>, <linux-fsd@tesla.com>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<conor+dt@kernel.org>, <gregkh@linuxfoundation.org>,
	<jirislaby@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>
Subject: RE: [PATCH 2/2] arm64: dts: fsd: Add fifosize for UART in Device Tree
Date: Mon, 5 Feb 2024 13:42:49 +0530	[thread overview]
Message-ID: <0dc501da580b$1dde1870$599a4950$@samsung.com> (raw)
In-Reply-To: <6980c4d5-78a2-4c14-b21e-a5ed1e4d5675@linaro.org>



> -----Original Message-----
> From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org]
> Sent: 05 February 2024 13:11
> To: Tamseel Shams <m.shams@samsung.com>; alim.akhtar@samsung.com;
> linux-fsd@tesla.com; robh+dt@kernel.org;
> krzysztof.kozlowski+dt@linaro.org; conor+dt@kernel.org;
> gregkh@linuxfoundation.org; jirislaby@kernel.org
> Cc: linux-arm-kernel@lists.infradead.org; linux-samsung-
> soc@vger.kernel.org; devicetree@vger.kernel.org; linux-
> kernel@vger.kernel.org; linux-serial@vger.kernel.org
> Subject: Re: [PATCH 2/2] arm64: dts: fsd: Add fifosize for UART in Device Tree
> 
> On 02/02/2024 22:24, Tamseel Shams wrote:
> > UART in FSD SoC has fifosize of 64 bytes.
> > Set fifosize as 64 bytes for UART from Device Tree.
> >
> > Signed-off-by: Tamseel Shams <m.shams@samsung.com>
> > ---
> >  arch/arm64/boot/dts/tesla/fsd.dtsi | 2 ++
> 
> Please split SoC changes from patches sent to serial, so it will be easy to apply
> for Greg and others.
> 
> Unless you want to say that there is dependency, but there cannot be such -
> it would be a NAK.
> 
Thanks for review. Will take care of this the next version.

Thanks & Regards,
Tamseel Shams


WARNING: multiple messages have this Message-ID (diff)
From: "Tamseel Shams" <m.shams@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
	<alim.akhtar@samsung.com>, <linux-fsd@tesla.com>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<conor+dt@kernel.org>, <gregkh@linuxfoundation.org>,
	<jirislaby@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>
Subject: RE: [PATCH 2/2] arm64: dts: fsd: Add fifosize for UART in Device Tree
Date: Mon, 5 Feb 2024 13:42:49 +0530	[thread overview]
Message-ID: <0dc501da580b$1dde1870$599a4950$@samsung.com> (raw)
In-Reply-To: <6980c4d5-78a2-4c14-b21e-a5ed1e4d5675@linaro.org>



> -----Original Message-----
> From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org]
> Sent: 05 February 2024 13:11
> To: Tamseel Shams <m.shams@samsung.com>; alim.akhtar@samsung.com;
> linux-fsd@tesla.com; robh+dt@kernel.org;
> krzysztof.kozlowski+dt@linaro.org; conor+dt@kernel.org;
> gregkh@linuxfoundation.org; jirislaby@kernel.org
> Cc: linux-arm-kernel@lists.infradead.org; linux-samsung-
> soc@vger.kernel.org; devicetree@vger.kernel.org; linux-
> kernel@vger.kernel.org; linux-serial@vger.kernel.org
> Subject: Re: [PATCH 2/2] arm64: dts: fsd: Add fifosize for UART in Device Tree
> 
> On 02/02/2024 22:24, Tamseel Shams wrote:
> > UART in FSD SoC has fifosize of 64 bytes.
> > Set fifosize as 64 bytes for UART from Device Tree.
> >
> > Signed-off-by: Tamseel Shams <m.shams@samsung.com>
> > ---
> >  arch/arm64/boot/dts/tesla/fsd.dtsi | 2 ++
> 
> Please split SoC changes from patches sent to serial, so it will be easy to apply
> for Greg and others.
> 
> Unless you want to say that there is dependency, but there cannot be such -
> it would be a NAK.
> 
Thanks for review. Will take care of this the next version.

Thanks & Regards,
Tamseel Shams


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

  reply	other threads:[~2024-02-05 10:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240202212456epcas5p15589813cd79526e9d0c444082e2f0e51@epcas5p1.samsung.com>
2024-02-02 21:24 ` [PATCH 1/2] serial: samsung: honor fifosize from dts at first Tamseel Shams
2024-02-02 21:24   ` Tamseel Shams
2024-02-02 21:24   ` [PATCH 2/2] arm64: dts: fsd: Add fifosize for UART in Device Tree Tamseel Shams
2024-02-02 21:24     ` Tamseel Shams
2024-02-05  7:41     ` Krzysztof Kozlowski
2024-02-05  7:41       ` Krzysztof Kozlowski
2024-02-05  8:12       ` Tamseel Shams [this message]
2024-02-05  8:12         ` Tamseel Shams
2024-02-05  7:40   ` [PATCH 1/2] serial: samsung: honor fifosize from dts at first Krzysztof Kozlowski
2024-02-05  7:40     ` Krzysztof Kozlowski
2024-02-05  8:11     ` Tamseel Shams
2024-02-05  8:11       ` Tamseel Shams

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='0dc501da580b$1dde1870$599a4950$@samsung.com' \
    --to=m.shams@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fsd@tesla.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --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 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.