From: Sui Jingfeng <15330273260@189.cn>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Roland Scheidegger <sroland@vmware.com>,
Zack Rusin <zackr@vmware.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Dan Carpenter <dan.carpenter@oracle.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>,
Sam Ravnborg <sam@ravnborg.org>,
"David S . Miller" <davem@davemloft.net>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Lucas Stach <l.stach@pengutronix.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Ilia Mirkin <imirkin@alum.mit.edu>,
Qing Zhang <zhangqing@loongson.cn>,
suijingfeng <suijingfeng@loongson.cn>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
Randy Dunlap <rdunlap@infradead.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v10 3/4] drm/lsdc: add drm driver for loongson display controller
Date: Wed, 23 Feb 2022 23:14:12 +0800 [thread overview]
Message-ID: <0d4a75c4-78bb-4aed-0fa8-88e9cc165896@189.cn> (raw)
In-Reply-To: <20220223143912.m727fie3vtdkvklo@houat>
On 2022/2/23 22:39, Maxime Ripard wrote:
> On Tue, Feb 22, 2022 at 10:46:35PM +0800, Sui Jingfeng wrote:
>> On 2022/2/22 16:27, Maxime Ripard wrote:
>>>> + if (!of_device_is_available(output)) {
>>>> + of_node_put(output);
>>>> + drm_info(ddev, "connector%d is not available\n", index);
>>>> + return NULL;
>>>> + }
>>>> +
>>>> + disp_tims_np = of_get_child_by_name(output, "display-timings");
>>>> + if (disp_tims_np) {
>>>> + lsdc_get_display_timings_from_dtb(output, &lconn->disp_tim);
>>>> + lconn->has_disp_tim = true;
>>>> + of_node_put(disp_tims_np);
>>>> + drm_info(ddev, "Found display timings provided by connector%d\n", index);
>>>> + }
>>>> +
>>>> + connector_type = lsdc_get_connector_type(ddev, output, index);
>>>> +
>>>> + if (output) {
>>>> + of_node_put(output);
>>>> + output = NULL;
>>>> + }
>>>> +
>>>> +DT_SKIPED:
>>>> +
>>>> + /* Only create the i2c channel if display timing is not provided */
>>>> + if (!lconn->has_disp_tim) {
>>>> + const struct lsdc_chip_desc * const desc = ldev->desc;
>>>> +
>>>> + if (desc->have_builtin_i2c)
>>>> + lconn->ddc = lsdc_create_i2c_chan(ddev, index);
>>>> + else
>>>> + lconn->ddc = lsdc_get_i2c_adapter(ddev, index);
>>> This looks weird: the connector bindings have a property to store the
>>> i2c controller connected to the DDC lines, so you should use that
>>> instead.
>>>
>> This is not weird, ast, mgag200, hibmc do the same thing.
> And none of them have DT support.
>
> Maxime
You are wrong, ast driver have dt support. See ast_detect_config_mode()
in drm/ast/ast_main.c
static void ast_detect_config_mode(struct drm_device *dev, u32 *scu_rev)
{
struct device_node *np = dev->dev->of_node;
struct ast_private *ast = to_ast_private(dev);
struct pci_dev *pdev = to_pci_dev(dev->dev);
uint32_t data, jregd0, jregd1;
/* Defaults */
ast->config_mode = ast_use_defaults;
*scu_rev = 0xffffffff;
/* Check if we have device-tree properties */
if (np && !of_property_read_u32(np, "aspeed,scu-revision-id",
scu_rev)) {
/* We do, disable P2A access */
ast->config_mode = ast_use_dt;
drm_info(dev, "Using device-tree for configuration\n");
return;
}
....
}
next prev parent reply other threads:[~2022-02-23 15:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 14:55 [PATCH v10 0/4] " Sui Jingfeng
2022-02-20 14:55 ` [PATCH v10 1/4] MIPS: Loongson64: dts: update the display controller device node Sui Jingfeng
2022-02-20 18:18 ` Jiaxun Yang
2022-02-21 1:27 ` Sui Jingfeng
2022-02-21 9:19 ` Sergei Shtylyov
2022-02-21 10:01 ` Krzysztof Kozlowski
2022-02-21 13:57 ` Sui Jingfeng
2022-02-21 13:53 ` Sui Jingfeng
2022-02-20 14:55 ` [PATCH v10 2/4] Documentation/dt: Add descriptions for loongson display controller Sui Jingfeng
2022-02-20 18:22 ` Jiaxun Yang
2022-02-21 7:31 ` Krzysztof Kozlowski
2022-02-22 23:02 ` Rob Herring
2022-02-23 13:56 ` 隋景峰
2022-02-23 15:35 ` Sui Jingfeng
2022-02-23 15:44 ` Krzysztof Kozlowski
2022-02-23 15:40 ` Krzysztof Kozlowski
2022-02-20 14:55 ` [PATCH v10 3/4] drm/lsdc: add drm driver " Sui Jingfeng
2022-02-22 8:27 ` Maxime Ripard
2022-02-22 13:53 ` Sui Jingfeng
2022-02-22 14:46 ` Sui Jingfeng
2022-02-23 14:39 ` Maxime Ripard
2022-02-23 15:14 ` Sui Jingfeng [this message]
2022-02-23 15:41 ` Maxime Ripard
2022-02-23 15:45 ` Sui Jingfeng
2022-02-23 12:47 ` kernel test robot
2022-02-20 14:55 ` [PATCH v10 4/4] MAINTAINERS: add maintainers for DRM LSDC driver Sui Jingfeng
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=0d4a75c4-78bb-4aed-0fa8-88e9cc165896@189.cn \
--to=15330273260@189.cn \
--cc=airlied@linux.ie \
--cc=andrey.zhizhikin@leica-geosystems.com \
--cc=christian.gmeiner@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=jiaxun.yang@flygoat.com \
--cc=krzk@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime@cerno.tech \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sroland@vmware.com \
--cc=suijingfeng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.com \
--cc=zhangqing@loongson.cn \
/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
all inboxes | Powered by JetHome®