Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Dominik Haller <D.Haller@phytec.de>
To: "tony@atomide.com" <tony@atomide.com>,
	Steffen Hemer <S.Hemer@phytec.de>,
	"khilman@baylibre.com" <khilman@baylibre.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: PHYTEC Upstream <upstream@lists.phytec.de>
Subject: Re: [PATCH 1/2] ARM: dts: ti: omap: am335x-regor: Fix RS485 settings
Date: Tue, 30 Jul 2024 09:07:28 +0000	[thread overview]
Message-ID: <25ebcbe75bc395c53d4756f3b8eff2c0c7ee3d3e.camel@phytec.de> (raw)
In-Reply-To: <7hbk2g3qhe.fsf@baylibre.com>

On Mon, 2024-07-29 at 13:14 -0700, Kevin Hilman wrote:
> Dominik Haller <d.haller@phytec.de> writes:
> 
> > From: Steffen Hemer <s.hemer@phytec.de>
> > 
> > RTS pin seems to have inverted behavior on am335x, other than
> > expected
> > with default "rs485-rts-active-high" (instead of low on idle, high
> > on send,
> > it is the opposite). Transceiver datasheet also suggests a
> > pulldown.
> > Add includes to pin definitions that are used.
> > 
> > Signed-off-by: Steffen Hemer <s.hemer@phytec.de>
> 
> Series LGTM, but as the sender, we need your Signed-off-by here too.
> See the docs on submitting patches for all the details[1].
> 
> Kevin

Sure, I'll add it in a v2.

Thanks

Dominik
> 
> [1]  
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin

      reply	other threads:[~2024-07-30  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 14:19 [PATCH 1/2] ARM: dts: ti: omap: am335x-regor: Fix RS485 settings Dominik Haller
2024-07-25 14:19 ` [PATCH 2/2] ARM: dts: ti: omap: am335x-wega: Fix audio clock provider Dominik Haller
2024-07-29 20:14 ` [PATCH 1/2] ARM: dts: ti: omap: am335x-regor: Fix RS485 settings Kevin Hilman
2024-07-30  9:07   ` Dominik Haller [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=25ebcbe75bc395c53d4756f3b8eff2c0c7ee3d3e.camel@phytec.de \
    --to=d.haller@phytec.de \
    --cc=S.Hemer@phytec.de \
    --cc=khilman@baylibre.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=upstream@lists.phytec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox