[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <501852E6-6934-4BB2-850C-B53A07580568@goldelico.com>
Date: Mon, 9 May 2022 22:19:36 +0200
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Zhou Yanjie <zhouyanjie@...yeetech.com>
Cc: Paul Cercueil <paul@...pouillou.net>, jringle@...dpoint.com,
shc_work@...l.ru, Rob Herring <robh@...nel.org>,
Paul Boddie <paul@...die.org.uk>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
linux-serial@...r.kernel.org,
linux-mips <linux-mips@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Question about SC16IS752 device tree.
Hi,
> Am 09.05.2022 um 20:41 schrieb Zhou Yanjie <zhouyanjie@...yeetech.com>:
>
> Hi Paul,
>
> On 2022/5/10 上午2:13, Paul Cercueil wrote:
>> I can't say for sure that it's your problem, but your bluetooth nodes are missing "reg" properties.
>
>
> Unfortunately it doesn't seem to be the problem here, I added "reg" and
> the problem persists, and I've looked at other device trees that contain
> "brcm,bcm43438-bt", none of them use "reg", and "reg" is not mentioned in
> neither "Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt" nor
> "Documentation/devicetree/bindings/net/broadcom-bluetooth.yaml".
what happens if you remove the serdev children from DTS? Does the driver create two separate /dev/tty ports? And do they work?
Maybe the sc16is752 driver does not separate them for child nodes, i.e. while "reg" should be added it may not be handled?
BR,
Nikolaus
Powered by blists - more mailing lists