| /kernel/linux/linux-5.10/drivers/pinctrl/intel/ |
| D | pinctrl-intel.c | 94 struct intel_community *community; in intel_get_community() local
98 community = &pctrl->communities[i]; in intel_get_community()
99 if (pin >= community->pin_base && in intel_get_community()
100 pin < community->pin_base + community->npins) in intel_get_community()
101 return community; in intel_get_community()
104 dev_warn(pctrl->dev, "failed to find community for pin %u\n", pin); in intel_get_community()
109 intel_community_get_padgroup(const struct intel_community *community, in intel_community_get_padgroup() argument
114 for (i = 0; i < community->ngpps; i++) { in intel_community_get_padgroup()
115 const struct intel_padgroup *padgrp = &community->gpps[i]; in intel_community_get_padgroup()
127 const struct intel_community *community; in intel_get_padcfg() local
[all …]
|
| D | pinctrl-intel.h | 62 * If pad groups of a community are not the same size, use this structure
87 * struct intel_community - Intel pin community description
88 * @barno: MMIO BAR number where registers for this community reside
99 * @pin_base: Starting pin of pins in this community
100 * @npins: Number of pins in this community
107 * @ngpps: Number of pad groups in this community
109 * @nirqs: Optional total number of IRQs this community can generate
111 * @regs: Community specific common registers (reserved for core driver)
112 * @pad_regs: Community specific pad registers (reserved for core driver)
208 * @communities: Opaque context per community (driver dependent)
|
| D | pinctrl-cherryview.c | 77 * struct intel_community_context - community context for Cherryview
266 * Southwest community can generate GPIO interrupts only for the first 8
360 * North community can generate GPIO interrupts only for the first 8
569 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_readl() local
571 return readl(community->regs + offset); in chv_pctrl_readl()
576 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_writel() local
577 void __iomem *reg = community->regs + offset; in chv_pctrl_writel()
587 const struct intel_community *community = &pctrl->communities[0]; in chv_padreg() local
593 return community->pad_regs + offset + reg; in chv_padreg()
1403 const struct intel_community *community = &pctrl->communities[0]; in chv_gpio_irq_handler() local
[all …]
|
| /kernel/linux/linux-6.6/drivers/pinctrl/intel/ |
| D | pinctrl-intel.c | 112 struct intel_community *community; in intel_get_community() local
116 community = &pctrl->communities[i]; in intel_get_community()
117 if (pin >= community->pin_base && in intel_get_community()
118 pin < community->pin_base + community->npins) in intel_get_community()
119 return community; in intel_get_community()
122 dev_warn(pctrl->dev, "failed to find community for pin %u\n", pin); in intel_get_community()
128 intel_community_get_padgroup(const struct intel_community *community, in intel_community_get_padgroup() argument
133 for (i = 0; i < community->ngpps; i++) { in intel_community_get_padgroup()
134 const struct intel_padgroup *padgrp = &community->gpps[i]; in intel_community_get_padgroup()
146 const struct intel_community *community; in intel_get_padcfg() local
[all …]
|
| D | pinctrl-intel.h | 55 * If pad groups of a community are not the same size, use this structure
80 * struct intel_community - Intel pin community description
81 * @barno: MMIO BAR number where registers for this community reside
92 * @pin_base: Starting pin of pins in this community
93 * @npins: Number of pins in this community
99 * @ngpps: Number of pad groups in this community
101 * @nirqs: Optional total number of IRQs this community can generate
103 * @regs: Community specific common registers (reserved for core driver)
104 * @pad_regs: Community specific pad registers (reserved for core driver)
222 * @communities: Opaque context per community (driver dependent)
|
| D | pinctrl-cherryview.c | 81 * struct intel_community_context - community context for Cherryview
270 * Southwest community can generate GPIO interrupts only for the first 8
364 * North community can generate GPIO interrupts only for the first 8
573 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_readl() local
575 return readl(community->regs + offset); in chv_pctrl_readl()
580 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_writel() local
581 void __iomem *reg = community->regs + offset; in chv_pctrl_writel()
591 const struct intel_community *community = &pctrl->communities[0]; in chv_padreg() local
597 return community->pad_regs + offset + reg; in chv_padreg()
1303 const struct intel_community *community = &pctrl->communities[0]; in chv_gpio_set_intr_line() local
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | researcher-guidelines.rst | 8 The Linux kernel community welcomes transparent research on the Linux
13 The community greatly appreciates if researchers can share preliminary
17 sharing open access copies of the published research with the community
20 This document seeks to clarify what the Linux kernel community considers
31 The Linux kernel community expects that everyone interacting with the
34 code) produced by the Linux kernel community is welcome, though research
51 contributors. As a general rule, though, the kernel community derives
56 themselves or to the kernel community as a whole. For this reason, this
59 Kernel community members already receive far too much email and are likely
61 such requests deprives the community of valuable contributor time and is
[all …]
|
| D | code-of-conduct-interpretation.rst | 7 provide a set of rules for almost any open source community. Every
8 open-source community is unique and the Linux kernel is no exception.
10 community will interpret it. We also do not expect this interpretation
28 kernel community, a "maintainer" is anyone who is responsible for a
41 That being said, our community is vast and broad, and there is no new
43 behave in the parts of the community where they are active. That
49 others in the community when needed. Do not be afraid to reach out to
83 the Code of Conduct. The kernel community is aware of that and provides
89 The Linux kernel community primarily interacts on a set of public email
98 Conduct. The Linux kernel community does not have an "official" project
[all …]
|
| D | code-of-conduct.rst | 11 our community a harassment-free experience for everyone, regardless of age, body
25 * Focusing on what is best for the community
26 * Showing empathy towards other community members
58 when an individual is representing the project or its community. Examples of
59 representing a project or community include using an official project e-mail
86 kernel community will be interpreting this document.
|
| D | 1.Intro.rst | 13 availability to users, community support in many forms, and the ability to
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
81 Working with the kernel development community is not especially hard. But,
83 difficulties when trying to do kernel work. The kernel community has
93 community's ways (or, worse, who tries to flout or circumvent them) will
94 have a frustrating experience in store. The development community, while
101 community is always in need of developers who will help to make the kernel
103 join our community.
121 learning how to work with the kernel community and get their code into the
[all …]
|
| D | contribution-maturity-model.rst | 15 part of the Linux Kernel community need to allow engineers to be
24 expectations for upstream community engagement aim to increase the
35 upstream community.
70 * A Software Engineer’s community contributions will be considered in
98 * Organizations will consider community member feedback in official
106 * Organizations will actively seek out community member feedback as a
|
| D | kernel-enforcement-statement.rst | 9 sustainability of our software and community.
12 contributions made to our community, we share an interest in ensuring that
14 community and do not have an unintended negative impact on the health and
17 community to undertake the following commitment to users of the Linux kernel
21 it is in the best interests of our development community to adopt the
45 as a last resort, to be initiated only when other community efforts have
|
| D | 3.Early-stage.rst | 31 immediate problem. To the wider kernel community, though, it was seen as a
38 The audio community, however, could not see past the particular solution
55 - and to discuss it with the development community before investing in the
75 discussions with the community before launching into implementation. Early
95 Years of experience with the kernel development community have taught a
98 released into the community. Sometimes these problems are severe,
100 the kernel community's standards. Some examples include:
173 provide can help the development community provide useful input on the
189 community informed as you go.
|
| D | howto.rst | 8 to work with the Linux kernel development community. It tries to not
24 and hints on how to work with the community. It will also try to
25 explain some of the reasons why the community works like it does.
50 existing development community. It is a diverse group of people, with
79 invaluable for learning how to interact with the kernel community. When
207 some task to start doing to join into the kernel development community,
429 Working with the community
432 The goal of the kernel community is to provide the best possible kernel
457 In a community that is looking for the best technical solution possible,
471 Differences between the kernel community and corporate structures
[all …]
|
| D | index.rst | 9 Working with the kernel development community
14 to learn about how our community works. Reading these documents will make
46 Other guides to the community that are of interest to most developers are:
|
| D | embargoed-hardware-issues.rst | 78 unable to enter into any non-disclosure agreements. The kernel community
86 The Linux kernel community has a deep understanding of the requirement to
90 The Linux kernel community has successfully handled hardware security
92 community compliant development under embargo restrictions.
94 The Linux kernel community has a dedicated hardware security team for
108 effective deterrent in our community. In case a violation happens the
194 kernel developer community as needed. Bringing in experts can happen at any
279 the Linux kernel community.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 7 provide a set of rules for almost any open source community. Every
8 open-source community is unique and the Linux kernel is no exception.
10 community will interpret it. We also do not expect this interpretation
28 kernel community, a "maintainer" is anyone who is responsible for a
41 That being said, our community is vast and broad, and there is no new
43 behave in the parts of the community where they are active. That
49 others in the community when needed. Do not be afraid to reach out to
83 the Code of Conduct. The kernel community is aware of that and provides
89 The Linux kernel community primarily interacts on a set of public email
98 Conduct. The Linux kernel community does not have an "official" project
[all …]
|
| D | code-of-conduct.rst | 11 our community a harassment-free experience for everyone, regardless of age, body
25 * Focusing on what is best for the community
26 * Showing empathy towards other community members
58 when an individual is representing the project or its community. Examples of
59 representing a project or community include using an official project e-mail
86 kernel community will be interpreting this document.
|
| D | 1.Intro.rst | 13 availability to users, community support in many forms, and the ability to
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
81 Working with the kernel development community is not especially hard. But,
83 difficulties when trying to do kernel work. The kernel community has
93 community's ways (or, worse, who tries to flout or circumvent them) will
94 have a frustrating experience in store. The development community, while
101 community is always in need of developers who will help to make the kernel
103 join our community.
121 learning how to work with the kernel community and get their code into the
[all …]
|
| D | kernel-enforcement-statement.rst | 9 sustainability of our software and community.
12 contributions made to our community, we share an interest in ensuring that
14 community and do not have an unintended negative impact on the health and
17 community to undertake the following commitment to users of the Linux kernel
21 it is in the best interests of our development community to adopt the
45 as a last resort, to be initiated only when other community efforts have
|
| D | 3.Early-stage.rst | 31 immediate problem. To the wider kernel community, though, it was seen as a
38 The audio community, however, could not see past the particular solution
55 - and to discuss it with the development community before investing in the
75 discussions with the community before launching into implementation. Early
95 Years of experience with the kernel development community have taught a
98 released into the community. Sometimes these problems are severe,
100 the kernel community's standards. Some examples include:
172 provide can help the development community provide useful input on the
188 community informed as you go.
|
| D | index.rst | 8 Working with the kernel development community
13 to learn about how our community works. Reading these documents will make
35 Other guides to the community that are of interest to most developers are:
|
| D | howto.rst | 8 to work with the Linux kernel development community. It tries to not
24 and hints on how to work with the community. It will also try to
25 explain some of the reasons why the community works like it does.
50 existing development community. It is a diverse group of people, with
79 invaluable for learning how to interact with the kernel community. When
207 some task to start doing to join into the kernel development community,
430 Working with the community
433 The goal of the kernel community is to provide the best possible kernel
458 In a community that is looking for the best technical solution possible,
472 Differences between the kernel community and corporate structures
[all …]
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | xfs-maintainer-entry-profile.rst | 34 elsewhere in the kernel community.
45 and nudge the community in that direction.
89 - **Community Manager**: This person calls and moderates meetings of as many
155 community.
174 This gives the community time to review the changes, to suggest other changes,
179 This allows the broader kernel community adequate time to test the
|
| /kernel/linux/linux-6.6/sound/soc/sof/ |
| D | sof-pci-dev.c | 115 /* all Up boards use the community key */
124 * All newer platforms use the community key
266 * for platforms using the SOF community key, change the in sof_pci_probe()
284 "community"); in sof_pci_probe()
287 "Platform uses community key, changed fw path to %s\n", in sof_pci_probe()
305 "community"); in sof_pci_probe()
308 "Platform uses community key, changed fw_lib path to %s\n", in sof_pci_probe()
|