From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jammy Huang <jammy_huang@aspeedtech.com>,
robh@kernel.org, conor+dt@kernel.org, eajames@linux.ibm.com,
mchehab@kernel.org, joel@jms.id.au, andrew@aj.id.au,
hverkuil@xs4all.nl, pmenzel@molgen.mpg.de, krzk+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-media@vger.kernel.org,
openbmc@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] media: aspeed: Allow to capture from SoC display (GFX)
Date: Thu, 29 Aug 2024 09:56:18 +0200 [thread overview]
Message-ID: <51d48faf-9f62-431f-b1bf-b78f0a30ae14@kernel.org> (raw)
In-Reply-To: <20240829064508.3706672-3-jammy_huang@aspeedtech.com>
On 29/08/2024 08:45, Jammy Huang wrote:
> ASPEED BMC IC has 2 different display engines. Please find AST2600's
> datasheet to get detailed information.
>
...
>
> +/*
> + * Get regmap without checking res, such as clk/reset, that could lead to
> + * conflict.
> + */
> +static struct regmap *aspeed_regmap_lookup(struct device_node *np, const char *property)
> +{
> + struct device_node *syscon_np __free(device_node) = of_parse_phandle(np, property, 0);
> +
> + if (!syscon_np)
> + return ERR_PTR(-ENODEV);
> +
> + return device_node_to_regmap(syscon_np);
> +}
> +
> static int aspeed_video_init(struct aspeed_video *video)
> {
> int irq;
> int rc;
> struct device *dev = video->dev;
>
> + video->scu = aspeed_regmap_lookup(dev->of_node, "aspeed,scu");
> + video->gfx = aspeed_regmap_lookup(dev->of_node, "aspeed,gfx");
So that's a new property? Not related to conversion? Then split the
patches. Conversion is one logical change. Adding properties for new
hardware is completely different.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-08-29 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 6:45 [PATCH v6 0/2] " Jammy Huang
2024-08-29 6:45 ` [PATCH v6 1/2] dt-bindings: media: convert aspeed-video.txt to dt-schema Jammy Huang
2024-08-29 7:55 ` Krzysztof Kozlowski
2024-09-02 1:44 ` Jammy Huang
2024-09-02 6:57 ` Krzysztof Kozlowski
2024-08-29 8:23 ` Rob Herring (Arm)
2024-09-02 0:43 ` Jammy Huang
2024-08-30 0:21 ` kernel test robot
2024-08-29 6:45 ` [PATCH v6 2/2] media: aspeed: Allow to capture from SoC display (GFX) Jammy Huang
2024-08-29 7:56 ` Krzysztof Kozlowski [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=51d48faf-9f62-431f-b1bf-b78f0a30ae14@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=hverkuil@xs4all.nl \
--cc=jammy_huang@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robh@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
all inboxes | Powered by JetHome®