From: Guenter Roeck <linux@roeck-us.net>
To: linux-aspeed@lists.ozlabs.org
Subject: [v6 2/4] dt-bindings: hwmon: Add ASPEED TACH Control documentation
Date: Mon, 17 Jul 2023 23:45:36 -0700 [thread overview]
Message-ID: <28de46d5-bf6a-da0c-ad24-5404ad416b3a@roeck-us.net> (raw)
In-Reply-To: <3756dffd-1407-d656-485a-9cf1eefd9ae1@linaro.org>
On 7/17/23 23:04, Krzysztof Kozlowski wrote:
[ ... ]
>> The first method involves passing the memory region from an MFD
>> driver, which was the
>
> I have no clue how can you pass memory region
> (Documentation/devicetree/bindings/reserved-memory/) from MFD and why
> does it make sense here.
>
It is quite common for mfd drivers to pass regmap information to
child drivers. Child drivers typically call dev_get_regmap() with
the parent device as parameter. Granted, that is typically used
for spi or i2c devices, but I don't see why it would not work
here as well.
Then there s syscon, but I don't know if that works with overlapping
memory regions.
Guenter
next prev parent reply other threads:[~2023-07-18 6:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 7:04 [v6 2/4] dt-bindings: hwmon: Add ASPEED TACH Control documentation 蔡承達
2023-07-14 7:13 ` Krzysztof Kozlowski
2023-07-14 9:59 ` Guenter Roeck
2023-07-14 10:18 ` 蔡承達
2023-07-14 10:26 ` Guenter Roeck
2023-07-14 11:17 ` 蔡承達
2023-07-16 16:08 ` Krzysztof Kozlowski
2023-07-16 17:00 ` Guenter Roeck
2023-07-17 9:01 ` 蔡承達
2023-07-17 9:39 ` Krzysztof Kozlowski
2023-07-18 4:01 ` 蔡承達
2023-07-18 6:04 ` Krzysztof Kozlowski
2023-07-18 6:39 ` Thierry Reding
2023-07-18 6:54 ` Guenter Roeck
2023-07-18 7:14 ` Thierry Reding
2023-08-15 6:32 ` 蔡承達
2023-07-18 6:45 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-08 2:18 [v6 0/4] Support pwm/tach driver for aspeed ast26xx Billy Tsai
2023-06-08 2:18 ` [v6 2/4] dt-bindings: hwmon: Add ASPEED TACH Control documentation Billy Tsai
2023-06-08 4:58 ` Guenter Roeck
2023-06-08 6:21 ` Billy Tsai
2023-06-08 13:18 ` Guenter Roeck
2023-06-28 5:30 ` Billy Tsai
2023-06-08 6:40 ` Krzysztof Kozlowski
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=28de46d5-bf6a-da0c-ad24-5404ad416b3a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-aspeed@lists.ozlabs.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